You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i bumped duckdb from version 1.1.3 to 1.2.0,
i'm using it to run queries on azure blob storage, with the following bootstrap queries:
INSTALL azure;
LOAD azure;
SET azure_http_stats = true;
SET azure_read_transfer_concurrency = 16;
SET azure_read_transfer_chunk_size = 1024*1024*8;
SET azure_read_buffer_size = 1024*1024*8;
SET azure_transport_option_type = 'curl;
SET azure_context_caching = true;
CREATE SECRET IF NOT EXISTS azureSecret (
TYPE AZURE,
CONNECTION_STRING <redacted>'
);
INSTALL delta;
LOAD delta;
this was working exceptionally well in duckdb 1.1.3, but in version 1.2.0 i'm getting this error: Errore SQL: java.sql.SQLException: IO Error: AzureBlobStorageFileSystem could not open file: 'az://myfile.parquet', unknown error occurred, this could mean the credentials used were wrong. Original error message: 'Fail to get a new connection for: https://myblob.blob.core.windows.net. SSL connect error'
changing azure_transport_option_type rom curl to default fixed the problem.
but i have no idea why, since the blob storage configuration hasn't changed.
The text was updated successfully, but these errors were encountered:
i bumped duckdb from version 1.1.3 to 1.2.0,
i'm using it to run queries on azure blob storage, with the following bootstrap queries:
this was working exceptionally well in duckdb 1.1.3, but in version 1.2.0 i'm getting this error:
Errore SQL: java.sql.SQLException: IO Error: AzureBlobStorageFileSystem could not open file: 'az://myfile.parquet', unknown error occurred, this could mean the credentials used were wrong. Original error message: 'Fail to get a new connection for: https://myblob.blob.core.windows.net. SSL connect error'
changing azure_transport_option_type rom curl to default fixed the problem.
but i have no idea why, since the blob storage configuration hasn't changed.
The text was updated successfully, but these errors were encountered: