fix(deps): resolve logging conflicts from Hive Metastore #2648
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.
The
hive-metastore
dependency transitively introducedlogback-classic
andcommons-logging
, which conflicted with the project's existingslf4j-reload4j
logging setup. This caused the primary logging configuration to be ignored and replaced by unwanted default logging.This commit resolves the issue by:
logback-classic
,logback-core
, and the nativecommons-logging
implementation across all project configurations.jcl-over-slf4j
bridge dependency. This satisfies Hive's runtime requirement for thecommons-logging
API while redirecting its log calls to the project's unified SLF4J backend.