-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Querying Unity Catalog with DuckDB UC extension requires retrying the first SQL statement #8
Comments
At least part of the problem appears to be that the extension is trying to convert column types to an internal type: Lines 32 to 144 in 71e18a9
But it does not have a mapping for "varchar(xxxx)", so it throws an exception: Line 146 in 71e18a9
Scanning our (databricks) system.information_schema.columns for unique full_data_types
It looks like you might also need to map:
Maybe also the 'unsized' versions for extra diligence?
|
Hi @edwardsdm, thanks for reporting this. We will take a look at this at some point. Currently we have prioritized the development of the Delta extension over the uc_catalog extension so I can not give a timeline yet! |
Hey team, this issue is also happening to me and I could reproduce exactly what was described here. I can read the metadata for all tables normally after the 3rd attempt, WHICH IS SUPER COOL. But I can't query anything due to permission errors on S3, in my org we need to query that through UC and not using the S3 path directly (that I believe is what is happening under the hood with the Delta extension). |
Adding these 4 lines seems generally to fix the issues in our environment: } else if (type_text.find("varchar") == 0) {
return LogicalType::VARCHAR;
} else if (type_text.find("char") == 0) {
return LogicalType::VARCHAR;
I built the plugin locally with these changes and tested it in our (@edwardsdm and me) environment. |
The information below has been share with the Databricks UC engineering team. They suggested the issue is likely with the DuckDB UC extension.
Credential serving is enabled on the Databricks instance the code is connecting to.
Duckdb CLI installed on MacOS - Retry SHOW TABLES query
R - Retry SHOW TABLES query
Python - Retry SHOW TABLES query
Additionally even after a successful SHOW TABLES query no tables are found and the table queried successfully in R cannot be queried using Python.
The text was updated successfully, but these errors were encountered: