Interesting, glad we have prior art ;)
They seem to have gone a step further though: a single unified commit
of Neo4J includes both the data and the index changesets. We still
have to figure out how to better integrate the index changes with the
database transaction; although that's only interesting for a minority
use case and I still agree that our current design is better for most
typical use cases, but some have asked for stronger XA like
guarantees.
On 26 March 2015 at 09:27, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
Interesting, Neo4J 2.2 now does unified commits like we do in
Hibernate Search to get several transactions per disk flush in Lucene.
http://neo4j.com/blog/neo4j-2-2-0-scalability-performance/
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev