-
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
[FEA] Support arrays with nulls in the input of GpuRowBasedUDF
for Spark 3.1.1+
#3942
Comments
Here is a related issue #3855 |
Just found this test can pass if the code generation for SafeProjection is disabled. |
I'm confused. Is this a bug report for code that we are not going to commit? If so I say we just close this, and the PR that wants to update to the 3.1.1 conversion code will need to resolve the test failures before it is committed. |
CPUBasedUDFSuite
fails when running under Spark 3.1+GpuRowBasedUDF
for Spark 3.1.1+
I updated it to be a feature request after adding shim layers for GpuRowBasedUDF. |
The null error mentioned in description is probably a bug of code generation in Spark . The below code (extracted from the file scala-test-detailed-output.log for this test case here) is generated from the 3 lines 1095-1097.
And the log I added for debugging in
But as we know, |
On the other hand, seems it was not always reasonale to throw exception when trying to get a null value.
|
This is a follow on issue for #3897.
When the input of
GpuRowBasedUDF
contains arrays with nulls, the UDF will run into the below error for Spark 3.1.1+ during our Unit tests where the Java assertion is enabled.So in the PR #3897, we let it fall back to CPU for this case for now.
However, we need to eventually support this case for Spark 3.1.1+, since we already do for Spark3.0.x.
[Update] Everything works well as the CPU under production envs where the Java assertion is disabled.
The text was updated successfully, but these errors were encountered: