lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4858) Early termination with SortingMergePolicy
Date Tue, 09 Apr 2013 10:00:16 GMT


Shai Erera commented on LUCENE-4858:

bq. Maybe NumericDocValuesSorter.getID() could just return 'fieldName'?

The reason I did that is in case someone will want to sort by a stored field and numeric field
which have same names. I know it's probably very low chance, but "numericdv_field" is really
unique, as you cannot have two numeric DV fields with the same name, but different meaning.
> Early termination with SortingMergePolicy
> -----------------------------------------
>                 Key: LUCENE-4858
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Adrien Grand
>            Assignee: Adrien Grand
>            Priority: Minor
>             Fix For: 4.3
>         Attachments: LUCENE-4858.patch, LUCENE-4858.patch, LUCENE-4858.patch, LUCENE-4858.patch,
LUCENE-4858.patch, LUCENE-4858.patch
> Spin-off of LUCENE-4752, see
> When an index is sorted per-segment, queries that sort according to the index sort order
could be early terminated.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message