[SPARK-53309][SQL] Allow to propagate extra conf to executor #52071
+10
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Yuan <[email protected]>
zhouyuan
force-pushed
the
wip_spark_config_prefix
branch
from
79fc7e2 to
4cbf645
Compare
|
Many places in Spark code ignore configs without |
itskals
reviewed
Aug 25, 2025
| @@ -458,6 +458,13 @@ object SQLConf { | |||
| .booleanConf | |||
| .createWithDefault(true) | |||
|
|
|||
| val PROPAGATE_CONF_PREFIXES = buildConf("spark.sql.propagateConfPrefixes") | |||
There was a problem hiding this comment.
All Hadoop and Hive configurations have also been mandated to include the prefix spark.. Several systems have been developed based on this understanding. Why then can the gluten configuration not adhere to the same standard?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes were proposed in this pull request?
By default Spark only propagate configurations with "spark" prefix to executor side.
This patch added a new configuration to define a comma based list, configurations with such prefix will propagated to executor side.
This will help to pass session level configurations to new native execution engine like Gluten project.
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?