[
https://issues.apache.org/jira/browse/LUCENE-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882364#action_12882364
]
Robert Muir commented on LUCENE-2514:
-------------------------------------
{quote}
Yeah tests can use string methods, i meant only core classes should compile
without Term's String methods.
{quote}
Ok, i will have another look at this (ignoring tests and queryparser and such).
Maybe i will find something interesting.
{quote}
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...
{quote}
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: https://issues.apache.org/jira/browse/LUCENE-2514
> 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: [email protected]
For additional commands, e-mail: [email protected]
