Fix error handling for existing entries in CreateIfNotExistsNamespace #75
Conversation
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
…ix pvc no permission of user Kvrocks
…ix pvc no permission of user Kvrocks
…to 'already exists'
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
This PR improves the error handling logic in the CreateIfNotExistsNamespace function. Specifically:
It ensures that the error message check for existing entries is more robust and consistent.
Refactors the condition to handle both "the entry already existed" and "already exists" messages.
Changes: Updated the conditional logic in CreateIfNotExistsNamespace to handle specific error messages more effectively.