[jira] [Resolved] (LUCENE-7573) DocValuesConsumer.mergeSortedSetField should use different DV instances for ords and counts

["Adrien Grand (JIRA)" <ji...@apache.org>]

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

Adrien Grand resolved LUCENE-7573.
----------------------------------
       Resolution: Not A Problem
    Fix Version/s:     (was: 6.6)
                       (was: master (7.0))

No worries, I had forgotten about this issue too.

I double checked, and since we make sure to always consume all ordinals after having called {{setDocument}}, it should not be a problem. I don't think there is anything to do since it is not a bug in 6.x and the trap is removed in 7.0.


> DocValuesConsumer.mergeSortedSetField should use different DV instances for ords and counts
> -------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-7573
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7573
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Adrien Grand
>            Priority: Blocker
>
> Follow-up of LUCENE-7569 where we noticed that SORTED_SET doc values do not use a different underlying DV instance for ords and counts, which can cause bugs if both iterators are consumed at the same time.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org