To answer my own question, it appears that despite the warning, using a
custom similarity only at search time appears to be working. The score()
method was the wrong code to override, I simply hardcoded the return value
of decodeNormValue to 1.0. Since this value is used for normalization, as
long
The analyzer is generating holes for the stop words - the position of the
subsequent term is incremented an extra time for each stop word so that
their positions are maintained.
-- Jack Krupansky
-Original Message-
From: Jean-Claude Dauphin
Sent: Monday, December 09, 2013 4:15 PM
To:
Hi,
My application uses an analyzer with a StopWordFilter. PhraseQuery
translates queries with stopwords by replacing stopwords to "?" characters.
For example, "Java and Lucene" is replaced by "Java ? Lucene" and "to
contribute" is replaced by "? contribute" . Sequence of terms are indexed
without
I am currently using document-level boosts, which really translates to
changing the norm for every field under the covers. As part of an
experiment, I want to remove the boost, but that would require either
re-indexing content or changing the scoring algorithm (similarity).
If I create my own simi
