humashankar26 opened a new pull request, #6303: URL: https://github.com/apache/hive/pull/6303
What changes were proposed in this pull request? I've upgraded the logging infrastructure from SLF4J 1.7.x to 2.0.13. Since SLF4J 2.x moves from static binding to a ServiceLoader architecture, I realigned the bridges to prevent "silent" logging failures. Key changes include: Updating slf4j-api, slf4j-reload4j, and jcl-over-slf4j to 2.0.13 across the root, standalone-metastore, and storage-api. Switching the Log4j2 bridge to log4j-slf4j2-impl (2.24.3) to ensure Hive's internal metrics and timing systems can communicate with the new API. Why are the changes needed? Security: Resolves several CVEs associated with the older 1.7.x line. Stability: Modernizes the logging backend and fixes "NOP" (No-Operation) logger errors that were causing metrics and audit logs to be dropped silently. Does this PR introduce any user-facing change? No. This is a backend dependency and architectural alignment. How was this patch tested? Dependency Audit: Verified via mvn dependency:tree that all modules have converged on 2.0.13 with no legacy 1.7.x bindings remaining. Unit Tests: Confirmed that logging-dependent tests (e.g., TestAtlasLoadTask, TestHiveRemote, and TestOperationLogManager) are passing, specifically verifying that metrics and API timing strings are correctly captured. Build Integrity: Passed a clean local build to ensure no compilation regressions in ql or service modules. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
