What happens?
Hello, I am able to perform the following set of steps successfully using duckdb shell (cli) but it breaks when done via the python library.
INSTALL aws;
INSTALL httpfs;
INSTALL iceberg;
CREATE OR REPLACE SECRET (
TYPE s3,
PROVIDER credential_chain
);
ATTACH OR REPLACE 'arn:aws:s3tables:...:bucket/s3_table' AS s3_tables_db (
TYPE iceberg,
ENDPOINT_TYPE s3_tables
);
# This works from the shell
FROM s3_tables_db.core.product LIMIT 5;
Any help at all would be appreciated.
To Reproduce
import duckdb
conn = duckdb.connect()
conn.install_extension("aws")
conn.install_extension("httpfs")
conn.install_extension("iceberg")
conn.sql(
"""
CREATE OR REPLACE SECRET (
TYPE s3,
PROVIDER credential_chain
);
"""
)
conn.sql(
"""
ATTACH OR REPLACE 'arn:aws:s3tables:...:bucket/s3_table' AS s3_tables_db (
TYPE iceberg,
ENDPOINT_TYPE s3_tables
);
"""
)
# Works
x = conn.execute("show all tables;").fetchall()
# Errors out
y = conn.execute(
"""
FROM s3_tables_db.core.product LIMIT 5;
"""
).fetchall()
Output
Exception has occurred: CatalogException
Catalog Error: Table with name product does not exist!
Did you mean "s3_tables_db.core.product"?
OS:
OSX
DuckDB Package Version:
1.4.1
Python Version:
3.12
Full Name:
Jibi Abraham
Affiliation:
Razor Group
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a stable release
Did you include all relevant data sets for reproducing the issue?
No - Other reason (please specify in the issue body)
Did you include all code required to reproduce the issue?
Did you include all relevant configuration to reproduce the issue?
What happens?
Hello, I am able to perform the following set of steps successfully using duckdb shell (cli) but it breaks when done via the python library.
Any help at all would be appreciated.
To Reproduce
Output
OS:
OSX
DuckDB Package Version:
1.4.1
Python Version:
3.12
Full Name:
Jibi Abraham
Affiliation:
Razor Group
What is the latest build you tested with? If possible, we recommend testing with the latest nightly build.
I have tested with a stable release
Did you include all relevant data sets for reproducing the issue?
No - Other reason (please specify in the issue body)
Did you include all code required to reproduce the issue?
Did you include all relevant configuration to reproduce the issue?