lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jamie (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LUCENE-5749) analyzers should be further customizable to allow for better code reuse
Date Tue, 10 Jun 2014 07:50:01 GMT
Jamie created LUCENE-5749:
-----------------------------

             Summary: 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


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


Mime
View raw message