lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <>
Subject [jira] Updated: (LUCENE-1279) RangeQuery and RangeFilter should use collation to check for range inclusion
Date Fri, 12 Sep 2008 18:42:44 GMT


Steven Rowe updated LUCENE-1279:

    Attachment: LUCENE-1279.patch

Updated to current trunk revision (694771).  Mostly this consisted of switching away from
deprecated Hits in tests.

Also, I used JavaCC 4.1 to regenerate et al., and it looks like all of the
files in the o.a.l.queryParser package have been changed - apparently the last time they were
generated, JavaCC 4.0 was used.

All tests pass for me (except TestIndexReaderReopen.testThreadSafety(), which I just posted
to java-dev about, and which should be completely unrelated to this issue).

> RangeQuery and RangeFilter should use collation to check for range inclusion
> ----------------------------------------------------------------------------
>                 Key: LUCENE-1279
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>    Affects Versions: 2.3.1
>            Reporter: Steven Rowe
>            Assignee: Grant Ingersoll
>            Priority: Minor
>             Fix For: 2.4
>         Attachments: LUCENE-1279.patch, LUCENE-1279.patch, LUCENE-1279.patch
> See [this java-user discussion|]
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:
For additional commands, e-mail:

View raw message