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

Hi @glilienfield,

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

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

I found the following Writing in read access mode not allowed when using Bloom and Data explorer for Neo4j Plugins and Problem writing to 4.1x 路 Issue #137 路 adam-cowley/neode 路 GitHub 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.