Skip to content

Conversation

@mxm
Copy link
Contributor

@mxm mxm commented Sep 19, 2025

In #26433, we removed the EOI marker in the form of Long.MAX_VALUE as the checkpoint id. Since streaming pipelines can continue to checkpoint even after their respective operators have been shut down, it is not safe to use a constant as this can lead to duplicate commits.

However, in batch pipelines we only have one commit on job shutdown. Using any checkpoint id should suffice in this scenario. Any pending committables should be processed by the ComitterOperator when the operator shuts down. No further checkpoints will take place.

There are various connectors which rely on this behavior. I don't see any drawbacks from keeping this behavior for batch pipelines.

Backport of #27004.

…es in batch mode

In apache#26433, we removed the EOI marker in the form of Long.MAX_VALUE as the checkpoint id. Since
streaming pipelines can continue to checkpoint even after their respective operators have been shut
down, it is not safe to use a constant as this can lead to duplicate commits.

However, in batch pipelines we only have one commit on job shutdown. Using any checkpoint id should
suffice in this scenario. Any pending committables should be processed by the ComitterOperator when
the operator shuts down. No further checkpoints will take place.

There are various connectors which rely on this behavior. I don't see any drawbacks from keeping
this behavior for batch pipelines.
@mxm mxm requested review from AHeise and Sxnan September 19, 2025 07:46
Copy link
Contributor

@AHeise AHeise left a comment

Choose a reason for hiding this comment

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

LGTM.

@flinkbot
Copy link
Collaborator

flinkbot commented Sep 19, 2025

CI report:

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

Copy link
Contributor

@Sxnan Sxnan left a comment

Choose a reason for hiding this comment

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

LGTM

@mxm mxm changed the title [backport][FLINK-38370] Ensure CommitterOperator commits all pending committables in batch mode [release-1.20][FLINK-38370] Ensure CommitterOperator commits all pending committables in batch mode Sep 19, 2025
@mxm
Copy link
Contributor Author

mxm commented Sep 19, 2025

I see spotless failures in https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=69775&view=logs&j=52b61abe-a3cc-5bde-cc35-1bbe89bb7df5&t=54421a62-0c80-5aad-3319-094ff69180bb

But when I run ./mvnw spotless:apply nothing changes. I also tried running the exact same task as in the build. Strange. I've manually corrected the failures according to the outputted diff.

@mxm mxm merged commit 691b8f9 into apache:release-1.20 Sep 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants