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-1279) RangeQuery and RangeFilter should use collation to check for range inclusion
Date Fri, 09 May 2008 05:04:55 GMT

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

Steven Rowe commented on LUCENE-1279:
-------------------------------------

bq. Hmmm... excellent point. you convinced me.

Okay. :)  At your (previous) suggestion, I have redone the patch (will attach shortly), moving
the collating stuff into RangeQuery and RangeFilter, with enabling bits in QueryParser and
ConstantScoreRangeQuery.  I put WARNING text in the javadoc for each method that invokes the
expensive index Term iteration, so hopefully that will give pause to those who might otherwise
unwittingly slow things down.

bq. BTW: if hooks for CollatingRangeQuery are added to QueryParser, it shouldn't use this
class just because a Locale is specified - that would cause some unexpected results for people
who have been specifying a Locale for date reasons. a new "setter" would need to indicate
when to pay attention to Collation.

I added a new setter to QueryParser for this purpose: {{ setRangeCollator(Collator) }}.

> RangeQuery and RangeFilter should use collation to check for range inclusion
> ----------------------------------------------------------------------------
>
>                 Key: LUCENE-1279
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1279
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>    Affects Versions: 2.3.1
>            Reporter: Steven Rowe
>            Priority: Minor
>             Fix For: 2.4
>
>         Attachments: LUCENE-1279.patch
>
>
> See [this java-user discussion|http://www.nabble.com/lucene-farsi-problem-td16977096.html]
of problems caused by Unicode code-point comparison, instead of collation, in RangeQuery.
> RangeQuery could take in a Locale via a setter, which could be used with a java.text.Collator
and/or CollationKey's, to handle ranges for languages which have alphabet orderings different
from those in Unicode.

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