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
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|52d 23h 17m||1||Michael McCandless||24/Jun/10 13:36|
|1050d 21h 6m||1||Uwe Schindler||10/May/13 10:43|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Workflow||Default workflow, editable Closed status [ 12564294 ]||jira [ 12584829 ]|
|Workflow||jira [ 12509850 ]||Default workflow, editable Closed status [ 12564294 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||4.0 [ 12314025 ]|
|Fix Version/s||3.1 [ 12314822 ]|