Adapt log4j2 to support Spark 3.3 #21
Open
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
|
support bandwidth limit ？ |
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.
Why changes are needed?
Since Spark 3.3, it migrate from Log4J 1.x to Log4J 2.x, see details in SPARK-37814
Currently, the
Logginghas a hard dependency on Log4J1, which does not work on Spark 3.3 and above.What are the changes?
This PR aims to use reflection to adapt both Log4J1 and Log4J2 to resolve such a compatible issue.
How was it verified?
A new test case
TestChangeLoggerLevelis added, also updated the Azure pipeline definition to include the Spark 3.3