-
Notifications
You must be signed in to change notification settings - Fork 242
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
Support TimeAdd for non-UTC time zone #10068
Changes from all commits
212a0b1
4f52067
c7dc304
89c9305
4c9485f
64a0232
f4e85d7
7f4237c
2de0e6e
3d5f2b9
4574ef1
2014495
c6102f3
66f3dd6
0801287
26152f5
cf10350
a4334d9
be5f813
06c6c47
ec7c4b0
511f8ee
a3ab495
0fb8ecb
a9deb35
1f3410f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -473,7 +473,7 @@ object GpuScalar extends Logging { | |
* | ||
* This class is introduced because many expressions require both the cudf Scalar and its | ||
* corresponding Scala value to complete their computations. e.g. 'GpuStringSplit', | ||
* 'GpuStringLocate', 'GpuDivide', 'GpuDateAddInterval', 'GpuTimeMath' ... | ||
* 'GpuStringLocate', 'GpuDivide', 'GpuDateAddInterval', 'GpuTimeAdd' ... | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Q: Why name changed? It seems different over different Spark version. We can comment both in There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
* So only either a cudf Scalar or a Scala value can not support such cases, unless copying data | ||
* between the host and the device each time being asked for. | ||
* | ||
|
@@ -493,7 +493,7 @@ object GpuScalar extends Logging { | |
* happens. | ||
* | ||
* Another reason why storing the Scala value in addition to the cudf Scalar is | ||
* `GpuDateAddInterval` and 'GpuTimeMath' have different algorithms with the 3 members of | ||
* `GpuDateAddInterval` and 'GpuTimeAdd' have different algorithms with the 3 members of | ||
* a `CalendarInterval`, which can not be supported by a single cudf Scalar now. | ||
* | ||
* Do not create a GpuScalar from the constructor, instead call the factory APIs above. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How to ensure the random df will 100% overflow?
Maybe specify some constant variables to ensure overflow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By not making it actually random.
DayTimeIntervalGen
Has both amin_value
and amax_value
. You could set it up so all of the values generated would overflow. You might need to also remove the special cases and disable nulls to be 100% sure of it.spark-rapids/integration_tests/src/main/python/data_gen.py
Line 743 in 384b2a9
You could also use SetValuesGen with only values in it that would overflow.
spark-rapids/integration_tests/src/main/python/data_gen.py
Line 358 in 384b2a9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated to SetValuesGen.