[
https://issues.apache.org/jira/browse/SPARK-37814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487591#comment-17487591
]
Dongjoon Hyun commented on SPARK-37814:
---------------------------------------
I don't think so, [~sldr] . Apache Spark community has own pre-defined release
cycle and we are already working hard at our best speed to achieve it in a
successful way. You should understand that (1) we are considering many
community requests in various dimension, (2) the reckless dependency changes
could affect most of the users seriously, and (3) how much efforts we are
putting in the community directions.
To be clear, Apache Spark 3.3 code freeze is already planned on March 15th
2022. This is the fastest attempt we can deliver.
- https://spark.apache.org/versioning-policy.html
> Migrating from log4j 1 to log4j 2
> ---------------------------------
>
> Key: SPARK-37814
> URL: https://issues.apache.org/jira/browse/SPARK-37814
> Project: Spark
> Issue Type: Umbrella
> Components: Build
> Affects Versions: 3.3.0
> Reporter: L. C. Hsieh
> Assignee: L. C. Hsieh
> Priority: Major
> Labels: releasenotes
> Fix For: 3.3.0
>
>
> This is umbrella ticket for all tasks related to migrating to log4j2.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
