You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gabor Somogyi (Jira)" <ji...@apache.org> on 2026/04/23 12:18:00 UTC
[jira] [Created] (FLINK-39530) Native S3 connector detects s3 compatible servers wrong without any workaround
Gabor Somogyi created FLINK-39530:
-------------------------------------
Summary: 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
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)