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

planner: move more methods from StatsHandle to its sub-packages #47760

Merged
merged 13 commits into from
Oct 19, 2023

Conversation

qw4990
Copy link
Contributor

@qw4990 qw4990 commented Oct 18, 2023

What problem does this PR solve?

Issue Number: ref #46905

Problem Summary: planner: move more methods from StatsHandle to its sub-packages

What is changed and how it works?

planner: move more methods from StatsHandle to its sub-packages

No logical change, just refactor.

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No need to test
    • I checked and no code files have been changed.

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

Please refer to Release Notes Language Style Guide to write a quality release note.

None

@ti-chi-bot ti-chi-bot bot added needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. release-note-none Denotes a PR that doesn't merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Oct 18, 2023
@tiprow
Copy link

tiprow bot commented Oct 18, 2023

Hi @qw4990. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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 kubernetes/test-infra repository.

@qw4990 qw4990 removed the needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. label Oct 18, 2023
@codecov
Copy link

codecov bot commented Oct 18, 2023

Codecov Report

Merging #47760 (ae8343d) into master (ac1f0d9) will increase coverage by 0.9103%.
Report is 4 commits behind head on master.
The diff coverage is 89.5522%.

Additional details and impacted files
@@               Coverage Diff                @@
##             master     #47760        +/-   ##
================================================
+ Coverage   71.8931%   72.8035%   +0.9103%     
================================================
  Files          1398       1421        +23     
  Lines        405200     411590      +6390     
================================================
+ Hits         291311     299652      +8341     
+ Misses        94269      93093      -1176     
+ Partials      19620      18845       -775     
Flag Coverage Δ
integration 41.4957% <32.8358%> (?)
unit 71.8658% <89.5522%> (-0.0274%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
dumpling 53.9913% <ø> (ø)
parser ∅ <ø> (∅)
br 48.6844% <ø> (-4.2491%) ⬇️

@ti-chi-bot ti-chi-bot bot added the needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. label Oct 18, 2023
@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Oct 18, 2023
@ti-chi-bot ti-chi-bot bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Oct 18, 2023
@qw4990
Copy link
Contributor Author

qw4990 commented Oct 19, 2023

/test check-dev

@tiprow
Copy link

tiprow bot commented Oct 19, 2023

@qw4990: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test check-dev

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 kubernetes/test-infra repository.

@ti-chi-bot
Copy link

ti-chi-bot bot commented Oct 19, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrysan, hawkingrei

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

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the lgtm label Oct 19, 2023
@ti-chi-bot ti-chi-bot bot removed the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Oct 19, 2023
@ti-chi-bot
Copy link

ti-chi-bot bot commented Oct 19, 2023

[LGTM Timeline notifier]

Timeline:

  • 2023-10-18 13:47:23.280390347 +0000 UTC m=+1837640.867500491: ☑️ agreed by chrysan.
  • 2023-10-19 06:18:01.536718393 +0000 UTC m=+1897079.123828538: ☑️ agreed by hawkingrei.

@ti-chi-bot ti-chi-bot bot merged commit 6dea081 into pingcap:master Oct 19, 2023
12 of 15 checks passed
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch release-7.5: #47783.

ti-chi-bot pushed a commit to ti-chi-bot/tidb that referenced this pull request Oct 19, 2023
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. release-note-none Denotes a PR that doesn't merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants