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
I am not 100% sure what is happening here as there is code in place for this, and there appears to be some tests in ScanJson for it. But the tests and the checks don't look like they are compatible with each other and every time I try to set the timestampFormat, for from_json it fallback back to the CPU. I don't know why. Even if I set it to the one hard coded value that should work.
But for dateFormat I am able to set it to something like MMM yyyy which is a format that we don't support, and it does not fall back to the CPU. Instead we get an error about how when we try to convert it to the format that CUDF wants it is not supported.
The text was updated successfully, but these errors were encountered:
revans2
changed the title
[BUG] setting timestampFormat/dateFormat for JsonToStructs appears to always fall back to the CPU
[BUG] setting timestampFormat/dateFormat for JsonToStructs appears to always fall back too often and also not often enough
Feb 23, 2024
revans2
changed the title
[BUG] setting timestampFormat/dateFormat for JsonToStructs appears to always fall back too often and also not often enough
[BUG] setting timestampFormat/dateFormat for JsonToStructs appears to fall back too often and also not often enough
Feb 23, 2024
Describe the bug
I am not 100% sure what is happening here as there is code in place for this, and there appears to be some tests in ScanJson for it. But the tests and the checks don't look like they are compatible with each other and every time I try to set the timestampFormat, for from_json it fallback back to the CPU. I don't know why. Even if I set it to the one hard coded value that should work.
But for dateFormat I am able to set it to something like
MMM yyyy
which is a format that we don't support, and it does not fall back to the CPU. Instead we get an error about how when we try to convert it to the format that CUDF wants it is not supported.The text was updated successfully, but these errors were encountered: