[#11053] improvement(deps): Upgrade Log4j from 2.24.3 to 2.25.4 - #11054
Merged
Conversation
Code Coverage Report
|
danhuawang
pushed a commit
to danhuawang/gravitino
that referenced
this pull request
Jun 8, 2026
…apache#11054) ### What changes were proposed in this pull request? Upgrade Log4j from 2.24.3 to 2.25.4 in `gradle/libs.versions.toml`. ### Why are the changes needed? Log4j 2.25.4 includes fixes for log injection, malformed XML/JSON output, and improved configuration attribute handling. Keeping dependencies up to date reduces the surface area flagged by security scanners and ensures we benefit from upstream bug fixes. Gravitino uses only standard PatternLayout with common date patterns (`%d{yyyy-MM-dd HH:mm:ss.SSS}`), so the behavioral changes introduced in 2.25.0 (date formatting, exception converter defaults) do not affect the project. Fix: apache#11053 ### Does this PR introduce _any_ user-facing change? No. The logging output format remains unchanged since Gravitino uses explicit date patterns that are compatible across versions. ### How was this patch tested? - `./gradlew :core:test :server:test -PskipITs` — all tests pass - `./gradlew :catalogs:hive-metastore-common:test :iceberg:iceberg-common:test -PskipITs` — all tests pass - Compilation verified across core, server, and api modules
danhuawang
pushed a commit
to danhuawang/gravitino
that referenced
this pull request
Jun 9, 2026
…apache#11054) ### What changes were proposed in this pull request? Upgrade Log4j from 2.24.3 to 2.25.4 in `gradle/libs.versions.toml`. ### Why are the changes needed? Log4j 2.25.4 includes fixes for log injection, malformed XML/JSON output, and improved configuration attribute handling. Keeping dependencies up to date reduces the surface area flagged by security scanners and ensures we benefit from upstream bug fixes. Gravitino uses only standard PatternLayout with common date patterns (`%d{yyyy-MM-dd HH:mm:ss.SSS}`), so the behavioral changes introduced in 2.25.0 (date formatting, exception converter defaults) do not affect the project. Fix: apache#11053 ### Does this PR introduce _any_ user-facing change? No. The logging output format remains unchanged since Gravitino uses explicit date patterns that are compatible across versions. ### How was this patch tested? - `./gradlew :core:test :server:test -PskipITs` — all tests pass - `./gradlew :catalogs:hive-metastore-common:test :iceberg:iceberg-common:test -PskipITs` — all tests pass - Compilation verified across core, server, and api modules
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
Upgrade Log4j from 2.24.3 to 2.25.4 in
gradle/libs.versions.toml.Why are the changes needed?
Log4j 2.25.4 includes fixes for log injection, malformed XML/JSON output, and improved configuration attribute handling. Keeping dependencies up to date reduces the surface area flagged by security scanners and ensures we benefit from upstream bug fixes.
Gravitino uses only standard PatternLayout with common date patterns (
%d{yyyy-MM-dd HH:mm:ss.SSS}), so the behavioral changes introduced in 2.25.0 (date formatting, exception converter defaults) do not affect the project.Fix: #11053
Does this PR introduce any user-facing change?
No. The logging output format remains unchanged since Gravitino uses explicit date patterns that are compatible across versions.
How was this patch tested?
./gradlew :core:test :server:test -PskipITs— all tests pass./gradlew :catalogs:hive-metastore-common:test :iceberg:iceberg-common:test -PskipITs— all tests pass