-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix regression from 21.12 where udfs defined in repl no longer worked #5030
Conversation
Signed-off-by: Alessandro Bellina <abellina@nvidia.com>
build |
Should we add some tests for such case? |
I am not sure this is worth it, and honestly I do not know how to replicate the repl in a test. I guess I could define a lambda in a different class loader, but then again I am not sure if it is wortwhile. |
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.
LGTM
Would be great if we can also verify a non-REPL use of Scala UDF in a Spark Job manually. We don't have Scala integration tests.
udf-compiler/src/main/scala/com/nvidia/spark/udf/LambdaReflection.scala
Outdated
Show resolved
Hide resolved
…ion.scala Co-authored-by: Gera Shegalov <gshegalov@nvidia.com>
Sorry it took me a little while. We do have the
With the plugin disabled:
With the plugin enabled:
|
build |
Signed-off-by: Alessandro Bellina abellina@nvidia.com
Closes #5019.
Reverts a localized change to the udf-compiler introduced with this PR (#3726).
With
ShimLoader.loadClass
, we couldn't resolve a UDF defined in the repl, as documented here: #5019.