Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
3.1.0
-
None
-
None
Description
If you set a default spark.scheduler.pool in your configuration when you create a SparkSession and then you attempt to override that configuration by calling setLocalProperty on a SparkSession, as described in the Spark documentation - https://spark.apache.org/docs/latest/job-scheduling.html#fair-scheduler-pools - it won't work.
Spark will go with the original pool name.
I've traced this down to SQLExecution.withSQLConfPropagated, which copies any key that starts with "spark" from the the session state to the local properties. The can end up overwriting the scheduler, which is set by spark.scheduler.pool