[
https://issues.apache.org/jira/browse/LUCENE-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621167#comment-16621167
]
David Smiley commented on LUCENE-7875:
--------------------------------------
It's a shame MultiReader is already taken as a name since it'd be a good place
for some of these methods given our use of Multi in many places. Perhaps
MultiLeafReader could be a new class to hold these utilities?
I'd like to get these changes into 8.0, to further ween ourselves off of
MultiFields.
> Rename or move most of MultiFields
> ----------------------------------
>
> Key: LUCENE-7875
> URL: https://issues.apache.org/jira/browse/LUCENE-7875
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: David Smiley
> Priority: Major
>
> MultiFields.java has a bunch of static methods that provide a single
> LeafReader's view over a bunch of things.
> These could perhaps go to ReaderUtil:
> * {{Bits getLiveDocs(IndexReader reader)}}
> * {{FieldInfos getMergedFieldInfos(IndexReader reader)}} (removing "Merged"
> in its name which seems inconsistent, or replace with "Multi")
> These could perhaps go to MultiTerms:
> * {{Collection<String> getIndexedFields(IndexReader reader)}}
> * {{Terms getTerms(IndexReader r, String field)}}
> * {{PostingsEnum getTermDocsEnum(IndexReader r, String field, BytesRef term)}}
> Finally, the MultiFields instance itself, implementing {{Fields}} along with
> the static utility method {{Fields getFields(IndexReader reader)}} could
> perhaps remain until we can finally remove it (or move to a test classpath or
> something) when there is no more purpose for Fields.java.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
