It just waits to write stuff until the transaction committs. Application crashes in between are guarded by the logical log, because all operations are written in the prepare-phase to a logical log (before the commit starts). Neo4j doesn't do any magical tweaking of lucene at all because it isn't necessary... it's fully ACID and transactional with the graph as it is.
2011/7/17 eialbur <[email protected]> > Sorry, but how does this thin layer control how Lucene interacts with the > disk (since Lucene isn't transactional). Does it somehow buffer the disk > I/O? Does it coerce Lucene to write to a different file and then update > the > real file at the end of the transaction? > > I'm not trying to be difficult, but I am interested in Lucene for my > project > as well, and need it to behave properly regarding transactions. > > -- > View this message in context: > http://neo4j-community-discussions.438527.n3.nabble.com/How-can-you-have-transactions-with-Lucene-tp3176918p3176951.html > Sent from the Neo4J Community Discussions mailing list archive at > Nabble.com. > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user > -- Mattias Persson, [[email protected]] Hacker, Neo Technology www.neotechnology.com _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
