ddl: Fix rename come after database has been dropped (#9274) #9276
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.
This is an automated cherry-pick of #9274
What problem does this PR solve?
Issue Number: close #9266
Problem Summary:
In
InterpreterRenameQuery
, it usecontext.getDatabase
which will throw an exception if the database instance is not exist in tiflash.The database has been dropped in TiDB before TiFlash sync the schema diff of "create database". And the following rename table to that database (database_id=170) throw exception.
What is changed and how it works?
In
SchemaBuilder::applyRenamePhysicalTable
it should create a local IDatabase instance with a "fake" DBInfo if can not fetch from TiKV.Check List
Tests
Side effects
Documentation
Release note