[SPARK-38544][BUILD] Upgrade log4j2 to 2.17.2 #35839
Closed
+9
−9
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
martin-g
approved these changes
Mar 14, 2022
yaooqinn
approved these changes
Mar 14, 2022
dongjoon-hyun
approved these changes
Mar 14, 2022
There was a problem hiding this comment.
+1, LGTM. Thank you, @LuciferYang and all!
Merged to master for Apache Spark 3.3.
|
thanks all |
|
https://github.com/Yikun/spark/runs/5543930959?check_suite_focus=true |
|
@dongjoon-hyun @yaooqinn should revert this first? I haven't found the cause of the failure yet |
|
Reverted through 2a63fea |
|
thanks @wangyum |
|
Thank you for reverting. |
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 aims to upgrade log4j2 to 2.17.2.
Why are the changes needed?
This version brings a lot of fixes released to log1.x support, the release notes and change report as follows:
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GA