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

Jack Krupansky commented on SOLR-3359:
--------------------------------------

Is there any particular reason why this enhancement is not targeted at 4.x as 
well?

Also, could the title summary be updated to reflect the fact that the change 
specifies the analyzer class name rather than "fieldType"?

                
> SynonymFilterFactory should accept fieldType attribute rather than 
> tokenizerFactory
> -----------------------------------------------------------------------------------
>
>                 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to