[
https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657455#action_12657455
]
Michael McCandless commented on LUCENE-1483:
--------------------------------------------
{quote}
> BooleanScorer can collect hits out of order if you force it (against the
> contract).
{quote}
Hmmm... right. You mean if you pass in allowDocsOutOfOrder=true (defaults to
false).
I think this should not be a problem? (Though, I really don't fully understand
BooleanScorer!). Since we are running scoring per-segment, each segment might
collect its docIDs out of order, but all such docs are still within the current
segment. Then when we advance to the new segment, the collector can do
something if it needs to, and then collection proceeds again on the next
segment's docs, possibly out of order. Ie, the out-of-orderness never jumps
across a segment and then back again?
But this is a challenge for LUCENE-831, if we go with a primarily
iterator-driven API.
> Change IndexSearcher to use MultiSearcher semantics for multiple subreaders
> ---------------------------------------------------------------------------
>
> Key: LUCENE-1483
> URL: https://issues.apache.org/jira/browse/LUCENE-1483
> Project: Lucene - Java
> Issue Type: Improvement
> Affects Versions: 2.9
> Reporter: Mark Miller
> Priority: Minor
> Attachments: LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch,
> LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch,
> LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch,
> LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch
>
>
> FieldCache and Filters are forced down to a single segment reader, allowing
> for individual segment reloading on reopen.
--
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]
