lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7875) Rename or move most of MultiFields
Date Thu, 18 Oct 2018 23:50:00 GMT


ASF subversion and git services commented on LUCENE-7875:

Commit fd9164801e703b278922dae6cc3c53e0578fa1d6 in lucene-solr's branch refs/heads/master
from [~dsmiley]
[;h=fd91648 ]

LUCENE-7875: Moved MultiFields static methods to MultiTerms, FieldInfos and MultiBits.
MultiBits is now public and has getLiveDocs.

> Rename or move most of MultiFields
> ----------------------------------
>                 Key: LUCENE-7875
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Minor
>             Fix For: master (8.0)
>         Attachments: LUCENE-7875.patch, LUCENE-7875.patch, LUCENE-7875.patch, LUCENE-7875.patch
> 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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message