[
https://issues.apache.org/jira/browse/FLINK-39530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18075886#comment-18075886
]
Gabor Somogyi commented on FLINK-39530:
---------------------------------------
[{{2cf4c36}}|https://github.com/apache/flink/commit/2cf4c361f5fb230ada46b1706eb38f58b5d4c399]
on release-2.3
> Native S3 connector detects s3 compatible servers wrong without any workaround
> ------------------------------------------------------------------------------
>
> Key: FLINK-39530
> URL: https://issues.apache.org/jira/browse/FLINK-39530
> Project: Flink
> Issue Type: Bug
> Components: Connectors / FileSystem
> Affects Versions: 2.3.0
> Reporter: Gabor Somogyi
> Assignee: Gabor Somogyi
> Priority: Blocker
> Labels: pull-request-available
>
> Now when user sets the following valid config entry for the native connector:
> {code:java}
> conf.set(Constants.ENDPOINT, "s3.us-west-2.amazonaws.com");
> {code}
> then the connector detects servers as s3 compatible and sets the following
> forced:
> {code:java}
> pathStyleAccess = true
> s3ConfigBuilder.chunkedEncodingEnabled(false).checksumValidationEnabled(false);
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
