You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2018/11/16 22:01:00 UTC

[jira] [Resolved] (LUCENE-8552) optimize getMergedFieldInfos for one-segment FieldInfos

     [ https://issues.apache.org/jira/browse/LUCENE-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Smiley resolved LUCENE-8552.
----------------------------------
       Resolution: Fixed
         Assignee: David Smiley
    Fix Version/s: 7.7

Thanks for contributing!

> 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
>            Assignee: David Smiley
>            Priority: Minor
>             Fix For: 7.7
>
>          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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org