Uh oh!
There was an error while loading. Please reload this page.
[fix](maxcompute)Fix MaxCompute IN predicate pushdown polarity. - #65083
Conversation
hello-stephen
commented
Jul 1, 2026
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
hubgeter
commented
Jul 1, 2026
run buildall |
hello-stephen
commented
Jul 1, 2026
FE UT Coverage ReportIncrement line coverage |
hello-stephen
commented
Jul 1, 2026
TPC-H: Total hot run time: 29429 ms |
hello-stephen
commented
Jul 1, 2026
TPC-DS: Total hot run time: 174228 ms |
hello-stephen
commented
Jul 1, 2026
ClickBench: Total hot run time: 25.26 s |
Gabriel39
commented
Jul 6, 2026
/review |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
There was a problem hiding this comment.
Review summary:
I found one blocking issue: the changed MaxCompute IN/NOT IN polarity branch is not covered by local FE tests, and the current PR head still has check_coverage_fe (Coverage) failing. The end-to-end MaxCompute regression is useful, but it is remote-gated and does not satisfy the FE coverage job.
Critical checkpoints:
- Goal: fixes MaxCompute IN predicate pushdown polarity; code maps non-negated IN to ODPS IN and NOT IN to ODPS NOT_IN.
- Scope: small and focused, limited to the converter plus a regression suite/output.
- Parallel paths: the newer connector MaxCompute predicate converter already uses matching polarity; no additional parallel-path issue found.
- Concurrency/lifecycle/persistence/config/protocol: not materially changed.
- Tests: remote regression added and expected output is ordered; local FE coverage for the changed Java branch is missing, matching the failing coverage check.
- Validation: static review plus GitHub PR metadata/checks; local FE build/tests were not run because this runner lacks
thirdparty/installed/bin/protoc.
Subagent conclusions: optimizer-rewrite found no new valuable findings; tests-session-config raised TSC-1, which was accepted as MAIN-1 and submitted as the inline comment. Final convergence round 1 ended with both subagents replying NO_NEW_VALUABLE_FINDINGS for the same ledger/comment set.
User focus: no additional user-provided review focus was supplied.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
fix maxcompute error in predicate pushdown.
…rity (#65083) (#64358) ### What problem does this PR solve? bp #65083 Problem Summary: fix maxcompute error in predicate pushdown. ### 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 -->
What problem does this PR solve?
Problem Summary:
fix maxcompute error in predicate pushdown.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)