-
Notifications
You must be signed in to change notification settings - Fork 230
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] 3.1.0 pos_explode tests are failing #953
Comments
It looks like https://issues.apache.org/jira/browse/SPARK-32295 caused this to happen |
Looking at the code change it is supposed to skip this if the children are foldable. We are hitting this in a special case where the child is not foldable. We cannot |
jira in spark: https://issues.apache.org/jira/browse/SPARK-33544?filter=-2 |
spark PR for the jira is merged, we need to wait for a build and then we can add our tests back |
…IDIA#953) Signed-off-by: spark-rapids automation <70000568+nvauto@users.noreply.github.com>
Describe the bug
A lot of pos_explode and explode integration tests are failing in the 3.1.0 CI.
From looking at the exception it appears to be that spark is inserting a filter into the plan somewhere now that checks the length of the array, and this results in the data not being on the GPU any longer.
This appears to be a needless step because we are creating the array right then. This also will make things more compilcated to optimize and keep the same functionality in place. I also don't want to have to materialize the arrays so this is going to require some optimizations in the planning of the query, and possibly pushing those back into spark itself.
The text was updated successfully, but these errors were encountered: