-
Notifications
You must be signed in to change notification settings - Fork 235
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
Fix issue in GpuArrayExists where a parent view outlived the child #5232
Fix issue in GpuArrayExists where a parent view outlived the child #5232
Conversation
@tgravescs @sameerz @jlowe fyi it wasn't a cuDF bug as I originally thought. Should we backport this to 22.04? |
build |
sql-plugin/src/main/scala/com/nvidia/spark/rapids/higherOrderFunctions.scala
Outdated
Show resolved
Hide resolved
Signed-off-by: Alessandro Bellina <abellina@nvidia.com>
d95e8c0
to
d2ab38d
Compare
I re-targeted this for 22.04 since it technically is a bug in 22.04 |
build |
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.
The change LGTM.
As for 22.04 it is not a high priority because the call path is off by default on Spark 3.x. However, the fix is also very localized to this call path, thus it's a strict improvement without risking to break anything that was not broken before.
Signed-off-by: Alessandro Bellina abellina@nvidia.com
Closes #5183.
This fixes a subtle bug with
GpuArrayExists.legacyExists
that manifests itself with the CUDA async allocator, but is not caused by it.In the old code,
noNullsChildView
was closed whenreplaceChildNullsByFalseView
returned, and it was assumed to be a valid child in the calling code (legacyExists
). I changed it so this child view is alive and well while we callexistsReduce
.Note this seems to me like a bug that exists in 22.04 also.