[
https://issues.apache.org/jira/browse/LUCENE-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413364#comment-15413364
]
Shai Erera commented on LUCENE-7344:
------------------------------------
After chatting with Mike about this, here's an example for an "interleaving"
case that Mike mentioned, where this patch does not work:
{code}
writer.updateNumericDocValue(new Term("id", "doc-1"), "val", 17L);
writer.deleteDocuments(DocValuesRangeQuery.newLongRange("val", 5L, 10L,
true, true));
writer.updateNumericDocValue(new Term("id", "doc-1"), "val", 7L);
{code}
Here, "doc-1" should not be deleted, because the DBQ is submitted before the DV
update, but because we resolve all DV updates before DBQ (in this patch), it
ends up deleted. This is wrong of course. I'm looking into Mike's other idea of
having a LeafReader view with the DV updates up until that document, and then
ensuring DV updates / DBQs are applied in the order they were submitted. This
starts to get very complicated.
> Deletion by query of uncommitted docs not working with DV updates
> -----------------------------------------------------------------
>
> Key: LUCENE-7344
> URL: https://issues.apache.org/jira/browse/LUCENE-7344
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Ishan Chattopadhyaya
> Attachments: LUCENE-7344.patch, LUCENE-7344.patch
>
>
> When DVs are updated, delete by query doesn't work with the updated DV value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
