Skip to content
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

fix(pyarrow): support accepting pyarrow dictionary types as inputs #8276

Merged

Conversation

jcrist
Copy link
Member

@jcrist jcrist commented Feb 8, 2024

Fixes #8207.

@jcrist jcrist requested a review from kszucs February 8, 2024 05:28
@cpcloud cpcloud added this to the 9.0 milestone Feb 8, 2024
@cpcloud cpcloud added bug Incorrect behavior inside of ibis datatypes Issues relating to ibis's datatypes (under `ibis.expr.datatypes`) labels Feb 8, 2024
@cpcloud cpcloud merged commit 977df11 into ibis-project:the-epic-split Feb 8, 2024
70 of 71 checks passed
@cpcloud
Copy link
Member

cpcloud commented Feb 8, 2024

Thank you!

@kszucs
Copy link
Member

kszucs commented Feb 10, 2024

I would possibly a good idea to have a dictionary type in ibis since many of the backends support dictionary/enum/lowcardinality types.

@cpcloud
Copy link
Member

cpcloud commented Feb 10, 2024

I don't particularly like the idea of that type in ibis, because whether a type is encoded as a dictionary or any other specific way has no effect on the expression API.

Since this type is useful in DDL, perhaps there's a way we can have a set of expanded DDL-only types?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Incorrect behavior inside of ibis datatypes Issues relating to ibis's datatypes (under `ibis.expr.datatypes`)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants