-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Objects should be owned by schema owner in Babelfish #3560
Merged
shardgupta
merged 39 commits into
babelfish-for-postgresql:BABEL_4_X_DEV
from
amazon-aurora:jira-babel-5361-4x
Mar 20, 2025
Merged
Objects should be owned by schema owner in Babelfish #3560
shardgupta
merged 39 commits into
babelfish-for-postgresql:BABEL_4_X_DEV
from
amazon-aurora:jira-babel-5361-4x
Mar 20, 2025
+4,085
−176
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
Pull Request Test Coverage Report for Build 13929337773Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
tanscorpio7
suggested changes
Mar 12, 2025
HarshLunagariya
suggested changes
Mar 18, 2025
HarshLunagariya
approved these changes
Mar 19, 2025
tanscorpio7
approved these changes
Mar 19, 2025
shardgupta
approved these changes
Mar 20, 2025
d35674f
into
babelfish-for-postgresql:BABEL_4_X_DEV
48 checks passed
shalinilohia50
added a commit
to amazon-aurora/babelfish_extensions
that referenced
this pull request
Mar 20, 2025
…ostgresql#3560) When a new object is created in Babelfish, its owner should be same as its schema owner. Upgrade approach: Older objects will continue to have the owner (which can be different than the schema owner). There are functions provided to check the objects where there is owner mismatch between object and its schema. User can run the scripts and update the ownership themselves. Task: BABEL-5361 Signed-off-by: Shalini Lohia [email protected]
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
When a new object is created in Babelfish, its owner should be same as its schema owner.
Upgrade approach:
Issues Resolved
Task: BABEL-5361
Signed-off-by: Shalini Lohia [email protected]
Test Scenarios Covered