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

[Enhancement] pushdown runtime filter when cbo_agg_push is enabled and join type is broadcast and rf builded from colocate group (backport #52506) #52546

Merged
merged 1 commit into from
Nov 1, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 1, 2024

Why I'm doing:

fix tpcds bad case when agg pushdown enabled.

What I'm doing:

pushdown runtime filter to exchange node when rf is builded from broadcast join and colocate group.
Because the rf generated by broadcast join is full, it can be pushed down for this case like query58.

tpcds-100g q58 comparison results with agg_pushdown enabled

base optimized patch
2375 ms 465ms

this patch will not cause performance degradation of other tpcds queries by test.

Fixes #issue

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.3
    • 3.2
    • 3.1
    • 3.0
    • 2.5

This is an automatic backport of pull request #52506 done by [Mergify](https://mergify.com). ## Why I'm doing: fix tpcds bad case when agg pushdown enabled. ## What I'm doing: pushdown runtime filter to exchange node when rf is builded from broadcast join and colocate group. Because the rf generated by broadcast join is full, it can be pushed down for this case like query58.

tpcds-100g q58 comparison results with agg_pushdown enabled

base optimized patch
2375 ms 465ms

this patch will not cause performance degradation of other tpcds queries by test.

Fixes #issue

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

…d join type is broadcast and rf builded from colocate group (#52506)

Signed-off-by: stephen <[email protected]>
(cherry picked from commit aed02ae)
Copy link

sonarqubecloud bot commented Nov 1, 2024

@wanpengfei-git wanpengfei-git merged commit 86a484f into branch-3.3 Nov 1, 2024
34 of 35 checks passed
@wanpengfei-git wanpengfei-git deleted the mergify/bp/branch-3.3/pr-52506 branch November 1, 2024 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants