[
https://issues.apache.org/jira/browse/LUCENE-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618459#comment-13618459
]
Shai Erera commented on LUCENE-4858:
------------------------------------
Another way to fix addIndexes is to never merger, but rather behave like
addIndexes(Directory) -- iterate on leaves and call SegmentMerger.merge() on
each one of them. App can call maybeMerge afterwards. addIndexes(IndexReader)
is intended, mostly I think, for filtering readers, otherwise the Directory
version is much faster. Fixing addIndexes like that makes it consistent with
the Directory version, and still accomplishing its goal. Note, it does not
address the 'sorted' issue, but as I wrote a couple times already, the two are
unrelated.
> Early termination with SortingMergePolicy
> -----------------------------------------
>
> Key: LUCENE-4858
> URL: https://issues.apache.org/jira/browse/LUCENE-4858
> 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
> https://issues.apache.org/jira/browse/LUCENE-4752?focusedCommentId=13606565&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13606565
> and
> https://issues.apache.org/jira/browse/LUCENE-4752?focusedCommentId=13607282&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13607282
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
