This is an automated email from the ASF dual-hosted git repository.

yangjie01 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/master by this push:
     new c1ecab4d77b4 [SPARK-49541][BUILD] Upgrade log4j2 to 2.24.1
c1ecab4d77b4 is described below

commit c1ecab4d77b487c595028f8d33e3d1b41634b44e
Author: panbingkun <[email protected]>
AuthorDate: Thu Oct 3 15:28:41 2024 +0800

    [SPARK-49541][BUILD] Upgrade log4j2 to 2.24.1
    
    ### What changes were proposed in this pull request?
    The pr aims to upgrade log4j2 from `2.22.1` to `2.24.1`.
    
    ### Why are the changes needed?
    - The full release notes:
    https://github.com/apache/logging-log4j2/releases/tag/rel%2F2.24.1
    https://github.com/apache/logging-log4j2/releases/tag/rel%2F2.24.0
    https://github.com/apache/logging-log4j2/releases/tag/rel%2F2.23.1
    https://github.com/apache/logging-log4j2/releases/tag/rel%2F2.23.0
    
    - The new version contains some bug fixes:
    Fix regression in JdkMapAdapterStringMap performance. 
(https://github.com/apache/logging-log4j2/issues/2238)
    Fix NPE in PatternProcessor for a UNIX_MILLIS pattern 
(https://github.com/apache/logging-log4j2/issues/2346)
    Fix that parameterized message formatting throws an exception when there 
are insufficient number of parameters. It previously simply
    didn't replace the '{}' sequence. The behavior changed in 2.21.0 and should 
be restored for backward compatibility. 
(https://github.com/apache/logging-log4j2/issues/2380)
    Fix putAll() in the default thread context map implementation 
(https://github.com/apache/logging-log4j2/pull/2942)
    
    ### Does this PR introduce _any_ user-facing change?
    No.
    
    ### How was this patch tested?
    Pass GA.
    
    ### Was this patch authored or co-authored using generative AI tooling?
    No.
    
    Closes #48029 from panbingkun/SPARK-49541.
    
    Authored-by: panbingkun <[email protected]>
    Signed-off-by: yangjie01 <[email protected]>
---
 dev/deps/spark-deps-hadoop-3-hive-2.3 | 10 +++++-----
 pom.xml                               |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/dev/deps/spark-deps-hadoop-3-hive-2.3 
b/dev/deps/spark-deps-hadoop-3-hive-2.3
index f6ce3d25ebc8..5cba1c687e5a 100644
--- a/dev/deps/spark-deps-hadoop-3-hive-2.3
+++ b/dev/deps/spark-deps-hadoop-3-hive-2.3
@@ -189,11 +189,11 @@ leveldbjni-all/1.8//leveldbjni-all-1.8.jar
 libfb303/0.9.3//libfb303-0.9.3.jar
 libthrift/0.16.0//libthrift-0.16.0.jar
 
listenablefuture/9999.0-empty-to-avoid-conflict-with-guava//listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar
-log4j-1.2-api/2.22.1//log4j-1.2-api-2.22.1.jar
-log4j-api/2.22.1//log4j-api-2.22.1.jar
-log4j-core/2.22.1//log4j-core-2.22.1.jar
-log4j-layout-template-json/2.22.1//log4j-layout-template-json-2.22.1.jar
-log4j-slf4j2-impl/2.22.1//log4j-slf4j2-impl-2.22.1.jar
+log4j-1.2-api/2.24.1//log4j-1.2-api-2.24.1.jar
+log4j-api/2.24.1//log4j-api-2.24.1.jar
+log4j-core/2.24.1//log4j-core-2.24.1.jar
+log4j-layout-template-json/2.24.1//log4j-layout-template-json-2.24.1.jar
+log4j-slf4j2-impl/2.24.1//log4j-slf4j2-impl-2.24.1.jar
 logging-interceptor/3.12.12//logging-interceptor-3.12.12.jar
 lz4-java/1.8.0//lz4-java-1.8.0.jar
 metrics-core/4.2.27//metrics-core-4.2.27.jar
diff --git a/pom.xml b/pom.xml
index 6a77da703dbd..31046e5a85f8 100644
--- a/pom.xml
+++ b/pom.xml
@@ -120,7 +120,7 @@
     <sbt.project.name>spark</sbt.project.name>
     <asm.version>9.7</asm.version>
     <slf4j.version>2.0.16</slf4j.version>
-    <log4j.version>2.22.1</log4j.version>
+    <log4j.version>2.24.1</log4j.version>
     <!-- make sure to update IsolatedClientLoader whenever this version is 
changed -->
     <hadoop.version>3.4.0</hadoop.version>
     <!-- SPARK-41247: When updating `protobuf.version`, also need to update 
`protoVersion` in `SparkBuild.scala` -->


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to