failure with insert principal where 2 roles are created simultaneously with the same new member #2368
Conversation
This file contains 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
…y with the same new member Signed-off-by: Henry Avetisyan <hga@yahooinc.com>
abvaidya
approved these changes
Oct 22, 2023
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.
Description
further improvement for handling issue #2364
when we get 0 results or a duplicate exception, it's possible that when the server goes to read the principal id, the other transaction is not committed yet so it still returns no results. To handle this completely we now return a sql exception with conflict state and this gets converted into conflict resource exception and then the DB service class receives this exception it tries to retry the operation again.
Contribution Checklist:
Attach Screenshots (Optional)