I am trying to add a CharFilter
to my StandardAnalyzer
. My intention is to strip out punctuation from all the text I index; for example I want a PrefixQuery "pf" to match "P.F. Chang's" or "zaras" to match "Zara's".
It seems that the easiest plan of attack here is to filter out all punctuation before analysis. Per the Analyzer package documentation, that means I should use a CharFilter
.
However, it seems next to impossible to actually insert a CharFilter
into the analyzer!
The JavaDoc for Analyzer.initReader says "Override this if you want to insert a CharFilter".
If my code extends Analyzer, I can extend initReader but I cannot delegate the abstract createComponents to my base StandardAnalyzer, as it is protected. I cannot delegate tokenStream to my base analyzer, because it is final. So a subclass of Analyzer seemingly cannot use another Analyzer to do its dirty work.
There is an AnalyzerWrapper
class that seems perfect for what I want! I can provide a base analyzer and only override the pieces that I want. Except … initReader is overridden already to delegate to the base analyzer, and this override is "final"! Bummer!
I guess I could have my Analyzer
be in the org.apache.lucene.analyzers
package and then I can access the protected createComponents
method, but this seems like a disgustingly hacky way to bypass the public API that I really should use.
Am I missing something glaring here? How can I amend a StandardAnalyzer
to use a custom CharFilter
?
The intent is for you to override
Analyzer
, rather thanStandardAnalyzer
. The thinking is that you should never subclass an Analyzer implementation (some discussion of there here). Analyzer implementations are pretty straightforward though, and adding a CharFilter to an Analyzer implementing the same tokenizer/filter chain as StandardAnalyzer would look something like: