On Tue, Feb 1, 2011 at 10:59 PM, Massimo Lusetti <mluse...@gmail.com> wrote:
> On Tue, Feb 1, 2011 at 10:50 PM, Tobias Ivarsson > <tobias.ivars...@neotechnology.com> wrote: > > > That is correct, the Isolation of ACID says that data isn't visible to > other > > threads until after commit. > > > > The CHM should not replace the index check though, since you want to > limit > > the number of items in the CHM, you only want this to reflect the > elements > > currently being worked on, the index check should still be there for > > elements processed before. > > So if I read you right you suggest to use a buffer (the CHM) just to > mitigate the effects of ACID from the Lucene/Node db. Is it right? I would of course put it the other way around, since ACID is a desired property. What you are "mitigating" is your need for concurrent insertion of elements that are potentially equal. What I am suggesting is exactly what I'm saying, that you use a CHM to synchronize the concurrent writers, so that they don't write the same items concurrently. Cheers, -- Tobias Ivarsson <tobias.ivars...@neotechnology.com> Hacker, Neo Technology www.neotechnology.com Cellphone: +46 706 534857 _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
