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

[AilinKid]

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.

[lostcache]

/assign

[lostcache]

Hi @AilinKid , I went thought the community guidelines on how to craft PR/s and commit scoping but since I have changes across 34 files under tests/integrationtests/t, specifically in the following directories:

• globalindex
• planner
• executor

I would like guidance on how to best structure commits and pull requests to make the review process straightforward.

My initial plan is:

• One logical commit per directory (globalindex, planner, executor)
• One pull request per directory

If a different granularity is preferred (smaller commits per test category, or a single PR), please let me know. I am happy to restructure to match reviewer expectations.

[terry1purcell]

@lostcache - can you link your PR here? It's difficult to know how to answer your question. If you've made code changes and the testcases needed to be regenerated based upon those testcases - then they should all be within the same PR. If you are making testcase changes that are independent, it is reasonable to create separate PRs.

[lostcache]

Hi @terry1purcell , I haven't made a PR yet as I wanted some help to plan and avoid overwhelming a reviewer. I think I have a good idea on how to do it after your input. Since no testcases needs to be regenerated I will have one PR per independent testcase change.

Thanks for your quick response!