Skip to content

[hotfix][docs] Document node digests and golden-file traps in the planner AGENTS.md - #29240

Draft
MartijnVisser wants to merge 1 commit into
apache:masterfrom
MartijnVisser:hotfix-planner-agents-md
Draft

MartijnVisser wants to merge 1 commit into
apache:masterfrom
MartijnVisser:hotfix-planner-agents-md

Conversation

@MartijnVisser

Copy link
Copy Markdown
Contributor

What is the purpose of the change

Brief change log

  • Node digest bullet under Key Abstractions
  • Plan-test bullet rewritten with the missing-case trap and the .out goldens
  • Restore-tests bullet: compiled plans are inputs
  • Build section: put -am back after switching branches or worktrees

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): no
  • The public API, i.e., is any changed class annotated with @Public(Evolving): no
  • The serializers: no
  • The runtime per-record code paths (performance sensitive): no
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
  • The S3 file system connector: no

Documentation

  • Does this pull request introduce a new feature? no
  • If yes, how is the feature documented? not applicable

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

Generated-by: Claude Code (Claude Fable 5.1)

…nner AGENTS.md

- Calcite equivalence and SubplanReuser identify a physical node by its explainTerms digest
- A plan test case missing from the reference .xml records the current plan as the golden
- Restore-test compiled plans are inputs whose description strings drift after a digest change
- Put -am back after switching branches or worktrees

Generated-by: Claude Code (Claude Fable 5.1)
@flinkbot

flinkbot commented Sep 19, 2026

Copy link
Copy Markdown
Collaborator

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

Then:
1. Register in `FlinkStreamRuleSets.scala` and/or `FlinkBatchRuleSets.scala`
2. Plan tests with XML golden files — when the test fails, copy the framework's generated log file over the reference `.xml` (cases are ordered alphabetically by method name)
2. Plan tests with XML golden files. When a test fails, copy the generated `<Class>_actual.xml` over the reference `.xml` (cases are ordered alphabetically by method name). A case missing from the reference also fails and the current plan is written to that file, or straight into the reference when it is empty. For a bug fix, write the expected case by hand, or the golden records the bug. `explain/**/*.out` files are plain string goldens; `ExplainTest` regenerates its own under `PLAN_TEST_FORCE_OVERWRITE`, the others are edited by hand.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

about xml sounds like super complicated approach...
after FLINK-38609
the approach for xml

  1. drop xml
  2. run all the tests from the specific class (it will fail however it will create a renewed xml)
  3. run again to double check it is green now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants