[ 
https://issues.apache.org/jira/browse/LUCENE-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644773#action_12644773
 ] 

Hoss Man commented on LUCENE-1435:
----------------------------------

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. 

(I only brought it up in my first comment because i know very little about the 
internals of *any* Collator Implementations out there, and i wasn't sure if 
*all* Implementations produces keys that were only comparable between "same" 
instances .. as long as there are *some* implementations of Collator that 
products keys which can be compared between "equivalent" instances, then this 
feature certainly seems useful.

> 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]

Reply via email to