[
https://issues.apache.org/jira/browse/SOLR-16212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lamine updated SOLR-16212:
--------------------------
Description:
Calling _deleteById_ in _DocBasedVersionConstraintsProcessor_ adds the
document (As tombstone) even if the doc does not exist.
I feel this is not solvable in the state of the art. The issue here is you
cannot make conclusion if the doc exist or not as concurrent updates can hit
the same doc some for deletes and other for add/update. Using _version_ field
to resolve version conflicts doesn't help unless we add a 4th option (something
like "{_}if request version > doc version"{_}) as opposed to the 3 existing
options (-1, 0, 1).
was:
Calling _deleteById_ in _DocBasedVersionConstraintsProcessor_ adds the
document (As tombstone) even if the doc does not exist.
> DocBasedVersionConstraintsProcessor's deleteById creates non existing docs
> --------------------------------------------------------------------------
>
> Key: SOLR-16212
> URL: https://issues.apache.org/jira/browse/SOLR-16212
> Project: Solr
> Issue Type: Bug
> Reporter: Lamine
> Priority: Minor
>
> Calling _deleteById_ in _DocBasedVersionConstraintsProcessor_ adds the
> document (As tombstone) even if the doc does not exist.
>
> I feel this is not solvable in the state of the art. The issue here is you
> cannot make conclusion if the doc exist or not as concurrent updates can hit
> the same doc some for deletes and other for add/update. Using _version_ field
> to resolve version conflicts doesn't help unless we add a 4th option
> (something like "{_}if request version > doc version"{_}) as opposed to the 3
> existing options (-1, 0, 1).
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
