[#3320] fix(client): shadow slf4j for client-java-runtime #3331
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
### What changes were proposed in this pull request? shadow slf4j for client-java-runtime and spark-connector-runtime ### Why are the changes needed? some systems like spark 3.3 need low version log4j, will encounter the conflict bug: ``` java.lang.NoSuchMethodError: org.apache.logging.slf4j.Log4jLoggerFactory: method 'void <init>()' not found ``` fix: #3320 ### Does this PR introduce _any_ user-facing change? no ### How was this patch tested? existing tests
FANNG1
approved these changes
May 10, 2024
jerryshao
deleted the
cherry-pick-branch-0.5-4307d5f4f3fdab29fa2728ec2b7b344c44249d5c
branch
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?
shadow slf4j for client-java-runtime and spark-connector-runtime
Why are the changes needed?
some systems like spark 3.3 need low version log4j, will encounter the conflict bug:
fix: #3320
Does this PR introduce any user-facing change?
no
How was this patch tested?
existing tests