lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Commented: (LUCENE-2766) ParallelReader should support getSequentialSubReaders if possible
Date Tue, 04 Jan 2011 23:00:50 GMT


Robert Muir commented on LUCENE-2766:

bq. I'm gonna hold off on LUCENE-2771 until we figure this one out... because it would make
your getSequentialSubReaders in the synced=true case quite heavy (without modifications).

Sorry, I was wrong on this... I totally forgot the norms cache is lazy-loaded always in that
patch. I'll commit LUCENE-2771 it shouldnt affect this!

> ParallelReader should support getSequentialSubReaders if possible
> -----------------------------------------------------------------
>                 Key: LUCENE-2766
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Index
>            Reporter: Andrzej Bialecki 
>         Attachments: LUCENE-2766.patch
> 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:
For additional commands, e-mail:

View raw message