On Thu, Jul 25, 2013 at 3:15 PM, Marcos Juarez Lopez wrote:
> Shai and Michael,
>
> Thanks for your help. That did the trick, getting the live
> IndexDeletionPolicy from the live writer config.
>
> I also agree with Michael, it's not obvious at all from the docs and/or
> Lucene in Action book. M
Well, it's sort of documented on IndexWriterConfig already:
* Once {@link IndexWriter} has been created with this object, changes to
this
* object will not affect the {@link IndexWriter} instance. For that, use
* {@link LiveIndexWriterConfig} that is returned from {@link
IndexWriter#getConfig()
Shai and Michael,
Thanks for your help. That did the trick, getting the live
IndexDeletionPolicy from the live writer config.
I also agree with Michael, it's not obvious at all from the docs and/or
Lucene in Action book. Maybe this can be clarified on the
IndexDeletionPolicy javadocs going forw
This is unfortunately very trappy ... this happened with LUCENE-4876,
where we added cloning of IndexDeletionPolicy on IW construction.
It's very confusing that the IDP you set on your IWC is not in fact
the one that IW uses...
Mike McCandless
http://blog.mikemccandless.com
On Wed, Jul 24, 2013
Hi
In Lucene 4.4 we've improved the snapshotting process so that you don't
need to specify an ID.
Also, there's a new Replicator module which can be used for just that
purpose - take hot index backups of the index.
It pretty much hides most of the snapshotting from you. You can read about
it here:
