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:55:15 GMT


Robert Muir commented on LUCENE-4858:

Just to be clear, I'm not against allowing someone to tradeoff relevance for speed (even where
the requested sort is e.g. by score), but I just think that its way more important to make
these tradeoffs clear in the APIs than to worry about expert things like addIndexes.

By having good APIs that are clear about this (e.g. a "safe" way and also an "unsafe" way)
with good javadocs, then its more likely users will be happy and not run into traps.

The stuff like addIndexes is still good, I just dont think its as important in the big picture:
its so esoteric that it need not even be addressed in the initial commit. I know good APIs
and javadocs arent as sexy as adding more stuff to the index, but its much more important
here IMO.
> 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