[SPARK-41528][CONNECT][FOLLOW-UP] Do not set null as a string for remote option #39168
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
|
Please let me go and merge this one to recover the PySpark shall .. Otherwise, the very entry point is broken, and I am 100% sure this is the right fix. Merged to master. |
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?
This PR is a followup of #39041 that avoids to set
nullas string for remote configuration and option.Why are the changes needed?
To make the default as the regular PySpark as is. Otherwise, it attempts to create remote SparkSession by default, which later fails because of
nullSpark Connect URL.Does this PR introduce any user-facing change?
No, the main code has not be released yet.
It fixes
./bin/pysparkcase.How was this patch tested?
Manually tested via: