-
Notifications
You must be signed in to change notification settings - Fork 1.2k
engine/schema: create default network offering for vpc tier with conserve_mode=1 for fresh installation #10744
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so only this needs backporting to 4.19?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this part, and also the SQL to 4.19.2->4.19.3 upgrade schema
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
checked with Pearl, currently therre is no upgrade path for 4.19.2 to 4.19.3
old envs deployed before 4.19.0 will be good when they upgrade to 4.19.0 or later
the impacted versions are old envs deployed with 4.19.0/4.19.1/4.19.2
they will be good when upgrade to 4.20.1
but they will have the issue when upgade to 4.19.3, if we do not add upgrade path with db change
the db change is quite simple ..
we can backport the java change to 4.19.3, so 4.19.3 fresh env will be fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, I have a bit of an issue with backporting the sql change, not of principle but because there is no other reason to create an upgrade path yet. I think this issue is too low priority to create the upgrade path for the sake of it. what do you think @Pearl1594 @weizhouapache ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree @DaanHoogland
maybe you can add SQL changes to the description of the PR #10843
in case someone want the fix in 4.19.1/2/3, they can execute the SQL