A TokenFilter object already build won't work, because the Analyzer must create new instances of the TokenFilters as needed.
Uwe ----- Uwe Schindler Achterdiek 19, D-28357 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Nicolás Lichtmaier [mailto:nicol...@wolfram.com] > Sent: Wednesday, March 29, 2017 7:00 PM > To: java-user@lucene.apache.org > Subject: Adding TokenFilters to a CustomAnalyzer is too inflexible > > I'm using a CustomAnalyzer.Builder to set up an analyzer. I now would > like to add synonym processing, I already have the SynonymMap in memory. > But the builder interface only takes String arguments. Wouldn't it be a > good thing to add a method to CustomAnalyzer.Builder to add a > TokenFilter object already constructed, instead of only being able to > pass a class name? That is: overload the addTokenFilter method to do > this: builder.addTokenizer(new MyTokenFilter(....)); > > Am I missing something? > > Should I create a patch with this minor modification and send it? > > Thanks! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
