statistics: skip build statistics for view in auto analyze#27866
statistics: skip build statistics for view in auto analyze#27866ti-chi-bot merged 4 commits intopingcap:masterfrom
Conversation
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
|
@tiancaiamao does this pr need to cherry-pick? |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 8cc46ae |
|
/merge |
|
/run-check_dev_2 |
|
@tiancaiamao: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
What problem does this PR solve?
Issue Number: close #27274
I'm not sure will it also close #25898 and #26539, because in those two, the data race stack is lost.
After this fix, if we don't see them in the future, that means they are also fixed.
Problem Summary:
The DATA RACE happen between
explain view(or "select * from information_schema.columns") and auto-analyze.Auto analyze need to read the table column info, while 'explain view' will modify it.
tryFillViewColumnTypewill modify the column in model.TableInfo, It's not a operation on a copy of data.This operation is dangerous.
What is changed and how it works?
What's Changed:
View is a special table, it doesn't not need to maintain the statistics.
This commit skip build statistics for view.
How it Works:
Statistics will skip the view table, so it doesn't conflict with the
explain vieworselect * from infoschema.columns...Maybe change the
tryFillViewColumnTypefunction is another option, but this fix is obviously right, and just one line change.Check List
Tests
Side effects
Documentation
Release note