[SPARK-45431][DOCS] Document new SSL RPC feature #43240
Closed
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
hasnain-db
force-pushed
the
spark-tls-docs
branch
from
e71d443
to
7be2a62
Compare
|
@mridulm could you look at this one when you have a chance? (or recommend a different reviewer if someone else is more suited to review docs PRs) |
mridulm
reviewed
Oct 30, 2023
mridulm
reviewed
Oct 30, 2023
mridulm
reviewed
Oct 30, 2023
|
+CC @JoshRosen as well. |
hasnain-db
force-pushed
the
spark-tls-docs
branch
from
a781f10
to
fa9ca55
Compare
mridulm
reviewed
Nov 7, 2023
|
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?
Add some documentation to clarify the new flags being added and how this feature interacts with existing SSL and encryption support. It's a little confusing so feedback is welcome.
Note I am not sure if it's best practice to merge this after the feature is fully merged - thought I would put this up now since it's unblocked.
Why are the changes needed?
New features require documentation so users can understand how to use them.
Does this PR introduce any user-facing change?
Yes, this is adding documentation for a new feature
How was this patch tested?
Not applicable, this is documentation
Was this patch authored or co-authored using generative AI tooling?
No