# Updating Node Label, without changing graph itself, using virtual nodes and relationships causes duplicate nodes

**URL:** <https://community.neo4j.com/t/updating-node-label-without-changing-graph-itself-using-virtual-nodes-and-relationships-causes-duplicate-nodes/62038>\
**Category:** Procedures & APOC\
**Created:** [April 13, 2023, 3:35pm UTC](https://community.neo4j.com/t/updating-node-label-without-changing-graph-itself-using-virtual-nodes-and-relationships-causes-duplicate-nodes/62038 "2023-04-13T15:35:40Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![j.brent](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/j.brent/32/22522_2.png) [@j.brent](https://community.neo4j.com/u/j.brent)\
**Post date:** [April 14, 2023, 7:02pm UTC](https://community.neo4j.com/t/updating-node-label-without-changing-graph-itself-using-virtual-nodes-and-relationships-causes-duplicate-nodes/62038/5 "2023-04-14T19:02:18Z")

</div>

Hi @glilienfield,

Thanks for the update and no need to apologize, I didn't provide the data! 😃

Interestingly, the updated cypher works in browser but not in Bloom!

The bloom failure produced the following:  
`AN ERROR OCCURRED WHILE EXECUTING SEARCH: Writing in read access mode not allowed. Attempted write to internal graph 1 `

![image](https://us1.discourse-cdn.com/flex021/uploads/neo4jcommunity/original/3X/2/3/23fc47d2a0bf63c061eeb7b6115d596e9b77fa2b.png)

I found the following [Writing in read access mode not allowed when using Bloom and Data explorer for Neo4j Plugins](https://community.neo4j.com/t/writing-in-read-access-mode-not-allowed-when-using-bloom-and-data-explorer-for-neo4j-plugins/49185) and [Problem writing to 4.1x · Issue #137 · adam-cowley/neode · GitHub](https://github.com/adam-cowley/neode/issues/137) which seem semi-related.

The response from the first link seems unlikely at this point as I can confirm that Bloom can handle vNodes and vRelationships. The second leads me to believe it may be a version issue (I know our versions are not up to date ... ). Do you have any ideas?

I am using Enterprise Neo4j V 4.4.3, Neo4j Bloom version: 2.0.0 on an AWS EC2.

---

_[View the full topic](https://community.neo4j.com/t/updating-node-label-without-changing-graph-itself-using-virtual-nodes-and-relationships-causes-duplicate-nodes/62038)._