[
https://issues.apache.org/jira/browse/LUCENE-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644541#action_12644541
]
Robert Muir commented on LUCENE-1435:
-------------------------------------
at least in ICU, its not completely safe. If the different JVM instances are
"different" in version (upgrade, etc) then it would be a shame to find your
sorts all busted.
When comparing keys, it is important to know that both keys were generated by
the same algorithms and weightings. Otherwise, identical strings with keys
generated on two different dates, for example, might compare as unequal. Sort
keys can be affected by new versions of ICU or its data tables, new sort key
formats, or changes to the Collator.
http://www.icu-project.org/userguide/Collate_ServiceArchitecture.html
> CollationKeyFilter: convert tokens into CollationKeys encoded using
> IndexableBinaryStringTools
> ----------------------------------------------------------------------------------------------
>
> Key: LUCENE-1435
> URL: https://issues.apache.org/jira/browse/LUCENE-1435
> Project: Lucene - Java
> Issue Type: New Feature
> Affects Versions: 2.4
> Reporter: Steven Rowe
> Priority: Minor
> Fix For: 2.9
>
> Attachments: LUCENE-1435.patch
>
>
> Converts each token into its CollationKey using the provided collator, and
> then encodes the CollationKey with IndexableBinaryStringTools, to allow it to
> be stored as an index term.
> This will allow for efficient range searches and Sorts over fields that need
> collation for proper ordering.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
