-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] test_date_format_for_time and test_date_format_maybe_incompat failed in non-utc job #10083
Comments
Confirmed reproduce via:
Seed value doesn't seem to matter |
It seems like an overflow for the values. The year values should be up to
|
cuDF can not handle years that are bigger than 9999.
Output:
I guess cuDF expect %Y prints 4 digits, so it truncates 10000 to 0000. Spark output is:
|
Depending on cuDF to handle years bigger than 9999:
The long value in cv is: 253402329599000000L |
This is not trivially supported in cudf since it requires fixed width input strings for each field. For example, Ref: https://github.com/rapidsai/cudf/blob/branch-24.02/cpp/src/strings/convert/convert_datetime.cu#L114 |
Thanks @ttnghia Related to the following issues: |
Java API returns
|
@res-life I think |
Thanks @NVnavkumar
Currently I added a sub-task in this issue to track this. |
It looks like the formatted row is getting an extra
+
sign:After fix #10032, please update the following:
Change time range to the full range. Now max time is 9999-12-30, not 9999-12-31
test_date_format
Change time range to the full range. Now max time is 9999-12-30, not 9999-12-31
update test_from_unixtime to use 9999-12-31, Change time range to the full range
The text was updated successfully, but these errors were encountered: