Use SQLConf instead of SparkConf when looking up SQL configs #522
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.
Signed-off-by: Jason Lowe [email protected]
The shuffle manager can crash during planning because it is trying to lookup a
SQLConf
config property on theSparkConf
passed to the shuffle manager during init. If the user doesn't set thespark.sql.adaptive.enabled
property then the query fails with ajava.util.NoSuchElementException: spark.sql.adaptive.enabled
error trying to lookup the missing property.This updates the shuffle manager to get the
SQLConf
instance and use that to lookup the SQL-specific config key.