lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1435) CollationKeyFilter: convert tokens into CollationKeys encoded using IndexableBinaryStringTools
Date Sun, 02 Nov 2008 17:16:46 GMT

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

Steven Rowe commented on LUCENE-1435:
-------------------------------------

Three problems I can think of off the top of my head with attempting an automatically managed
solution to the problem of CollationKey comparability:

# There doesn't seem to be any way of ascertaining the RuleBasedCollator version, so one would
have to store exact JVM version and Locale used to genenerate the Collator, and the strength
used, and then fail any range or sort operations if the indexed CollationKeys were produced
with ones different from the current ones.
# Lucene doesn't have an index-level per-field place to store arbitrary information.
# Other implementations of java.text.Collator, besides RuleBasedCollator, are certainly possible.

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 :).

Would strong warnings in the javadocs be enough to allow people to take appropriate precautions?

> 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message