-
Notifications
You must be signed in to change notification settings - Fork 908
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
[FEA] Provide option to read fields with mixed types #11947
Comments
It is common in GeoJson to have different level of nested list data in the same column. Here's a column of a polygon and a linestring. (You can visualize this in https://geojson.io/) |
After some internal discussion we are favoring the option:
Here is an example of what this representation could look like:
|
This would be great :) Also running into this with this file: (value gets set as None for first two times, then keeps the empty object)
(Formatted JSON):
|
Also see #14239 |
Closed by #14572 |
Is your feature request related to a problem? Please describe.
The
cudf_experimental
JSON reader does not faithfully read fields with mixed nesting.If the field contains
scalar
andlist
then thescalar
values are set to null:If the field contains
scalar
andstruct
then thescalar
values are set to null:If the field contains different levels of nested lists, the shallower lists are set to null:
If the field contains
list
andstruct
types, we throw:Describe the solution you'd like
We've talked about a few solutions:
Describe alternatives you've considered
Without a workaround, JSON inputs including a field with mixed types will not be readable.
Additional context
This item still needs some design work. Please comment and share a data sample if it is impacting you.
The text was updated successfully, but these errors were encountered: