planner: migrate testdata-backed EXPLAIN tests to format='plan_tree'

[henrybw]

What problem does this PR solve?

Issue Number: ref #67112

Problem Summary: Test cases that rely on EXPLAIN output in format='brief' or format='verbose', but only need to validate the structure of the plan, are brittle and will start failing if minor changes in row estimates or table schema occur. This requires regenerating a large number of new plans for optimizer tests when making changes, adding noise to PR diffs and obscuring potential problems that these tests may have otherwise caught.

What changed and how does it work?

Convert EXPLAIN tests that use testdata recorded from format='brief' to format='plan_tree', and re-record their output:

• runtime_filter_generator_test.go + testdata
• operator/logicalop/logicalop_test/ + testdata
• casetest/cascades/ + testdata
• casetest/integration_test.go
• casetest/partition/partition_pruner_test.go
• casetest/plancache/plan_cache_partition_test.go

Check List

Tests

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

  • I checked and no code files have been changed.

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

Please refer to Release Notes Language Style Guide to write a quality release note.

None

Summary by CodeRabbit

• Tests

  • Updated query plan validation tests to use an improved explain format for better consistency and clarity across test suites.

• Chores

  • Refreshed expected test outputs across multiple test data files to align with updated plan formatting standards.

[pantheon-ai]

Review Complete

Findings: 0 issues
Posted: 0
Duplicates/Skipped: 0

_{ℹ️ Learn more details on Pantheon AI.}

[tiprow]

Hi @henrybw. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: c4fb08fb-4f1a-4a60-88d3-f833a4213ae3

📥 Commits

Reviewing files that changed from the base of the PR and between 8412422 and 573b4c4.

📒 Files selected for processing (11)

• pkg/planner/core/casetest/cascades/memo_test.go
• pkg/planner/core/casetest/cascades/testdata/cascades_template_out.json
• pkg/planner/core/casetest/cascades/testdata/cascades_template_xut.json
• pkg/planner/core/casetest/integration_test.go
• pkg/planner/core/casetest/partition/partition_pruner_test.go
• pkg/planner/core/casetest/plancache/plan_cache_partition_test.go
• pkg/planner/core/operator/logicalop/logicalop_test/logical_operator_test.go
• pkg/planner/core/operator/logicalop/logicalop_test/testdata/cascades_suite_out.json
• pkg/planner/core/operator/logicalop/logicalop_test/testdata/cascades_suite_xut.json
• pkg/planner/core/runtime_filter_generator_test.go
• pkg/planner/core/testdata/runtime_filter_generator_suite_out.json

---

📝 Walkthrough

Walkthrough

This PR updates planner core unit tests to use EXPLAIN format='plan_tree' instead of EXPLAIN format='brief', and correspondingly updates all expected test output data to match the new format. Plan representations are reformatted to remove numeric cost annotations and normalize column identifiers.

Changes

Cohort / File(s)	Summary
Test File Format Migration pkg/planner/core/casetest/cascades/memo_test.go, pkg/planner/core/casetest/integration_test.go, pkg/planner/core/casetest/partition/partition_pruner_test.go, pkg/planner/core/casetest/plancache/plan_cache_partition_test.go, pkg/planner/core/operator/logicalop/logicalop_test/logical_operator_test.go, pkg/planner/core/runtime_filter_generator_test.go	Updated test assertions to generate and validate query plans using EXPLAIN format='plan_tree' instead of format='brief'.
Testdata Plan Output Updates pkg/planner/core/casetest/cascades/testdata/cascades_template_out.json, pkg/planner/core/casetest/cascades/testdata/cascades_template_xut.json, pkg/planner/core/operator/logicalop/logicalop_test/testdata/cascades_suite_out.json, pkg/planner/core/operator/logicalop/logicalop_test/testdata/cascades_suite_xut.json, pkg/planner/core/testdata/runtime_filter_generator_suite_out.json	Updated expected plan strings by removing numeric cost/cardinality prefixes (e.g., 1.00, 6400.00), normalizing column identifiers from specific numbers to generic Column placeholders, and reformatting node descriptors while preserving operator hierarchy and expressions.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• planner: migrate unit tests checking EXPLAIN output to format='plan_tree' #67479: Performs the same migration of planner unit tests from format='brief' to format='plan_tree' with corresponding testdata updates across the same test files.
• planner: align core casetests with plan_tree #67113: Makes identical code-level changes switching planner casetests in pkg/planner/core/casetest to format='plan_tree' with re-recorded expected plan text testdata.
• planner: use ExplainInfo/StringWithCtx for columns in EXPLAIN output paths #67340: Modifies the underlying plan_tree output formatting (removing numeric Column#N identifiers) that these test updates validate against.

Suggested labels

sig/planner, size/XXL, ok-to-test

Suggested reviewers

• hawkingrei
• qw4990
• AilinKid

Poem

🐰 The planner tests now dance in trees,
No cost or column numbers please!
From brief to plan_tree we leap with glee,
Reformatted rows, a sight to see! 🌳✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

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

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title clearly and concisely summarizes the main change: migrating testdata-backed EXPLAIN tests from brief format to plan_tree format.
Description check	✅ Passed	The pull request description follows the template structure, includes a referenced issue number, explains the problem and solution, and marks appropriate test checkboxes. All required sections are present and adequately filled.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.11.4)

Command failed

---

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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.5459%. Comparing base (8412422) to head (573b4c4).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #67502        +/-   ##
================================================
- Coverage   77.7173%   77.5459%   -0.1714%     
================================================
  Files          1959       1943        -16     
  Lines        543377     543390        +13     
================================================
- Hits         422298     421377       -921     
- Misses       120238     122011      +1773     
+ Partials        841          2       -839     

Flag	Coverage Δ
integration	40.9439% <ø> (+4.7691%)	⬆️
unit	76.7046% <ø> (+0.3615%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	61.5065% <ø> (ø)
parser	∅ <ø> (∅)
br	48.9074% <ø> (-12.0727%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pantheon-ai]

✅ Code looks good. No issues found.

[henrybw]

/retest-required

[tiprow]

@henrybw: PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test.

Details

In response to this:

/retest-required

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, qw4990

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• pkg/planner/OWNERS [hawkingrei,qw4990]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-04-02 01:56:01.062408046 +0000 UTC m=+402966.267768103: ☑️ agreed by hawkingrei.
• 2026-04-02 02:50:15.707833415 +0000 UTC m=+406220.913193462: ☑️ agreed by qw4990.

[hawkingrei]

/retest

[hawkingrei]

/retest

[hawkingrei]

/retest