SOLR-16218: Fix bug in in-place update when failOnVersionConflicts=false#898
Merged
anshumg merged 1 commit intoapache:mainfrom Jun 10, 2022
Conversation
anshumg
approved these changes
Jun 9, 2022
anshumg
added a commit
that referenced
this pull request
Jun 12, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://issues.apache.org/jira/browse/SOLR-16218
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
Set failOnVersionConflicts=false
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).
Checklist
Please review the following and check all that apply:
mainbranch../gradlew check.