You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Koji Sekiguchi (JIRA)" <ji...@apache.org> on 2013/07/17 16:26:49 UTC
[jira] [Updated] (SOLR-3359) SynonymFilterFactory should accept
analyzer attribute
[ https://issues.apache.org/jira/browse/SOLR-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koji Sekiguchi updated SOLR-3359:
---------------------------------
Summary: SynonymFilterFactory should accept analyzer attribute (was: SynonymFilterFactory should accept fieldType attribute rather than tokenizerFactory)
> SynonymFilterFactory should accept analyzer attribute
> -----------------------------------------------------
>
> Key: SOLR-3359
> URL: https://issues.apache.org/jira/browse/SOLR-3359
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Reporter: Koji Sekiguchi
> Assignee: Koji Sekiguchi
> Fix For: 5.0
>
> Attachments: 0001-Make-SynonymFilterFactory-accept-analyzer-attr.patch
>
>
> I've not been realized that CJKTokenizer and its factory classes was marked deprecated in 3.6/4.0 (the ticket is LUCENE-2906) until someone talked to me.
> {code}
> * @deprecated Use StandardTokenizer, CJKWidthFilter, CJKBigramFilter, and LowerCaseFilter instead.
> {code}
> I agree with the idea of using the chain of the Tokenizer and TokenFilters instead of CJKTokenizer, but it could be a problem for the existing users of SynonymFilterFactory with CJKTokenizerFactory.
> So this ticket comes to my mind again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org