Closed galipremsagar closed 3 years ago
This issue has been marked rotten due to no recent activity in the past 90d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.
This issue has been marked stale due to no recent activity in the past 30d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be marked rotten if there is no activity in the next 60d.
This error no longer presents in 21.08. Instead we get the data corruption bug covered in #6382
...
print(
cudf.read_json(io.StringIO(buf), engine="cudf", lines=True, dtype={"a":np.dtype("datetime64[ns]")})
)
a
0 1969-12-31 23:59:59.999
1 1969-12-31 23:59:59.999
2 1969-12-31 23:59:59.999
As a result, I'm going to close this issue to consolidate discussion in #6382
Describe the bug
cudf.read_json
provides ability to specify the dtypes of the resulting columns to be loaded into the dataframe from a json file. When a datetime type is provided it seems to be giving a RunTimeError, but duration types seem to be functioning correctly.Steps/Code to reproduce bug
Expected behavior We should be able to load correctly when we provide a
dtype
mapping which containsdatetime64
types.Environment overview (please complete the following information)
Environment details
Click here to see environment details
Additional context Surfaced while running fuzz tests: #6001