-
Notifications
You must be signed in to change notification settings - Fork 237
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_cast_float_to_timestamp_ansi_for_nan_inf failed in spark330 #5719
Comments
This is a same as previous failures that we have fixed in Spark 3.3.0+ Spark is moving away from standard Java Exceptions to their own Exceptions. This failure is happening because the Spark could have an error message to the tune of whereas we have a generic message for a value in the column To match the above error we have to know whether the column has a positive inf value or a negative inf value which will cost us an extra iteration over the entire column. Is matching the Exception type really important to us as a product when it's costing us this overhead? |
Thanks @razajafri for the detailed explanation of the issue. Previous failures were easy to fix as the Exceptions were not Test is failing after this change was backported :https://github.com/apache/spark/pull/36591/files so it would be in Spark-3.3 release. Here they are calling I tried throwing Adding @tgravescs @gerashegalov if they have any thoughts on this. |
With the above PR, the Exception is close to Spark's error message. Note that I am not extra check to identify if it's a Nan or INF.
|
Describe the bug
spark330shim run w/ spark 3.3.1-SNAPSHOT (due to spark 3.3.0 release is not out yet)
error message assert failed,
The text was updated successfully, but these errors were encountered: