[SPARK-46357] Replace incorrect documentation use of setConf with conf.set #44290
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
Contributor
Author
|
cc @gengliangwang for this minor documentation fix. (I just picked you since I see you recently worked on this file. Let me know if that's not appropriate.) |
yaooqinn
reviewed
Dec 12, 2023
yaooqinn
reviewed
Dec 12, 2023
yaooqinn
approved these changes
Dec 13, 2023
Member
|
Thanks @nchammas, merged to master |
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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?
setConfis a method onSQLContext. The docs perhaps used to refer toSQLContext, but now they refer toSparkSession, which does not have this method.This PR updates the docs to use the appropriate method for making configuration settings against
SparkSession.Why are the changes needed?
The current documentation is incorrect.
Does this PR introduce any user-facing change?
Yes.
How was this patch tested?
No testing.
Was this patch authored or co-authored using generative AI tooling?
No.