You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We know that there are some issues in CUDF with parsing empty lines. We first tried to fix this by passing in an empty dictionary as a place holder '{}' but this caused other problems because CUDF is not happy to produce a table with no columns in it. Or perhaps more accurately some of our code is not happy with that. We worked around this by adding in a column that was requested and setting it to null. That works for empty lines, but it shows up as a problem if all of the lines are {}, [], or all of them have something in them, but it is invalid.
We really should just fix the underlying problem instead of trying to work around it. This also exists in ScanJson, but I have not formally added a test for it yet.
The text was updated successfully, but these errors were encountered:
Describe the bug
We know that there are some issues in CUDF with parsing empty lines. We first tried to fix this by passing in an empty dictionary as a place holder '{}' but this caused other problems because CUDF is not happy to produce a table with no columns in it. Or perhaps more accurately some of our code is not happy with that. We worked around this by adding in a column that was requested and setting it to null. That works for empty lines, but it shows up as a problem if all of the lines are
{}
,[]
, or all of them have something in them, but it is invalid.We really should just fix the underlying problem instead of trying to work around it. This also exists in ScanJson, but I have not formally added a test for it yet.
The text was updated successfully, but these errors were encountered: