executor: disable runtime filter on join key type mismatch

[ChangRui-Ryan]

What problem does this PR solve?

Issue Number: close #10699

Problem Summary:

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None

Summary by CodeRabbit

• Bug Fixes

  • Runtime filters are now conservatively disabled when join key field types differ or signed/unsigned flags conflict; an informational log records the reason and empty filter lists are used to avoid incorrect pruning and preserve correct join results.

• Tests

  • Added tests validating runtime filters are disabled for multiple join key type-mismatch scenarios across execution modes, confirming execution plans and results remain unchanged.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign schrodingerzhu for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a conservative compatibility check that disables generation of join runtime filters when join key protobuf field types or integer signed/unsigned flags differ; runtime_filter_list is generated only when compatible (otherwise an empty list). Adds tests validating runtime filters are disabled for type-mismatch scenarios.

Changes

Cohort / File(s)	Summary
Runtime Filter Type Guard dbms/src/Flash/Planner/Plans/PhysicalJoin.cpp	Introduce is_join_key_field_type_compatible check for protobuf field-type and signed/unsigned compatibility; only call genRuntimeFilterList when compatible. Substitute an empty runtime_filter_list and emit an informational log when incompatible. Add #include <Flash/Coprocessor/DAGUtils.h> and explanatory comments.
Runtime Filter Type Mismatch Tests dbms/src/Flash/tests/gtest_runtime_filter_disable_on_type_mismatch.cpp	Add GoogleTest suite RuntimeFilterDisableOnTypeMismatchTestRunner (derives from ExecutorTest) and three tests: baseline, Int32 vs Int64 mismatch, Int32 vs UInt32 signed/unsigned mismatch. Tests assert runtime filters are disabled on mismatches and results match baseline across pipeline modes.

Sequence Diagram(s)

(Skipped)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Poem

🐇 I sniffed the left and sniffed the right,

When types or signs gave me a fright,
I paused my leap and left things be,
No filters jumping where they shouldn't be,
A cautious hop keeps joins carefree.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'executor: disable runtime filter on join key type mismatch' clearly and concisely summarizes the main change: disabling runtime filters when join key types don't match, which is the primary objective of this PR.
Description check	✅ Passed	The PR description follows the required template structure with Issue Number, checklist items (Unit and Integration tests marked), and side effects/documentation sections filled out appropriately.
Linked Issues check	✅ Passed	Changes implement the core requirement from #10699: preventing incorrect results by disabling runtime filters when join key types mismatch (signed vs unsigned integers), addressing the root cause of missing/extra rows.
Out of Scope Changes check	✅ Passed	All changes are directly scoped to the stated objective: PhysicalJoin.cpp adds type compatibility checking logic, and the new test file validates runtime filter disablement on type mismatches, with no extraneous modifications.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@dbms/src/Flash/Planner/Plans/PhysicalJoin.cpp`:
- Around line 173-212: Rename the snake_case local symbols to camelCase: change
the lambda is_join_key_field_type_compatible to isJoinKeyFieldTypeCompatible,
the bool enable_runtime_filter to enableRuntimeFilter, and runtime_filter_list
to runtimeFilterList; update the lambda invocation and its use sites (the const
bool assignment and the ternary that builds runtimeFilterList using
tiflash_join.genRuntimeFilterList) so all references match the new camelCase
names and keep behavior unchanged.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@dbms/src/Flash/tests/gtest_runtime_filter_disable_on_type_mismatch.cpp`:
- Around line 43-49: The loop variable name in the WrapForRuntimeFilterTestBegin
macro is declared as enablePipeline but the test code uses enable_pipeline,
causing a compile error; fix by making the identifier consistent—either change
the macro's loop variable to enable_pipeline or update all references (the
usages currently named enable_pipeline) to enablePipeline so the symbol matches,
ensuring WrapForRuntimeFilterTestBegin and all occurrences use the same
identifier.

🧹 Nitpick comments (2)

dbms/src/Flash/Planner/Plans/PhysicalJoin.cpp (1)

161-199: Conservative guard logic looks correct; minor style nit on redundant continue.

The lambda correctly checks:

1. Equal number of join keys
2. Both keys have valid field types
3. Same protobuf type (tp())
4. Same unsigned flag

One minor observation: the continue; on line 196 is redundant as it's at the end of the for-loop body.

🧹 Optional: remove redundant continue

             // Otherwise keep conservative: if we got here (same tp + same unsigned flag), treat as compatible.
-            continue;
         }
         return true;
     };

dbms/src/Flash/tests/gtest_runtime_filter_disable_on_type_mismatch.cpp (1)

43-49: Use the existing WRAP_FOR_TEST_BEGIN and WRAP_FOR_TEST_END macros from ExecutorTestUtils.h.

The file already imports ExecutorTestUtils.h and extends ExecutorTest, making it an executor test that should follow the established pattern. The custom WrapForRuntimeFilterTestBegin/End macros duplicate the existing WRAP_FOR_TEST_BEGIN/END macros and are already used consistently throughout other executor tests in dbms/src/Flash/tests/. Replace lines 43-49 with the standard macros to maintain consistency with the codebase pattern.

[ChangRui-Ryan]

/retest