Thanks Mike, that pointer was a great help - and Shai, that is exactly what
I ended up trying. (i.e. creating a
new ReferenceManager that
takes an IndexSearcher, TaxonomyReader & a SearcherFactory - based on the
current SearcherTaxonomyManager.)
The only difference is I didn't bother checking the
Opened https://issues.apache.org/jira/browse/LUCENE-5320.
Shai
On Fri, Nov 1, 2013 at 4:59 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
> On Fri, Nov 1, 2013 at 3:12 AM, Shai Erera wrote:
>
> > Maybe we should offer such a ReferenceManager (maybe it can even be
> > SearcherTaxono
On Fri, Nov 1, 2013 at 3:12 AM, Shai Erera wrote:
> Maybe we should offer such a ReferenceManager (maybe it can even be
> SearcherTaxonomyManager which takes a pair of Directory in another ctor),
> and document that its maybeRefresh needs to be called by the same thread
> that modified the index
SearcherTaxonomyManager can be used only for NRT, as it only takes an
IndexWriter and DirectoryTaxonomyWriter. And I don't think you want to keep
those writers open on the slaves side.
I think that a ReferenceManager, which returns a SearcherAndTaxonomy, is
the right thing to do. The reason why we
Maybe have a look at how the IndexAndTaxonomyReplicationClientTest.java works?
Hmm, in its callback, it manually reopens the index + taxoIndex, but I
think you could instead use a SearcherTaxonomyManager and call its
.maybeRefresh inside your callback?
Mike McCandless
http://blog.mikemccandless.
Hello,
I'm attempting to setup a master/slave arrangment between two servers where
the master uses a SearcherTaxonomyManger to index and search, and the slave
is read-only - using just an IndexSearcher and TaxonomyReader.
So far I am able to publish new IndexAndTaxonomyRevisions on the master and
