Conversation
…port (apache#62737) ### What problem does this PR solve? support decoupled rf. (A join B) join (C join D) decoupled rf: B->C and B->D Issue Number: close #xxx Related PR: #xxx Problem Summary: ### Release note None ### Check List (For Author) - Test <!-- At least one of them must be included. --> - [ ] Regression test - [ ] Unit Test - [ ] Manual test (add detailed scripts or steps below) - [ ] No need to test or manual test. Explain why: - [ ] This is a refactor/code format and no logic has been changed. - [ ] Previous test can cover this change. - [ ] No code files have been changed. - [ ] Other reason <!-- Add your reason? --> - Behavior changed: - [ ] No. - [ ] Yes. <!-- Explain the behavior change --> - Does this need documentation? - [ ] No. - [ ] Yes. <!-- Add document PR link here. eg: apache/doris-website#1214 --> ### Check List (For Reviewer who merge this PR) - [ ] Confirm the release note - [ ] Confirm test cases - [ ] Confirm document - [ ] Add branch pick label <!-- Add branch pick label that this PR should merge into --> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…decoupled runtime filter Regenerated with -forceGenOut on branch-4.2 + apache#62737: tpcds_sf100 query31, tpcds_sf1000 queries 4/11/24/30/64/74/81, tpcds_sf10t_orc queries 4/11/18/31/54/74 and tpch_sf1000 q8/q9/q21.
Contributor
Author
|
run buildall |
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
FE UT Coverage ReportIncrement line coverage |
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cherry-pick of #62737 to branch-4.2
[feature](runtime filter) Add decoupled runtime filter support
Adaptations for branch-4.2:
RuntimeFilterConsumerkeeps branch-4.2'swait_infinitelycomputation (no BITMAP_FILTER term) and wraps it in the newdesc->__isset.wait_time_msbranch.RuntimeFilterTranslator/generator call branch-4.2'sPushDownContext.createPushDownContextForHashJoinfactory instead of master's unifiedcreatePushDownContext.@VariableMgr.VarAttr;runtimeFilterWaitInfinitelybecomes public as upstream requires.Testing: BE rebuilt with the BE-side changes and the FE+BE cluster restarted from this branch; regression suite nereids_syntax_p0/decoupled_runtime_filter passes. Known issue: the new FE unit test RuntimeFilterTest#testDecoupledRuntimeFilter does not reach the decoupled-RF shape on branch-4.2 (its 3-table join is planned differently than on master); the other 28 tests in that class pass.