DB-12363: fix drop column and constraints(3.1) #5702
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
Author
|
jenkins please test branch @cdh6.3.0 |
Contributor
Author
|
jenkins please test branch @cdh6.3.0 |
Contributor
|
TEST SUCCEEDED +1 |
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.
Short Description
Fixes a regression from DB-12224
Long Description
DB-12224 introduced an upgrade scripts that recreate some system table indexes. For core system tables and indexes, splice stores their conglomerate number in zookeeper. The upgrade scripts needs to update them.
How to test
Deploy a pre-2024 build to create a splice database. Deploy 2025 build to upgrade database. Restart and run simple queries, such as show tables, select count(*) from sys.systable, from sqlshell.