[
https://issues.apache.org/jira/browse/LUCENE-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690044#comment-16690044
]
ASF subversion and git services commented on LUCENE-8552:
---------------------------------------------------------
Commit 0ed5cd5c3f97775567696f473579d0ad0623d749 in lucene-solr's branch
refs/heads/branch_7x from [~cbismuth]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=0ed5cd5 ]
LUCENE-8552: Optimize getMergedFieldInfos for zero or one segment
Closes #499
(cherry picked from commit db9542526ecc742234bff77d609a0f7071a78b46)
> optimize getMergedFieldInfos for one-segment FieldInfos
> -------------------------------------------------------
>
> Key: LUCENE-8552
> URL: https://issues.apache.org/jira/browse/LUCENE-8552
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: David Smiley
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> FieldInfos.getMergedFieldInfos could trivially return the FieldInfos of the
> first and only LeafReader if there is only one LeafReader.
> Also... if there is more than one LeafReader, and if FieldInfos & FieldInfo
> implemented equals() & hashCode() (including a cached hashCode), maybe we
> could also call equals() iterating through the FieldInfos to see if we should
> bother adding it to the FieldInfos.Builder? Admittedly this is speculative;
> may not be worth the bother.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
