You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Uwe Schindler (JIRA)" <ji...@apache.org> on 2011/01/14 19:14:47 UTC
[jira] Closed: (LUCENE-2439) Composite readers
(Multi/DirIndexReader) should not subclass IndexReader
[ https://issues.apache.org/jira/browse/LUCENE-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler closed LUCENE-2439.
---------------------------------
Resolution: Duplicate
Duplicate of LUCENE-2858.
> 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
>
>
> 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