-
Notifications
You must be signed in to change notification settings - Fork 68
Closed
Description
Bug: ATTACH
to AWS S3 Tables endpoint times out
DuckDB version
v1.3.2
Loaded/installed extensions
extension_name | loaded | installed | extension_version | install_mode | installed_from |
---|---|---|---|---|---|
autocomplete | true | true | v1.3.2 | STATICALLY_LINKED | |
aws | false | true | 50da167 | REPOSITORY | core_nightly |
core_functions | true | true | v1.3.2 | STATICALLY_LINKED | |
httpfs | true | true | 810f64e | REPOSITORY | core_nightly |
iceberg | true | true | ed65512 | REPOSITORY | core_nightly |
icu | true | true | v1.3.2 | STATICALLY_LINKED | |
json | true | true | v1.3.2 | STATICALLY_LINKED | |
parquet | true | true | v1.3.2 | STATICALLY_LINKED | |
shell | true | true | v1.3.2 | STATICALLY_LINKED | |
spatial | false | true | 662718c | REPOSITORY | core |
Reproduction
CREATE SECRET (
TYPE s3,
PROVIDER credential_chain
);
ATTACH 'arn:aws:s3tables:us-east-1:<project_id>:bucket/<bucket_name>'
AS s3_tables_db (
TYPE iceberg,
ENDPOINT_TYPE s3_tables
);
Result
I'm getting the following error:
Invalid Configuration Error:
Request to 's3tables.us-east-1.amazonaws.com/iceberg/v1/config?warehouse=arn%3Aaws%3As3tables%3Aus-east-1%3A<project_id>%3Abucket%2F<bucket_name>' returned a non-200 status code (INVALID), with reason: curlCode: 28, Timeout was reached; Details: Connection timed out after 1001 milliseconds
That timeout seems too short, and also, it is not aligned with any duckdb_settings (ie. http_timeout is 30 seconds by default)
Expected result
To be able to attach S3 tables with no problems.
Other details
- I'm running this through a VPN, but I can't find any details about expectations/assumptions about network latency in the documentation.
- I was able to inject data into S3 tables using the same network with no problems whatsoever.
Metadata
Metadata
Assignees
Labels
No labels