[ 
https://issues.apache.org/jira/browse/LUCENE-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael McCandless updated LUCENE-2426:
---------------------------------------

    Attachment: LUCENE-2426.patch

Attached patch, changing term sort order to unicode codepoint!  All tests pass. 
 I fixed preflex codec to seek around surrogates, and then back again, so that 
preflex indices also sort properly; it's rather hairy... I added a new 
randomized test that writes a preflex segment (just the terms dict) with random 
terms and then asserts the order.

> change sort order to binary order
> ---------------------------------
>
>                 Key: LUCENE-2426
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2426
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>    Affects Versions: 3.1
>            Reporter: Robert Muir
>             Fix For: 4.0
>
>         Attachments: LUCENE-2426.patch, LUCENE-2426.patch, 
> LUCENE-2426_automaton.patch
>
>
> Since flexible indexing, terms are now represented as byte[], but for 
> backwards compatibility reasons, they are not sorted as byte[], but instead 
> as if they were char[].
> I think its time to look at sorting terms as byte[]... this would yield the 
> following improvements:
> * terms are more opaque by default, they are byte[] and sort as byte[]. I 
> think this would make lucene friendlier to customizations.
> * numerics and collation are then free to use their own encoding (full byte) 
> rather than avoiding the use of certain bits to remain compatible with char[] 
> sort order.
> * automaton gets simpler because as in LUCENE-2265, it uses byte[] too, and 
> has special hacks because terms are sorted as char[]

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

Reply via email to