eventually available
16 views
Skip to first unread message
Niels Hoogeveen
May 16, 2013, 5:00:08 AM5/16/13
to ne...@googlegroups.com
The documentation of the new label/index functionality in Neo4j 2.0 speaks of eventual availability. Does this approach guarantee consistency? In other words, if I add a node with a certain property and immediately commit the transaction, will the index eventually be updated under all circumstances (eg. system crash immediately after commit but before index writes)?
Niels
Mattias Persson
May 16, 2013, 6:04:12 AM5/16/13
to Neo4j Development
It is the initial creation of the index over existing data that is eventually consistent. Whence online it's consistent along with the transaction synchronously.
The documentation of the new label/index functionality in Neo4j 2.0 speaks of eventual availability. Does this approach guarantee consistency? In other words, if I add a node with a certain property and immediately commit the transaction, will the index eventually be updated under all circumstances (eg. system crash immediately after commit but before index writes)?
Niels--
You received this message because you are subscribed to the Google Groups "Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Mattias Persson, [mat...@neotechnology.com]
Hacker, Neo Technology
www.neotechnology.com
Reply all
Reply to author
Forward
0 new messages