[SPARK-47721][DOC] Guidelines for the Structured Logging Framework #45862
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
Member
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
There was a problem hiding this comment.
Just a question. Which part do you mean by this, @gengliangwang ?
Yes, from Github copilot.
Member
Author
|
@dongjoon-hyun Thanks for pointing it out. I just updated the PR description. |
dongjoon-hyun
approved these changes
Apr 3, 2024
HyukjinKwon
approved these changes
Apr 3, 2024
Member
|
Merged to master. |
Contributor
|
Thanks for writing this. It's helpful |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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?
As suggested in https://github.com/apache/spark/pull/45834/files#r1549565157, I am creating initial guidelines for the structured logging framework.
Why are the changes needed?
We need guidelines to align the logging migration works in the community.
Does this PR introduce any user-facing change?
No
How was this patch tested?
It's just doc change.
Was this patch authored or co-authored using generative AI tooling?
Yes. Generated-by: GitHub Copilot 1.2.17.2887