[
https://issues.apache.org/jira/browse/LUCENE-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644782#action_12644782
]
Steven Rowe commented on LUCENE-1435:
-------------------------------------
Hoss wrote:
{quote}
bq. So, it seems to me, either the user of this functionality has to manage the
versioning external to the Lucene index, or they can't use the functionality .
bq. Would strong warnings in the javadocs be enough to allow people to take
appropriate precautions?
I agree with you on both points ... this is really just an extension of warning
people to use compatible analyzers when indexing/querying.
{quote}
I will add warnings about this issue to the javadocs.
> 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]
