[
https://issues.apache.org/jira/browse/LUCENE-9113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008604#comment-17008604
]
ASF subversion and git services commented on LUCENE-9113:
---------------------------------------------------------
Commit dcc01fdaa6841a94613f68b419799523a157fe4a in lucene-solr's branch
refs/heads/master from Adrien Grand
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=dcc01fd ]
LUCENE-9113: Speed up merging doc values' terms dictionaries. (#1136)
> Speed up merging doc values terms dictionaries
> ----------------------------------------------
>
> Key: LUCENE-9113
> URL: https://issues.apache.org/jira/browse/LUCENE-9113
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The default {{DocValuesConsumer#mergeSortedField}} and
> {{DocValuesConsumer#mergeSortedSetField}} implementations create a merged
> view of the doc values producers to merge. Unfortunately, it doesn't override
> {{termsEnum()}}, whose default implementation of {{next()}} increments the
> ordinal and calls {{lookupOrd()}} to retrieve the term. Currently,
> {{lookupOrd()}} doesn't take advantage of its current position, and would
> seek to the block start and then call {{next()}} up to 16 times to go to the
> desired term. While there are discussions to optimize lookups to take
> advantage of the current ord (LUCENE-8836), it shouldn't be required for
> merging to be efficient and we should instead make {{next()}} call {{next()}}
> on its sub enums.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
