You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ishan Chattopadhyaya (JIRA)" <ji...@apache.org> on 2017/05/22 21:10:05 UTC
[jira] [Comment Edited] (LUCENE-7573)
DocValuesConsumer.mergeSortedSetField should use different DV instances for
ords and counts
[ https://issues.apache.org/jira/browse/LUCENE-7573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020210#comment-16020210 ]
Ishan Chattopadhyaya edited comment on LUCENE-7573 at 5/22/17 9:09 PM:
-----------------------------------------------------------------------
[~jpountz], are we planning to have this for 6.6, or may I downgrade priority to a Major instead of Blocker? I'm fine waiting with 6.6 if you think this is important. Sorry, I didn't realize this isue was there before cutting the RC1.
was (Author: ichattopadhyaya):
[~jpountz], are we planning to have this for 6.6, or may I downgrade priority to a Major instead of Blocker?
> 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
> Fix For: master (7.0), 6.6
>
>
> 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