[
https://issues.apache.org/jira/browse/LUCENE-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932469#action_12932469
]
Yonik Seeley commented on LUCENE-2766:
--------------------------------------
Same merge policy would normally end up giving different results since the data
is different.
If you have the primary index, and are building an aux index, what you want is
a policy that won't merge at all, but that you can manually flush at the end of
every segment in the primary index.
> ParallelReader should support getSequentialSubReaders if possible
> -----------------------------------------------------------------
>
> Key: LUCENE-2766
> URL: https://issues.apache.org/jira/browse/LUCENE-2766
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Reporter: Andrzej Bialecki
>
> Applications that need to use ParallelReader can't currently use per-segment
> optimizations because getSequentialSubReaders returns null.
> Considering the strict requirements on input indexes that ParallelReader
> already enforces it's usually the case that the additional indexes are built
> with the knowledge of the primary index, in order to keep the docId-s
> synchronized. If that's the case then it's conceivable that these indexes
> could be created with the same number of segments, which in turn would mean
> that their docId-s are synchronized on a per-segment level. ParallelReader
> should detect such cases, and in getSequentialSubReader it should return an
> array of ParallelReader-s created from corresponding segments of input
> indexes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
