-
Notifications
You must be signed in to change notification settings - Fork 232
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] Please consider to support spark.sql.extensions=com.nvidia.spark.rapids.SQLExecPlugin #479
Comments
Sorry I though this issue was to have a friendlier exception thrown here. I am going to file something different for that, it is a nuisance and different to the main issue discussed here. |
@wbo4958 fyi, we are changing this exception to be an We need, specifically, to have the correct GPU acquired in the plugin. One approach as of today for you to be able to run is to a) acquire a gpu, and b) initialize How do solve for the correct GPU in your case? That seems to be the main issue we have concerns about. Let us know what you think, perhaps there's more we can do to make it easier. |
Thx @abellina. |
Is your feature request related to a problem? Please describe.
This issue is regarding to #460, when user sets
spark.sql.extensitions=com.nvidia.spark.rapids.SQLExecPlugin
instead ofspark.plugins=com.nvidia.spark.SQLPlugin
, It will result Null Pointer exceptionThat's because RapidsExecutorPlugin will not be initialized, So GpuShuffleEnv will also not be initialized. If any code calls the method of GpuShuffleEnv, it may suffer NullPointerException, because the code assumes that the GpuShuffleEnv must have been initialized.
Describe the solution you'd like
Better to support
spark.sql.extensitions=com.nvidia.spark.rapids.SQLExecPlugin
The text was updated successfully, but these errors were encountered: