> > Even if the commit is called just before the close, the close triggers > a last commit. >
That seems wrong. If you do writer.commit() and them immediately writer.close(), and there are no changes to the writer in between (i.e. a thread comes in and adds/updates/deletes a document), then close() should not create a new commit point. Do you see that it does? Shai On Wed, Mar 19, 2014 at 11:09 PM, Roberto Franchini <franch...@celi.it>wrote: > On Sat, Mar 15, 2014 at 12:56 PM, Roberto Franchini <franch...@celi.it> > wrote: > > On Sat, Mar 15, 2014 at 12:47 PM, Shai Erera <ser...@gmail.com> wrote: > >> If you use LocalReplicator on both sides, you have to use the same > instance > >> on both sides. Otherwise the replicas will never see the published > >> revisions the which are done in a separate instance. Can you try that? > > > > Ok, I missed it. I was using different instances. > > I'll try this afternoon. > > Hi, > the replicator works fine on live writer, but when the writer is > closed it does a last commit that isn't replicated. > > Even if the commit is called just before the close, the close triggers > a last commit. > > And trying to use the writer after close is impossible: > > writer.close(); > revision= new IndexRevision(writer); > > produce: > org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed > .... > > So, I can replicate the last commit before the close, and don't worry > about the inner commit that close does. > May I'll lost something? > RF > > -- > Roberto Franchini > The impossible is inevitable. > http://www.celi.it http://www.blogmeter.it > http://github.com/celi-uim http://github.com/robfrank > Tel +39.011.562.71.15 > jabber:ro.franch...@gmail.com skype:ro.franchini tw:@robfrankie > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
