lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrien Grand (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4858) Early termination with SortingMergePolicy
Date Sat, 06 Apr 2013 14:13:15 GMT


Adrien Grand updated LUCENE-4858:

    Attachment: LUCENE-4858.patch

Thanks Shai, this looks good! I modified a bit your patch to fix the collector constructor
visiblity (from protected to public) and added some documentation. I'd like to discuss whether
we should actually add the name of the Sorter class in the "sorter" property of the diagnostics.
I would rather remove it so that renaming a Sorter class doesn't break compatibility, what
do you think?
> 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,
> 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