lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] Commented: (LUCENE-2514) Change Term to use bytes
Date Thu, 24 Jun 2010 21:56:51 GMT


Uwe Schindler commented on LUCENE-2514:

bq. I would temporary remove all String methods from Term and try to compile core. If this
works you should find all perf regressions in both directions.

i did this, but there is a lot of unrelated stuff that uses Term string methods and is perfectly
fine. especially many tests and things like queryparser.

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

bq. one option might be to split the collating range stuff into its own classes or something,
i think its a bit confusing how collation is mixed in with 'binary' order... it tricks you
into thinking the 'default' is UCA or default locale or something, but is neither. 

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

> 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