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
Is your feature request related to a problem? Please describe.
Given the following JSON file, Spark will produce the values 1 and null, but on GPU we would produce 1 for both rows (once #4790 is merged).
{ "number": 1 }
{ "number": "1" }
Describe the solution you'd like
We should have consistent behavior with Spark. We need to remove the XFAIL from the test in json_test.py that references this issue.
I should clarify a bit here. This is true for integer types, ByteType, ShortType, IntegerType, and LongType when using ScanJson or JsonToStructs. It is not true for GetJsonObject or JsonTuple. It is not true for DecimalType, which happily accepts quoted strings.
This was fixed as a part of #10542 but one of the tests marked with it was still failing because of a separate regression related to how ints are parsed as dates. That test is being updated.
Is your feature request related to a problem? Please describe.
Given the following JSON file, Spark will produce the values
1
andnull
, but on GPU we would produce1
for both rows (once #4790 is merged).Describe the solution you'd like
We should have consistent behavior with Spark. We need to remove the XFAIL from the test in json_test.py that references this issue.
Describe alternatives you've considered
None
Additional context
Depends on rapidsai/cudf#10283
The text was updated successfully, but these errors were encountered: