lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Created: (LUCENE-2439) Composite readers (Multi/DirIndexReader) should not subclass IndexReader
Date Mon, 03 May 2010 21:04:55 GMT
Composite readers (Multi/DirIndexReader) should not subclass IndexReader

                 Key: LUCENE-2439
             Project: Lucene - Java
          Issue Type: Improvement
          Components: Index
            Reporter: Michael McCandless
             Fix For: 4.0.0

I'd like to change Multi/DirIndexReader so that they no longer implement the low level methods
of IndexReader, and instead act more like an ordered collection of sub readers.  I think to
do this we'd need a new interface, common to atomic readers (SegmentReader) and the composite
readers, which IndexSearcher would accept.

We should also require that the core Query scorers always receive an atomic reader.

We've taken strong initial steps here with flex, by forcing users to use separate MultiFields
static methods to obtain Fields/Terms/etc. from a composite reader.  This issue is to finish
this cutover.

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