FLASH-444: Fix stale table info in metadata #204
Merged
Conversation
This file contains 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
|
so, how could it work in the past ？ |
|
/run-integration-tests |
Our testing didn't cover Spark read after modify column in TiDB. We have add/drop/modify column UT in CI, and we did manual testing of Spark read after add/drop column. Neither of them has covered the case that triggers the bug. |
12 tasks
12 tasks
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.
When altering TMT table, refreshing metadata is using stale table info stored in storage object rather than the updated one, which results in query schema version (fetched from metadata) less than the in-memory storage schema version.
Now fix it to using the new one.