[jira] Commented: (LUCENE-2439) Composite readers (Multi/DirIndexReader) should not subclass IndexReader

["Shai Erera (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863667#action_12863667 ] 

Shai Erera commented on LUCENE-2439:
------------------------------------

On this thread http://www.mail-archive.com/java-dev@lucene.apache.org/msg37497.html I've also proposed to make isDeleted final, which was somehow related to making this change. So if you're at it already, do you think this can be done here as well?

> Composite readers (Multi/DirIndexReader) should not subclass IndexReader
> ------------------------------------------------------------------------
>
>                 Key: LUCENE-2439
>                 URL: https://issues.apache.org/jira/browse/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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org