-
Notifications
You must be signed in to change notification settings - Fork 113
remove arrow from Canonical::empty #2105
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
Conversation
joseph-isaacs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good spot
| dtype.is_nullable(), | ||
| ) | ||
| .into_canonical() | ||
| builder_with_capacity(dtype, 0).finish()?.into_canonical() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make sure that infer_data_type matches this builder. I think that should also be fixed in this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we care about arrow data types?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this is incorrect?
joseph-isaacs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess infer data type is an unrelated problem
|
ah, I just found this in fuzzer, thanks for fixing it @onursatici |
Arrow Lists are nullable but elements of those lists are not. In
Identity::return_dtype, previous behaviour returnedlist(i64?)?when givenlist(i64)?