UUID is not available via cypher immediately upon creation about neo4j-uuid

[venkat125]

But, it is NICE TO HAVE feature though.
Can i get the below doubt cleared please?

• Do the UUID plugin from Graphaware will be unique even if we've more Neo4j (instance in the hosting/ running ip's in cloud)? @bachmanm

[bachmanm]

Unfortunately, this is how Neo4j works today - if you create a node a return it immediately, its contents do not reflect changes performed by transaction event handlers (i.e., it does not re-read the node before returning it). This is true for all the APIs, the browser, etc. A separate call must be made to get the UUID and I don't think there's any way we can change this behaviour in the framework.

[voidstardb]

Thanks for the explanation.

[voidstardb]

Just for future reference: http://neo4j.com/docs/2.2.1/javadocs/org/neo4j/graphdb/event/TransactionEventHandler.html

beforeCommit
The transaction is still open when this method is invoked, making it possible to perform mutating operations in this method. This is however highly discouraged. Changes made in this method are not guaranteed to be visible by this or other TransactionEventHandlers.

There's no other obvious lifecycle hook in which to place the UUID functionality. So, I guess we're stuck with this for now.

[Bretto]

What a shame...

[Crodaycat]

Is there something new about this?