lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Commented: (LUCENE-2514) Change Term to use bytes
Date Fri, 25 Jun 2010 14:12:50 GMT


Robert Muir commented on LUCENE-2514:

Uwe, thanks for the MTQ updates. i will merge them with my previous patch (not my latest broken

After looking at RangeQuery/Filter, i think i would prefer to make a subtask to refactor the
collation part out.
For example, we could make CollatedRangeQuery.

In my opinion this is really very different from an ordinary binary-ordered range query and
is confusing to both
users and the code to be mixed in. I think we should consider fixing the API by splitting
these and adding
documentation to the migrate.txt

> Change Term to use bytes
> ------------------------
>                 Key: LUCENE-2514
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Task
>          Components: Search
>    Affects Versions: 4.0
>            Reporter: Robert Muir
>         Attachments: LUCENE-2514-MTQPagedBytes.patch, LUCENE-2514-MTQPagedBytes.patch,
LUCENE-2514-MTQPagedBytes.patch, LUCENE-2514-surrogates-dance.patch, LUCENE-2514.patch, LUCENE-2514.patch,
LUCENE-2514.patch, LUCENE-2514.patch, LUCENE-2514.patch, LUCENE-2514.patch, LUCENE-2514.patch
> in LUCENE-2426, the sort order was changed to codepoint order.
> unfortunately, Term is still using string internally, and more importantly its compareTo()
uses the wrong order [utf-16].
> So MultiTermQuery, etc (especially its priority queues) are currently wrong.
> By changing Term to use bytes, we can also support terms encoded as bytes such as numerics,
instead of using
> strange string encodings.

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