lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4858) Early termination with SortingMergePolicy
Date Sun, 31 Mar 2013 17:37:15 GMT


Robert Muir commented on LUCENE-4858:

+1. This makes sense. We need to be as robust as possible. If a user makes a mistake, it's
best if he can avoid tripping himself.

Then step number 1 is not to futz around with adding more and more metadata to the index and
changing the behavior of addindexes and so on, but instead to enforce the collector is only
used when sorting by index order!

The current patch goes to great extremes to add more and more and more complexity at the index-level
but misses the forrest for the trees.
> 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
> 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