Skip to content
This repository was archived by the owner on Mar 1, 2026. It is now read-only.

Skip drop system tables during clone drop user data#1501

Closed
luqun wants to merge 1 commit into
facebook:fb-mysql-8.0.32from
luqun:fb-mysql-8.0.32
Closed

Skip drop system tables during clone drop user data#1501
luqun wants to merge 1 commit into
facebook:fb-mysql-8.0.32from
luqun:fb-mysql-8.0.32

Conversation

@luqun

@luqun luqun commented Oct 24, 2024

Copy link
Copy Markdown
Contributor

For MyRocks DDSE, its system table doesn't have valid tablespace id, thus these system tables(such as mysql.user) in the recipient instance will be droped during drop user data stage. if at same time, some automations may check the instance and found out the instance doesn't have these important tables.

The change is to use table name to check whether these table are DD/systems tables

Summary:

Test Plan:

Reviewers:

Subscribers:

Tasks:

Tags:
Comment thread mysql-test/suite/rocksdb_clone/t/ddse_debug.test
@luqun luqun closed this Nov 7, 2024
facebook-github-bot pushed a commit that referenced this pull request Jan 22, 2025
Summary:
Skip drop system tables during clone drop user data

    For MyRocks DDSE, its system table doesn't have valid tablespace id, thus these system tables(such as mysql.user) in the recipient instance will be droped during drop user data stage. if at same time, some automations may check the instance and found out the instance doesn't have these important tables.

    The change is to use table name to check whether these table are DD/systems tables

    PR:#1501

fbshipit-source-id: 75a97f523d25f14d524a782e38dc2836557c8ed8
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

3 participants