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: fix index merge shouldn't push partial limit down when index plans are keep ordered (#52979) #53149

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #52979

What problem does this PR solve?

Issue Number: close #52947

Problem Summary:
#52947 (comment)

What changed and how does it work?

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.

planner: fix index merge shouldn't push partial limit down when index plans are keep ordered

… keep ordered

Signed-off-by: AilinKid <314806019@qq.com>
Signed-off-by: AilinKid <314806019@qq.com>
Signed-off-by: AilinKid <314806019@qq.com>
@@ -893,6 +895,10 @@ func (p *PhysicalLimit) attach2Task(tasks ...task) task {
cop.idxMergePartPlans = limitChildren
t = cop.convertToRootTask(p.SCtx())
sunk = p.sinkIntoIndexMerge(t)
} else {
// when there are some limitations, just sink the limit upon the index merge reader.
t = cop.ConvertToRootTask(p.SCtx())
Copy link
Contributor

Choose a reason for hiding this comment

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

no this method.

Copy link
Contributor

Choose a reason for hiding this comment

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

i will take a look

Signed-off-by: AilinKid <314806019@qq.com>
Copy link

codecov bot commented May 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (release-8.1@5216ddb). Click here to learn what that means.

Additional details and impacted files
@@               Coverage Diff                @@
##             release-8.1     #53149   +/-   ##
================================================
  Coverage               ?   71.1671%           
================================================
  Files                  ?       1463           
  Lines                  ?     420767           
  Branches               ?          0           
================================================
  Hits                   ?     299448           
  Misses                 ?     100862           
  Partials               ?      20457           
Flag Coverage Δ
unit 71.1671% <100.0000%> (?)

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

Components Coverage Δ
dumpling 53.9957% <0.0000%> (?)
parser ∅ <0.0000%> (?)
br 40.9718% <0.0000%> (?)

Copy link

ti-chi-bot bot commented May 10, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, Defined2014

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:
  • OWNERS [AilinKid,Defined2014]

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

Copy link

ti-chi-bot bot commented May 10, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-05-10 03:09:37.776344302 +0000 UTC m=+1190731.533479871: ☑️ agreed by Defined2014.
  • 2024-05-10 05:00:52.986732814 +0000 UTC m=+1197406.743868379: ☑️ agreed by AilinKid.

@ti-chi-bot ti-chi-bot bot merged commit 53e5f74 into pingcap:release-8.1 May 10, 2024
18 checks passed
@wuhuizuo wuhuizuo deleted the cherry-pick-52979-to-release-8.1 branch May 11, 2024 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved cherry-pick-approved Cherry pick PR approved by release team. lgtm ok-to-test release-note sig/planner SIG: Planner size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-8.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants