Fixed guardrail check for super user permission and the query for checking if schema exist in case of YB Aeon #2051
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
… checking if schema exist in case of YB Aeon
priyanshi-yb
changed the title
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.
Describe the changes in this pull request
Fixing a few bugs with import schema and YB Aeon type of target db, the difference in behavior is because of yb_superuser with YB Aeon which has a subset of superuser's privileges.
issues are detailed in this ticket
https://yugabyte.atlassian.net/browse/DB-14398
Fixes - #2050
Describe if there are any user-facing changes
No
How was this pull request tested?
Manually with YB Aeon
Does your PR have changes that can cause upgrade issues?