-
Notifications
You must be signed in to change notification settings - Fork 238
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 yyyyMMdd in GetTimestamp operator for LEGACY mode [databricks] #11449
Conversation
Signed-off-by: Chong Gao <[email protected]>
c7f0cc6
to
adbbefd
Compare
build |
Building failed due to #11436 Errors: |
Looks like this change will also enable |
build |
Updated cases. |
build |
assert_gpu_and_cpu_are_equal_sql( | ||
lambda spark : unary_op_df(spark, gen), | ||
"tab", | ||
"select unix_timestamp(a, 'yyyyMMdd'), from_unixtime(unix_timestamp(a, 'yyyyMMdd'), 'yyyyMMdd'), date_format(to_timestamp(a, 'yyyyMMdd'), 'yyyyMMdd') from tab", |
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.
Consider using multi-line strings
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.
Done
sql-plugin/src/main/scala/org/apache/spark/sql/rapids/datetimeExpressions.scala
Show resolved
Hide resolved
Looks good to me. |
build |
Spark 400 building failure is related to #11479 |
closes #11445
This PR supports yyyyMMdd in GetTimestamp operator for LEGACY mode
Note: this PR introduced inconsistent behavior compared to Spark:
Spark behavior:
GPU only support 8 digit strings.