[
https://issues.apache.org/jira/browse/LUCENE-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026292#comment-14026292
]
Robert Muir commented on LUCENE-5749:
-------------------------------------
Personally I don't think the analyzers should have all the options they have
today: they should just be simple, practical examples.
its really like 2 or 3 lines of code to make your own analyzer.
Maybe the problem is that since Analyzer is java, people see it as code when
its really just a definition. I would rather change the analyzers to just be
default configurations in a text file or something so that people won't want to
extend them anymore :)
> analyzers should be further customizable to allow for better code reuse
> -----------------------------------------------------------------------
>
> Key: LUCENE-5749
> URL: https://issues.apache.org/jira/browse/LUCENE-5749
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/analysis
> Affects Versions: 4.8.1
> Environment: All
> Reporter: Jamie
> Priority: Minor
> Labels: analyzers
>
> To promote code reuse, the customizability of the analyzers included with
> Lucene (e.g. EnglishAnalyzer) ought to be further improved.
> To illustrate, it is currently difficult to specify general stemming behavior
> without having to modify each and every analyzer class. In our case, we had
> to change the constructors of every analyzer class to accept an
> AnalyzerOption argument.
> The AnalyzerOption class has a getStemStrategy() method. StemStrategy is
> defined as follows:
> public enum StemStrategy { AGGRESSIVE, LIGHT, NONE };
> We needed to modify over 20 or so Lucene classes. This is obviously not ideal
> from a code reuse and maintainability standpoint.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
