Hi,
I have a webapp with a working Lucene search function. The indexed
documents contain among others two TextFields called "name" and
"fulltext". The "name" TextField holds only one term, for example
"bgh". The default field for query terms is "fulltext". The query
"+name:bgh" leads to a NullPoin
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
FYI
I figured out what the problem is/was.
It was not the PerFieldAnalyzer, it was the QueryParser I used.
The QueryParser created a TermRangeQuery and not a NumericRangeQuery.
-Original Message-
From: Vielsack, Marcel [mailto:marcel.viels...@capgemini.com]
Sent: Donnerstag, 31. Oktob
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
