-
Notifications
You must be signed in to change notification settings - Fork 245
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] Casting a Date to String results in a result different from Spark CPU #88
Comments
So it looks like the issue is really only in printing a > 4 digit year. Do we have a cudf issue filed for this? Is spark actually inserting a |
Yes, This is how it's working in Spark I think. 0001-01-01 00:00:00 is the first day of year 1. after the millenia has ended spark adds a +1 to the year for the subsequent millenia. +10001-01-01 00:00:00 is the first day of this millenia This goes up until +294247-01-09 20:00:54 after which the long will overflow So to do this in Spark we will have to know the boundaries of the milllenias in epoch and check the column for any values greater than the boundary and keep adding one until we don't find any more values that are greater than the value here are the epochs for the millenias starting from -290308 upto +294247
|
Signed-off-by: spark-rapids automation <[email protected]>
Describe the bug
When casting a Date to string doesn't always match the CPU result
Steps/Code to reproduce bug
The above code results in
Expected behavior
It should result in the following
The text was updated successfully, but these errors were encountered: