[
https://issues.apache.org/jira/browse/LUCENE-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2514:
----------------------------------
Attachment: LUCENE-2514-MTQPagedBytes.patch
Improved version of PagedBytes MTQ cut off collector. It adds a method to
PagedBytes.Reader to sequentially read all BytesRefs without a separate offset
array.
Mike, if you are fine with that, we should add this to the global patch for
this issue.
We should maybe also fix PagedBytes.freeze(boolean), as the parameter is
currently unused. For the use case here, reallocating the last block is not
really needed, it can stay as is. Maybe we should readd support for this
parameter.
> 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-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: [email protected]
For additional commands, e-mail: [email protected]
