Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

infoschema: remove the ID and NAME columns of TIDB_CLUSTER_INFO #13587

Merged
merged 3 commits into from
Nov 19, 2019
Merged

infoschema: remove the ID and NAME columns of TIDB_CLUSTER_INFO #13587

merged 3 commits into from
Nov 19, 2019

Conversation

lonng
Copy link
Contributor

@lonng lonng commented Nov 19, 2019

Signed-off-by: Lonng heng@lonng.org

What problem does this PR solve?

Fix issue #13586

What is changed and how it works?

We should remove the NAME and ID columns of TIDB_CLUSTER_INFO system table because they are not the real stable value for cluster topology according to

name := fmt.Sprintf("%s-%d", tp, len(rows))
.

Check List

Tests

  • Unit test

Release note

  • No need.

@lonng lonng added the type/enhancement The issue or PR belongs to an enhancement. label Nov 19, 2019
@lonng
Copy link
Contributor Author

lonng commented Nov 19, 2019

/run-unit-test

@codecov
Copy link

codecov bot commented Nov 19, 2019

Codecov Report

Merging #13587 into master will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master     #13587   +/-   ##
===========================================
  Coverage   79.9494%   79.9494%           
===========================================
  Files           472        472           
  Lines        115817     115817           
===========================================
  Hits          92595      92595           
  Misses        15974      15974           
  Partials       7248       7248

Copy link
Contributor

@zimulala zimulala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zimulala zimulala added the status/LGT1 Indicates that a PR has LGTM 1. label Nov 19, 2019
Copy link
Contributor

@crazycs520 crazycs520 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crazycs520
Copy link
Contributor

/run-all-tests

@lonng
Copy link
Contributor Author

lonng commented Nov 19, 2019

/merge

@sre-bot sre-bot added the status/can-merge Indicates a PR has been approved by a committer. label Nov 19, 2019
@sre-bot
Copy link
Contributor

sre-bot commented Nov 19, 2019

/run-all-tests

@sre-bot sre-bot merged commit f344958 into pingcap:master Nov 19, 2019
@lonng lonng added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants