You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Adrien Grand (Jira)" <ji...@apache.org> on 2020/01/02 10:39:00 UTC

[jira] [Updated] (LUCENE-9113) Speed up merging doc values terms dictionaries

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

Adrien Grand updated LUCENE-9113:
---------------------------------
    Issue Type: Improvement  (was: Bug)

> 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
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org