Skip to content
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

DB-12364: update zookeeper property if a core system table index is recreated #5693

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jyuanca
Copy link

@jyuanca jyuanca commented Jul 19, 2021

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.

@jyuanca
Copy link
Author

jyuanca commented Jul 19, 2021

jenkins please test branch @cdh6.3.0

@cloudspliceci
Copy link
Contributor

@jyuanca
Copy link
Author

jyuanca commented Jul 19, 2021

jenkins please test branch @cdh6.3.0

@cloudspliceci
Copy link
Contributor

@@ -81,7 +81,7 @@ public SpliceCatalogUpgradeScripts(SpliceDataDictionary sdd, TransactionControll

scripts = new ArrayList<>();
addUpgradeScript(baseVersion4, 2020, new UpgradeAddConglomerateNumberIndex(sdd, tc));
addUpgradeScript(baseVersion4, 2024, new UpgradeScriptToPrioritizeSchemaIdInSystemIndices(sdd, tc));
addUpgradeScript(baseVersion4, 2024, new UpgradeScriptToPrioritizeSchemaIdInSystemIndices(sdd, tc, startParams));
// DB-11296: UpgradeConglomerateTable has to be executed first, because it adds a system table
Copy link
Contributor

@ipraznik-splice ipraznik-splice Jul 20, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my question is if should the version be changed to 2025 in this case? The migration was done for the previous build 2024, but fixed in 2025.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should still be 2024 in theory, because the index were changed since 2024, but we should recommend customer install 2025 build to trigger upgrade.

@jyuanca
Copy link
Author

jyuanca commented Jul 20, 2021

jenkins please test branch @cdh6.3.0

@cloudspliceci
Copy link
Contributor

@jyuanca
Copy link
Author

jyuanca commented Jul 20, 2021

jenkins please test branch @cdh6.3.0

@cloudspliceci
Copy link
Contributor

Copy link

@carolp-503 carolp-503 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants