Repository navigation
Conversation
…pply to PTFs Generated-by: Claude Opus 5.5
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
The docs for
table.exec.uid.generationcurrently read as if this option always controls how streaming transformations get UIDs for state restore. That is not true for Process Table Functions with set or broadcast semantics: their state is restored by the PTF'suidargument (or the function name if the argument is omitted), regardless of this option. This change makes that exception explicit. See FLINK-41494.Brief change log
table.exec.uid.generationoption description that it does not apply to PTFs with set or broadcast semanticsexecution_config_configuration.htmlso the config docs stay in syncVerifying this change
Please make sure both new and modified tests in this PR follow the conventions for tests defined in our code quality guide.
This change is a trivial rework / code cleanup without any test coverage.
The added wording was checked against the existing PTF uid / state-restore behavior and the current option description in
ExecutionConfigOptions.Does this pull request potentially affect one of the following parts:
@Public(Evolving): yes (docs-only change to a@PublicEvolvingoption description; no behavioral change)Documentation
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Opus 5.5