[SPARK-49938][K8S] Prefer to use Hadoop configMap when specified #48427
Conversation
This file contains 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
zgzzbws
force-pushed
the
prefer-config-map
branch
from
547ce08
to
750c58c
Compare
|
Could you review this when you have some time? cc @dongjoon-hyun @cloud-fan |
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?
Currently, 'HADOOP_CONF_DIR' in ENV and Hadoop configmap cannot be both configured. However, in cloud vendor EMR environments, 'HADOOP_CONF_DIR' is often already configured. This issue is introduced to preferentially use the configmap specified through the property spark.kubernetes.hadoop.configMapName without changing the environment variables.
Why are the changes needed?
More convenient to use in cloud vendor environments.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit testing.
Was this patch authored or co-authored using generative AI tooling?
No.