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
Our current code to fall back to the CPU for unsupported time zones looks at the globally set time zone, or the one that is set specifically for an expression. But from_json has a text option that can be passed in that overrides all of them on how the timestamps should be interpreted.
We need to either support the time zone when parsing the timestamp or we need to fall back to the CPU for it.
I suspect this is also the case for ScanJson, but I don't have a test to verify that yet.
The text was updated successfully, but these errors were encountered:
The code was recently made common between JsonToStructs(from_json) and ScanJson so now the checks are the same and we do fall back if we are not in a UTC time zone when timestamps or dates are present in the read schema.
Describe the bug
Our current code to fall back to the CPU for unsupported time zones looks at the globally set time zone, or the one that is set specifically for an expression. But from_json has a text option that can be passed in that overrides all of them on how the timestamps should be interpreted.
We need to either support the time zone when parsing the timestamp or we need to fall back to the CPU for it.
I suspect this is also the case for ScanJson, but I don't have a test to verify that yet.
The text was updated successfully, but these errors were encountered: