[SPARK-49678][CORE][FOLLOWUP] Support spark.master in SparkSubmitArguments
#48134
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
Member
Author
|
cc @HyukjinKwon |
viirya
approved these changes
Sep 17, 2024
Member
Author
|
Thank you, @viirya . |
Member
|
Could we maybe just reuse 'PYSPARK_SUBMIT_ARGS' environment variable set to '--master local[1]' if this is just dev/test only? I haven't tested cuz I am away from keyboard today but I think it should work. |
Member
Author
|
Sorry, @viirya and @HyukjinKwon . I closed this PR and will add a comment to the original PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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?
This PR is a follow-up in order to support
spark.masterinstead ofspark.test.master.spark.test.masterinSparkSubmitArguments#48126Why are the changes needed?
By reusing the official config name, we can avoid to add a new test configuration.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.