Hi,
Analysis components are not intended to be subclassed, because they follow
another programming pattern. All components in Lucene around
TokenStreams/Tokenizers and Analyzers are using the "decorator pattern"
(similar to InputStreams in Java IO). You combine them by wrapping, similar
like a
Hi,
I wanted to subclass StandardTokenizer to manipulate a little with
PositionAttribute. I wanted to increase steps between adjacent fields of
the same, so if there is a multi-value TextField:
fieldX: "name1 name2",
fieldX:"name3 name4"
then PhraseQuery like this fieldX:"name2 name3" would not r
Hi Michael,
You want to set the positionIncrementGap - either wrap your analyzer with an
AnalyzerWrapper that overrides getPositionIncrementGap(), or use a
CustomAnalyzer builder and set it there.
Alan Woodward
www.flax.co.uk
> On 12 Jan 2017, at 10:57, Michael Wilkowski wrote:
>
> Hi,
> I
Perfect! Thanks, that is what I was looking for :-).
MW
On Thu, Jan 12, 2017 at 12:02 PM, Alan Woodward wrote:
> Hi Michael,
>
> You want to set the positionIncrementGap - either wrap your analyzer with
> an AnalyzerWrapper that overrides getPositionIncrementGap(), or use a
> CustomAnalyzer bu
I don't konw the rhyme/reason but it looks like it was removed (w/o
any deprecation first i guess) as part of LUCENE-7123 in commit:
ce3114233bdc45e71a315cb6ece64475d2d6b1d4
in that commit, existing callers in the lucene code base were changed to
use "2 * GeoProjectionUtils.SEMIMAJOR_AXIS"
(o
