mateczagany opened a new pull request, #29132:
URL: https://github.com/apache/flink/pull/29132
## What is the purpose of the change
Prevent the native S3 writer from aborting multipart uploads that may be
needed for recovery. Previously, disposing an in-progress file during task
shutdown or cancellation could invalidate checkpoint state, causing recovery to
fail with `NoSuchUpload`.
## Brief change log
- Preserve uploads after successful persistence and when resuming from
recoverable state
- Document cleanup of abandoned uploads and its implications for recovery
## Verifying this change
This change added tests and can be verified as follows:
- Added unit tests covering failed first and subsequent persistence,
disposal of an empty recovered stream, and concurrent persistence and disposal
- Extended existing S3 integration tests to dispose the original stream
before recovery
- Added integration tests covering disposal of recovered streams, recovery
after failed commit preparation, and cleanup of unpersisted uploads
## 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: yes — recovery of files
written through the native S3 connector
- The S3 file system connector: yes
## 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?
- [x] Yes (please specify the tool below)
Generated-by: Codex GPT-6
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
