-
Notifications
You must be signed in to change notification settings - Fork 603
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
bug: arrow type error when show data with 'UUID' object #8532
Comments
Thanks for opening this. Issue 1 should be fixed in #8535. Issue 2 is due to the The easiest (and I think most consistent) fix would be to stop returning uuid columns in cc @cpcloud for a 👍 / 👎 before I implement this fix. |
Eventually we should simplify the pandas output until |
Seems fine. I don't like that we have to do this but the alternative of implementing a custom pyarrow type seems less desirable than converting to strings. |
The repeated UUID issue has been addressed:
|
I think there is a simple and self-contained solution to UUID types and any other type that does not have a 1:1 mapping between Ibis and PyArrow, such as MAC addresses, UUIDs, etc. Let me know what you think. I am willing to add tests and make a PR if this approach makes sense. This commit only checks for bijectivity between Ibis and PyArrow types, and if any column of the schema does not comply, then it is cast server-side. There are some pros:
Cons:
|
At least for UUID, since Arrow has a canonical extension type for it, it seems like that would be a great way to maintain the type information. |
1 similar comment
At least for UUID, since Arrow has a canonical extension type for it, it seems like that would be a great way to maintain the type information. |
What happened?
Issue 1: duckdb will produce different uuid for each row, but same uuid generated by sqlite, there maybe other backends have the same issue.
Issue 2: get ArrowTypeError when show data:
Got the following error:
it works well for to_pandas()
What version of ibis are you using?
8.0.0
What backend(s) are you using, if any?
duckdb, sqlite
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: