What about opening IndexReader/Searcher on certain commit point? Will it be implemented in 2.9?
The use-case is similar to the one Michael Busch described, only I would like to open (or reopen) a searcher on specific commit point. On Fri, Feb 27, 2009 at 20:31, Michael McCandless <luc...@mikemccandless.com> wrote: > > Michael Busch wrote: > >> Actually I personally don't need Lucene to be "write once". The reason why >> I started this thread about the segments.gen file was that in our project we >> sometimes need to rollback to a previous commit-point (using Lucene 2.4.0) >> that we keep around with the SnapshotDeletionPolicy. To get rid of the >> newest commit-point we simply delete the most recent segments file. But then >> we also have to delete the segments.gen file, otherwise Lucene will read the >> generation from it and try to find the segments file we deleted. Then Lucene >> will recreate the segments.gen file. This just made me think that this is >> not very clean (deleting and recreating the segments.gen) especially because >> we use a local FS and don't even need the .gen file. > > Ahh... OK. In trunk/2.9, you can explicitly open an IndexWriter on a prior > commit point, which will take care of the gen file for you. --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
