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

Uwe Schindler resolved LUCENE-4254.
-----------------------------------

    Resolution: Invalid
      Assignee: Uwe Schindler

This is not a bug. ICUCollationKeyAnalyzer is not for tokenization, so it will 
never split words. Its solely use case is to create exactly one binary, 
non-human-readable token, to be able to sort search results by this binary 
value. The binary token will allow sorting by locale-dependent settings 
("collation"). If it would produce more than one token, it would break sorting.

In general you use this Tokenizer for a specific field (e.g. with 
PerFieldAnalyzerWrapper), so you can sort against this field. For all other 
fields use a different Analyzer.
                
> ICUCollationKeyAnalyzer fail to tokenize Thai word
> --------------------------------------------------
>
>                 Key: LUCENE-4254
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4254
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/analysis
>    Affects Versions: Realtime Branch
>         Environment: Windows 7 SP1.
> Java 1.7.0-b147
>            Reporter: Nattapong Sirilappanich
>            Assignee: Uwe Schindler
>
> Current implementation is:
> KeywordTokenizer tokenizer = new KeywordTokenizer(factory, reader, 
> KeywordTokenizer.DEFAULT_BUFFER_SIZE);
> return new TokenStreamComponents(tokenizer, tokenizer);
> I tried change tokenizer from KeywordTokenizer to ICUTokenizer. It return a 
> proper tokenized word.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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