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
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
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
an Ramasubramanian [mailto:kums@gmail.com]
> Sent: Thursday, January 12, 2017 2:53 AM
> To: java-user@lucene.apache.org
> Subject: Re: Heavy usage of final in Lucene classes
>
> Hi
>
> I want to know the purpose of having final in analyzers.
>
> For eg: classi
Hi
I want to know the purpose of having final in analyzers.
For eg: classicanalyzer. It will be easy to add asciifolding filter over
classicanalyzer.
-
Kumaran R
On Jan 12, 2017 5:41 AM, "Michael McCandless"
wrote:
I don't think it's about efficiency but rather about not exposing
possibly tr
I don't think it's about efficiency but rather about not exposing
possibly trappy APIs / usage ...
Do you have a particular class/method that you'd want to remove final from?
Mike McCandless
http://blog.mikemccandless.com
On Wed, Jan 11, 2017 at 4:15 PM, Michael Wilkowski wrote:
> Hi,
> I som
