pingcap/tidb

some explain test case should ignore plan-id in the result file

Open

#60940 opened on Apr 29, 2025

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Go (40,090 stars) (6,186 forks)batch import
good first issuesig/plannertype/enhancement

Description

Enhancement

Some explain-test cases will record the plan ID in the result file, which will be a burden when some optimization flow is changed, since plan ID allocation is sequential according to the allocation order or space.

Contributor guide

Tech stack
gosql
Domain
databasetesting
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingTiDB test framework
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Look at the explain test cases in the TiDB repository, likely in the `tests/integration tests` or similar directories. The plan id appears in expected output files. The goal is to ignore the specific plan id field in comparisons, possibly by using a placeholder or by modifying the test framework to skip that field. Check existing test patterns that handle non deterministic output. The fix likely involves updating the test case files or the test runner to strip out plan id values before comparison.