You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Alan Woodward (JIRA)" <ji...@apache.org> on 2014/07/07 19:50:34 UTC

[jira] [Commented] (LUCENE-5807) Deprecate Classic{Analyzer,Tokenizer,Filter} on branch_4x and remove them from trunk

    [ https://issues.apache.org/jira/browse/LUCENE-5807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053911#comment-14053911 ] 

Alan Woodward commented on LUCENE-5807:
---------------------------------------

+1.  I've done a few rescue jobs that had these in their configs, I think they're just confusing for users.

> Deprecate Classic{Analyzer,Tokenizer,Filter} on branch_4x and remove them from trunk
> ------------------------------------------------------------------------------------
>
>                 Key: LUCENE-5807
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5807
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: modules/analysis
>            Reporter: Steve Rowe
>            Assignee: Steve Rowe
>            Priority: Minor
>
> ClassicAnalyzer, ClassicTokenizer and ClassicFilter were introduced in Lucene 3.1, when the StandardTokenizer began implementing the Unicode standard word break rules.
> I think we can drop these analysis components.  ClassicTokenizer isn't being maintained anymore, and StandardTokenizer is a better choice anyway.



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