infoschema: handle partition table for tables
#12591
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
Codecov Report
@@ Coverage Diff @@
## master #12591 +/- ##
===========================================
Coverage 79.9119% 79.9119%
===========================================
Files 460 460
Lines 104042 104042
===========================================
Hits 83142 83142
Misses 14811 14811
Partials 6089 6089 |
lzmhhh123
added
status/can-merge
|
/run-all-tests |
|
cherry pick to release-3.0 failed |
|
cherry pick to release-3.1 failed |
alivxxx
added a commit
to alivxxx/tidb
that referenced
this pull request
Oct 11, 2019
alivxxx
added a commit
to alivxxx/tidb
that referenced
this pull request
Oct 11, 2019
sre-bot
pushed a commit
that referenced
this pull request
Oct 12, 2019
ngaut
pushed a commit
that referenced
this pull request
Oct 12, 2019
XiaTianliang
pushed a commit
to XiaTianliang/tidb
that referenced
this pull request
Dec 21, 2019
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.
What problem does this PR solve?
When build fields lile
data_lengthforinformation_schema.tables, we need to handle partition tables, because every partition would have their own stats.What is changed and how it works?
Sum up each partition's info to build data length fields for table.
Check List
Tests
Code changes
Side effects
Related changes
Release note
information_schema.tables