Fix shims provider override config not being seen by executors #798
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#765 has an issue where the configuration for the shim override is not being seen by the ShimLoader on the executors. Rather than loading a fresh
SparkConf
directly inShimLoader
this leverages the config being passed to the driver/executor plugins to set the shim provider override class on startup if one is specified in the configs.Manually tested on a standalone cluster and verified the shim provider override message appears both in the driver logs and the executor logs.