Closed mergify[bot] closed 3 months ago
one driver's profile has its' operators profiles, and store them in:
typedef std::map<std::string, RuntimeProfile*> ChildMap; ChildMap _child_map;
so every operator has unique profile name, which is "operator name" + plan node id.
right now group execution(https://github.com/StarRocks/starrocks/pull/44771) can has pipelines below:
scan1->limit1->local exchange sink1 local exchange sourc 4->limit4->join probe4->limit4
the first limit 4 is infered by limit1, they have same limit size, first limit4 can be used for short-circuit
so limit 4 is not unique anymore. so add opeartor id for limit, then pipeline become:
scan1->limit1(14)->local exchange sink1 local exchange sourc 4->limit4(17)->join probe4->limit4(18)
Fixes #issue
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Issues 0 New issues 0 Accepted issues
Measures 0 Security Hotspots 0.0% Coverage on New Code 0.0% Duplication on New Code
See analysis details on SonarCloud
Why I'm doing:
one driver's profile has its' operators profiles, and store them in:
so every operator has unique profile name, which is "operator name" + plan node id.
right now group execution(https://github.com/StarRocks/starrocks/pull/44771) can has pipelines below:
the first limit 4 is infered by limit1, they have same limit size, first limit4 can be used for short-circuit
so limit 4 is not unique anymore. so add opeartor id for limit, then pipeline become:
What I'm doing:
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #47737 done by Mergify.
Why I'm doing:
one driver's profile has its' operators profiles, and store them in:
so every operator has unique profile name, which is "operator name" + plan node id.
right now group execution(https://github.com/StarRocks/starrocks/pull/44771) can has pipelines below:
the first limit 4 is infered by limit1, they have same limit size, first limit4 can be used for short-circuit
so limit 4 is not unique anymore. so add opeartor id for limit, then pipeline become:
What I'm doing:
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: