[
https://issues.apache.org/jira/browse/LUCENE-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683174#action_12683174
]
Steven Rowe commented on LUCENE-1435:
-------------------------------------
It's in contrib/miscellaneous/
I used AnalyzingQueryParser in the tests to allow CollationKeyFilter to be
applied to the terms in the range query - the standard QueryParser doesn't
analyze range terms.
From:
http://lucene.apache.org/java/2_4_1/api/org/apache/lucene/queryParser/analyzing/AnalyzingQueryParser.html
bq. Overrides Lucene's default QueryParser so that Fuzzy-, Prefix-, Range-, and
WildcardQuerys are also passed through the given analyzer, but wild card
characters (like *) don't get removed from the search terms.
This is a (test-only) cross-contrib dependency. I'm not sure why I didn't have
trouble with compilation - I haven't looked at this in months. I'll take a
look later on tonight.
> 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
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.9
>
> Attachments: LUCENE-1435.patch, LUCENE-1435.patch, 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]
