com]
Sent: Tuesday, September 25, 2012 6:32 PM
To: java-user@lucene.apache.org
Subject: Re: Lucene 4.0 PerFieldAnalyzerWrapper question
Mike,
On Wed, Sep 26, 2012 at 1:05 PM, Mike O'Leary wrote:
> Hi Chris,
> So if I change my analyzer to inherit from AnalyzerWrapper, I need to
> def
he
components parameter unchanged.
>
> -----Original Message-
> From: Chris Male [mailto:gento...@gmail.com]
> Sent: Tuesday, September 25, 2012 5:34 PM
> To: java-user@lucene.apache.org
> Subject: Re: Lucene 4.0 PerFieldAnalyzerWrapper question
>
> Ah I see.
>
>
am);
}
}
-Original Message-
From: Chris Male [mailto:gento...@gmail.com]
Sent: Tuesday, September 25, 2012 5:34 PM
To: java-user@lucene.apache.org
Subject: Re: Lucene 4.0 PerFieldAnalyzerWrapper question
Ah I see.
The problem is that we don't really encourage wrapping of Anal
t; Mike
>
> -Original Message-
> From: Chris Male [mailto:gento...@gmail.com]
> Sent: Tuesday, September 25, 2012 5:18 PM
> To: java-user@lucene.apache.org
> Subject: Re: Lucene 4.0 PerFieldAnalyzerWrapper question
>
> Hi Mike,
>
> I don't really understa
java-user@lucene.apache.org
Subject: Re: Lucene 4.0 PerFieldAnalyzerWrapper question
Hi Mike,
I don't really understand what problem you're having.
PerFieldAnalyzerWrapper, like all AnalyzerWrappers, uses
Analyzer.PerFieldReuseStrategy which means it caches the TokenStreamCompone
Hi Mike,
I don't really understand what problem you're having.
PerFieldAnalyzerWrapper, like all AnalyzerWrappers, uses
Analyzer.PerFieldReuseStrategy which means it caches the
TokenStreamComponents per field. The TokenStreamComponents cached are
created by by retrieving the wrapped Analyzer thr
I am updating an analyzer that uses a particular configuration of the
PerFieldAnalyzerWrapper to work with Lucene 4.0. A few of the fields use a
custom analyzer and StandardTokenizer and the other fields use the
KeywordAnalyzer and KeywordTokenizer. The older version of the analyzer looks
like
