-
Notifications
You must be signed in to change notification settings - Fork 25
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
chore: move infer_schema and infer_data_type into vortex-dtype #1081
chore: move infer_schema and infer_data_type into vortex-dtype #1081
Conversation
I want to use these in PyVortex without depending on vortex-datafusion.
2632167
to
edf9b52
Compare
edf9b52
to
b0ab48f
Compare
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.
We should not standardise this code but instead come up with a solution. This method is wrong but necessary for datafusion. Not quite sure what the flow is in pyarrow but I would like to avoid this method being api. At most we should copy paste it as an implementation of pyvortex
@robert3005 we now bail on lists |
// There are four kinds of lists: List (32-bit offsets), Large List (64-bit), List View | ||
// (32-bit), Large List View (64-bit). We cannot both guarantee zero-copy and commit to an | ||
// Arrow dtype because we do not how large our offsets are. | ||
DType::List(..) => vortex_bail!("Unsupported dtype: {}", dtype), |
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.
For posterity - we will canonicalize to List View. We should figure out what to do about fixed size lists though
I want to use these in PyVortex without depending on vortex-datafusion.