statistics: skip build statistics for view in auto analyze

[tiancaiamao]

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.
tryFillViewColumnType will 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 view or select * from infoschema.columns ...

Maybe change the tryFillViewColumnType function is another option, but this fix is obviously right, and just one line change.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• lzmhhh123
• wjhuang2016

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[lzmhhh123]

@tiancaiamao does this pr need to cherry-pick?

[tiancaiamao]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 8cc46ae

[tiancaiamao]

/merge

[tiancaiamao]

/run-check_dev_2

[ti-chi-bot]

@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.

Instructions 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.