> If "store" fails, then index will not happen. Is code in StateChangeNotificationConcern#applyChanges handling this behaviour ? Becouse I see there that index is commited before data.
Some db engines behind EntityStore ( i.e. MongoDB, Neo4j ) has 'native' support for indexes. Is it against some Qi4j principles to have Index service backed by the same db engine ? (Becouse in my case, I have to. We don't own data and external updates will not update index then.) To implements this, it requires translate Specifications graph into engine native query language, that's it , right ? thanks, -Tibor On Jan 7, 2012, at 10:26 AM, Niclas Hedhman wrote: > If "store" fails, then index will not happen. "indexing" is 'not > allowed' to fail. If you have a crash, there is currently no mechanism > for detecting whether the index is in sync. It is just not > implemented, but planned since "forever". > > > On Sat, Jan 7, 2012 at 7:09 AM, Tibor Mlynarik <[email protected]> > wrote: >> Hi, >> >> I am trying to understand separation of EntityStore and Indexing of Qi4j 2.0. >> Is there couple of those services that garanties transactions ? >> I mean if data store fails, index should be rolled back and vice versa. >> If not transactional (JTA), is there other mechanism that will eventually >> keep index and data in-sync, except full reindex? >> >> Thanks. >> >> Tibor Mlynarik >> _______________________________________________ >> qi4j-dev mailing list >> [email protected] >> http://lists.ops4j.org/mailman/listinfo/qi4j-dev > > > > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/3xugrbk > I work here; http://tinyurl.com/6a2pl4j > I relax here; http://tinyurl.com/2cgsug > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
