-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[opt](nereids) when we check if there is a target for runtime filter, we should use ctx.probeSlot not ctx.probeExpr #57425
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
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
FE Regression Coverage ReportIncrement line coverage |
|
run feut |
|
run external |
FE UT Coverage ReportIncrement line coverage |
|
run external |
67a08bc to
45313c7
Compare
|
PR approved by anyone and no changes requested. |
|
run buildall |
TPC-H: Total hot run time: 34159 ms |
TPC-DS: Total hot run time: 188478 ms |
ClickBench: Total hot run time: 27.26 s |
FE Regression Coverage ReportIncrement line coverage |
|
PR approved by at least one committer and no changes requested. |
… we should use ctx.probeSlot not ctx.probeExpr (apache#57425) ### What problem does this PR solve? when we check if there is a target for runtime filter, we should use ctx.probeSlot not ctx.probeExpr
What problem does this PR solve?
when we check if there is a target for runtime filter, we should use ctx.probeSlot not ctx.probeExpr
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)