[
https://issues.apache.org/jira/browse/SOLR-16218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552336#comment-17552336
]
Anshum Gupta commented on SOLR-16218:
-------------------------------------
Assigning to myself as I was speaking with Lamine about it at work.
> failOnVersionConflicts not working on in-place updates
> ------------------------------------------------------
>
> Key: SOLR-16218
> URL: https://issues.apache.org/jira/browse/SOLR-16218
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Lamine
> Assignee: Anshum Gupta
> Priority: Minor
>
>
> *Description*
> Fix a bug in in-place update when _failOnVersionConflicts_=false.
> When sending in-place/atomic updates for a non-existent doc with
> __version_=1_ Solr throws 409 error even if _failOnVersionConflicts_ is set
> to _false_.
>
> *Steps to Reproduce*
> - Send an update request (single or batch) that includes Update
> in-place/atomic command of a non-existent doc.
> - Set _Version_=1
> - Solr will throw 409 exception with "_Document not found for update_"
> message error.
> Set failOnVersionConflicts=false
> - Solr still throws the same error.
>
> *Expected*
> if _failOnVersionConflicts=false_ Solr should ignore the error silently and
> continue processing the rest of the commands.
> *Actual Result*
> Solr throws 409 exception with "_Document not found for update_" message
> error.
> *Solution*
> Check in _getUpdatedDocument_ if _failOnVersionConflicts=true_ before
> throwing the exception.
> *Tests*
> Added test cases catching the expected behavior when
> __failOnVersionConflicts_ is set to _true_ or _false_ (default is true).
>
--
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
