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.

Sign up for GitHub

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

Jump to bottom

update default value of tidb_analyze_version in v5.1 and v5.2 (#8411) #8551

Merged
merged 7 commits into from
Apr 26, 2022
Merged

update default value of tidb_analyze_version in v5.1 and v5.2 (#8411) #8551

merged 7 commits into from
Apr 26, 2022

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #8411

What is changed, added or deleted? (Required)

update default value of tidb_analyze_version in v5.1 and v5.2

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions (in Chinese).

  • master (the latest development version)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)
  • v5.2 (TiDB 5.2 versions)
  • v5.1 (TiDB 5.1 versions)
  • v5.0 (TiDB 5.0 versions)
  • v4.0 (TiDB 4.0 versions)
  • v3.1 (TiDB 3.1 versions)
  • v3.0 (TiDB 3.0 versions)
  • v2.1 (TiDB 2.1 versions)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot
Copy link
Member Author

ti-chi-bot commented Mar 3, 2022 •
edited
Loading

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • TomShawn

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.

@ti-chi-bot ti-chi-bot added area/planner Indicates that the Issue or PR belongs to the area of SQL planner or optimizer. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Mar 3, 2022
@ti-chi-bot ti-chi-bot mentioned this pull request Mar 3, 2022
Merged
14 tasks
@ti-chi-bot ti-chi-bot added type/cherry-pick-for-release-5.2 This PR is cherry-picked to release-5.2 from a source PR. type/compatibility-or-feature-change This PR involves compatibility changes or feature behavior changes. labels Mar 3, 2022
@ti-chi-bot ti-chi-bot requested a review from TomShawn March 3, 2022 03:04
@TomShawn TomShawn added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 3, 2022
@VelocityLight VelocityLight added the cherry-pick-approved Cherry pick PR approved by release team. label Apr 12, 2022
TomShawn
TomShawn reviewed Apr 13, 2022
View reviewed changes
statistics.md Outdated Show resolved Hide resolved
TomShawn
TomShawn reviewed Apr 13, 2022
View reviewed changes
statistics.md Outdated Show resolved Hide resolved
TomShawn
TomShawn reviewed Apr 13, 2022
View reviewed changes
system-variables.md Outdated Show resolved Hide resolved
TomShawn
TomShawn reviewed Apr 13, 2022
View reviewed changes
system-variables.md Outdated Show resolved Hide resolved
TomShawn
TomShawn reviewed Apr 13, 2022
View reviewed changes
system-variables.md Outdated Show resolved Hide resolved
@shichun-0415 shichun-0415 requested review from yiwen92 and removed request for TomShawn April 13, 2022 07:00
yiwen92
yiwen92 approved these changes Apr 13, 2022
View reviewed changes
Copy link
Contributor

@yiwen92 yiwen92 left a comment

Choose a reason for hiding this comment

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

LGTM

@yiwen92 yiwen92 mentioned this pull request Apr 13, 2022
Merged
12 tasks
@VelocityLight VelocityLight added do-not-merge/cherry-pick-not-approved and removed cherry-pick-approved Cherry pick PR approved by release team. labels Apr 18, 2022
@TomShawn TomShawn removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 26, 2022
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Apr 26, 2022
@TomShawn
Copy link
Contributor

/merge

@ti-chi-bot
Copy link
Member Author

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

Commit hash: eeb1632

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Apr 26, 2022
@ti-chi-bot ti-chi-bot merged commit 5be21c4 into pingcap:release-5.2 Apr 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@TomShawn TomShawn TomShawn approved these changes

@yiwen92 yiwen92 yiwen92 approved these changes

Assignees

@TomShawn TomShawn

Labels
area/planner Indicates that the Issue or PR belongs to the area of SQL planner or optimizer. do-not-merge/cherry-pick-not-approved size/S Denotes a PR that changes 10-29 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1. type/cherry-pick-for-release-5.2 This PR is cherry-picked to release-5.2 from a source PR. type/compatibility-or-feature-change This PR involves compatibility changes or feature behavior changes.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ti-chi-bot @TomShawn @yiwen92 @VelocityLight