[
https://issues.apache.org/jira/browse/LUCENE-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415339#comment-15415339
]
Yonik Seeley edited comment on LUCENE-7344 at 8/10/16 2:29 PM:
---------------------------------------------------------------
bq. 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.
For Solr, this can never happen (in solr-cloud mode at least)... All updates
are blocked during A DBQ, and then we re-open the reader before releasing the
lock.
All we need at the Solr level is to resolve DV updates *before* resolving
deletes (since we know that the DQB will always be last).
was (Author: [email protected]):
bq. 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.
For Solr, this can never happen... All updates are blocked during A DBQ, and
then we re-open the reader before releasing the lock.
All we need at the Solr level is to resolve DV updates *before* resolving
deletes (since we know that the DQB will always be last).
> 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, 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: [email protected]
For additional commands, e-mail: [email protected]
