eskabetxe commented on code in PR #29422:
URL: https://github.com/apache/flink/pull/29422#discussion_r4287404450
##########
docs/content/docs/deployment/filesystems/s3.md:
##########
@@ -153,6 +153,10 @@ The legacy configuration key `s3.path.style.access` is
still supported as a fall
The Native S3 FileSystem is a pure-Java implementation built on the AWS SDK v2
completely removing the dependency on Hadoop. It is registered under the
schemes *s3://* and *s3a://*. It provides a drop-in replacement for the Presto
and Hadoop implementations, supporting checkpointing, the [FileSink]({{< ref
"docs/connectors/datastream/filesystem" >}}) (via `RecoverableWriter`),
server-side encryption (SSE-S3, SSE-KMS), cross-account access via IAM role
assumption, entropy injection, and bulk copy via S3TransferManager.
+{{< hint info >}}
+**Switching from the Hadoop or Presto implementations:** jobs with pending or
in-progress `FileSink` part files in their state can be restored directly with
the Native S3 FileSystem — checkpoints and savepoints written by the
Hadoop/Presto recoverable-state format are detected and migrated on restore.
The Hadoop and Presto implementations are being left behind, and this migration
path is a one-time occasion as it covers the legacy state format as it exists
today, and any future change to the Hadoop/Presto state format could not be
picked up by the Native S3 FileSystem. The reverse direction is also **not**
supported: state written by the Native S3 FileSystem cannot be restored with
the Hadoop or Presto implementations. Drain the job first (e.g.
`stop-with-savepoint --drain`) before switching back.
Review Comment:
added in english, if someone can give me the translation I will change it.
--
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]
