We started to implement a named entity recognition on the base of
AnalyzingSuggester, which offers
the great support for Synonyms, Stopwords, etc.
For this, we slightly modified AnalyzingSuggester.lookup() to only return the
exactFirst hits
(considering the exactFirst code block only, skipping th
It sounds as if you want to create a new Query type. I would start by
having a look at BooleanQuery and trying to write an analogous object
that does what you want instead.
-Mike
On 11/13/2013 10:03 AM, Harald Kirsch wrote:
Hello all,
I wonder if a query according to the following rules is
Hello all,
I wonder if a query according to the following rules is possible.
We have several fields with increasing hierarchy, say f_0 to f_{2n}. The
rule to search for a term is that starting with index 0 the first field
to contain a hit defines whether to return the document or not, i.e.:
When I include a BooleanClause with a NumericRangeQuery, the results for
MUST are different from those for SHOULD (as expected). My question is:
In the case of SHOULD, is the NumericRangeQuery effectively ignored? Is
there a similarity calculation based on how far the document's field value
is out
Pasting that line into a chunk of code works fine for me, with 4.5
rather than 4.3 but I don't expect that matters. Have you got a) all
the right jars in your classpath and b) none of the wrong jars?
--
Ian.
On Wed, Nov 13, 2013 at 11:20 AM, Hang Mang wrote:
> Hi guys,
>
> I'm using Lucene 4.3
Hi guys,
I'm using Lucene 4.3 and I'm getting this Exception:
java.lang.NoSuchFieldError: STOP_WORDS_SET
at this line in my code:
CharArraySet DEFAULT_STOP_SET = StandardAnalyzer.STOP_WORDS_SET;
This is driving me crazy, I don't know what's wrong!
