Feature Request: ignore columns with unsupported extension types if they aren't used (arrow extensions) #13931
westonpace
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
I think this is a valid point, we should probably throw at execution (after push-down) instead of throwing at bind. |
Beta Was this translation helpful? Give feedback.
1 reply
-
This behavior has changed in version 1.1. I am now getting this error while sorting a geoparquet but didn't get that error in 1.0
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I use duckdb to query arrow tables/datasets/readers/etc.
However, sometimes those tables have columns which are extension types. If DuckDb doesn't recognize the extension type then it raises an exception. This is understandable if the query needs to access that column. However, this occurs even when a query doesn't need a particular column. As a result, I have to manually prune these columns from my input before using duckdb which is inconvenient (not easy for me to know which data types duckdb supports and which it doesn't). I'd rather duckdb just ignore the presence of these unused columns.
Here is a complete example:
Beta Was this translation helpful? Give feedback.
All reactions