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 Thu, 24 Jun 2010 22:16:50 GMT


Robert Muir commented on LUCENE-2514:

Yeah tests can use string methods, i meant only core classes should compile without Term's
String methods.

Ok, i will have another look at this (ignoring tests and queryparser and such). Maybe i will
find something interesting.

I was always thinking about factoring out collation stuff from TermRangeQuery. I would like
to have a pure TermRangeQuery without any collations things and maybe a CollationTermRangeQuery
or whatever...

yeah, i think this would be better in the future too. but for now, i can work with what we
have. it just means lots of things like String lowerBound; /* only used when collator != null
*/ and such

> 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-surrogates-dance.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