LuigiDurso commented on issue #9386: URL: https://github.com/apache/seatunnel/issues/9386#issuecomment-2980143295
Root Cause Identified I've identified the root cause of this issue. The problem wasn't with the SeaTunnel Iceberg connector configuration itself, but rather with how Project Nessie handles S3 endpoint configuration. What was happening: The initial call to MinIO was made correctly using the configured endpoint (http://minio:9000) After the first Project Nessie response, Nessie returned the nessie.catalog.service.s3.default-options.external-endpoint property At this point, the endpoint configuration was overridden by the value in that Nessie property, causing subsequent calls to attempt connection to 127.0.0.1:9002 Solution: The issue is resolved by properly configuring the nessie.catalog.service.s3.default-options.external-endpoint property in the Nessie catalog service configuration to match the intended MinIO endpoint. This explains why the same MinIO configuration worked with other tools (Trino, Superset, Flink) - they weren't going through Nessie's S3 endpoint override mechanism. Closing this issue as the root cause has been identified and resolved. -- 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]
