Samrat002 commented on code in PR #27841:
URL: https://github.com/apache/flink/pull/27841#discussion_r3019786200
##########
docs/content/docs/deployment/filesystems/s3.md:
##########
@@ -295,11 +295,25 @@ Hadoop configuration keys are automatically translated.
For example, `fs.s3a.con
## Using Multiple S3 Implementations
+All three S3 implementations register as handlers for the *s3://* scheme.
Additionally, each implementation supports alternative schemes:
+
+| Implementation | Schemes |
+|---------------|---------|
+| Native S3 | *s3://*, *s3a://* |
+| Presto | *s3://*, *s3p://* |
+| Hadoop | *s3://*, *s3a://* |
+
+Only one implementation can handle a given scheme at a time. The Native S3
implementation has the lowest priority, so when another implementation is
present, it will take precedence for the *s3://* scheme.
+
You can use multiple S3 implementations simultaneously by leveraging their
different URI schemes. For example, if a job uses the [FileSystem]({{< ref
"docs/connectors/datastream/filesystem" >}}) sink (Hadoop-only) but Presto for
checkpointing:
- Use *s3a://* scheme for the sink (Hadoop)
- Use *s3p://* scheme for checkpointing (Presto)
+{{< hint info >}}
+The Native S3 implementation does not introduce a new URI scheme. It reuses
the existing *s3://* and *s3a://* schemes. To use it alongside the Hadoop
implementation, ensure only the Native S3 plugin JAR is in the `plugins`
directory (i.e., do not have both `flink-s3-fs-native` and `flink-s3-fs-hadoop`
plugins loaded simultaneously for the same scheme).
Review Comment:
Yeah , `"To use it alongside the Hadoop implementation"` sounds missleading
at the beginning.
I've updated the wording to be more explicit and direct . PTAL
--
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]
