You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jamie (JIRA)" <ji...@apache.org> on 2014/06/10 09:56:01 UTC

[jira] [Updated] (LUCENE-5749) analyzers should be further customizable to allow for better code reuse

     [ https://issues.apache.org/jira/browse/LUCENE-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie updated LUCENE-5749:
--------------------------

    Priority: Minor  (was: Major)

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org