You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Cleveland, Michael" <Mi...@breadfinancial.com> on 2022/06/02 14:16:41 UTC
Log4j 1.2 update timeline?
Good morning,
I was wondering if there was a timeline when the version of Log4j will be updated when using Kafka?
Thank you,
Michael Cleveland
______________________________________________________________________
The information contained in this e-mail message and any attachments may be privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this e-mail and delete the message and any attachments from your computer.
______________________________________________________________________
Re: Log4j 1.2 update timeline?
Posted by Tom Bentley <tb...@redhat.com>.
Hi Michael,
KIP-653 seeks to update the log4jv1 dependency to log4jv2. Following a
discussion a month or so ago [1] I think the plan is to do this in Kafka
4.0. The discussion for KIP-833 [2] suggests we'll see Kafka 3.5 followed
by Kafka 4.0, which should be around August 2023 (assuming we stick to the
usual time-based releases).
If you're asking for log4shell reasons, Kafka 3.2.0 and 3.1.1 use reload4j
instead of the original log4jv1 implementation.
Hopefully this answers your question.
Kind regards,
Tom
[1]: https://lists.apache.org/thread/qo1y3249xldt4cpg6r8zkcq5m1q32bf1
[2]: https://lists.apache.org/thread/90zkqvmmw3y8j6tkgbg3md78m7hs4yn6
On Thu, 2 Jun 2022 at 18:03, Cleveland, Michael <
Michael.Cleveland@breadfinancial.com> wrote:
> Good morning,
>
> I was wondering if there was a timeline when the version of Log4j will be
> updated when using Kafka?
>
> Thank you,
> Michael Cleveland
>
> ______________________________________________________________________
> The information contained in this e-mail message and any attachments may
> be privileged and confidential. If the reader of this message is not the
> intended recipient or an agent responsible for delivering it to the
> intended recipient, you are hereby notified that any review, dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this communication in error, please notify the sender
> immediately by replying to this e-mail and delete the message and any
> attachments from your computer.
> ______________________________________________________________________
Re: Log4j 1.2 update timeline?
Posted by "Cleveland, Michael" <Mi...@breadfinancial.com>.
Any word on this timeline by chance?
Michael Cleveland (He/Him/His)
Senior Mac Support Engineer, Engineering
Working from Syracuse, New York
Office: (516) 600-0927
BreadFinancial.com<https://www.BreadFinancial.com>
Alliance Data is now Bread Financial
[cid:image001.png@01D8773C.16A5B010]<https://www.breadfinancial.com/>
[cid:image002.png@01D8773C.16A5B010]<https://www.linkedin.com/company/bread-financial>
[cid:image003.png@01D8773C.16A5B010]<https://www.facebook.com/breadfinancial>
[cid:image004.png@01D8773C.16A5B010]<https://www.twitter.com/BreadFinancial>
[cid:image005.png@01D8773C.16A5B010]<https://www.instagram.com/breadfinancial>
From: Cleveland, Michael <Mi...@breadfinancial.com>
Date: Thursday, June 2, 2022 at 10:16 AM
To: dev@kafka.apache.org <de...@kafka.apache.org>
Subject: Log4j 1.2 update timeline?
Good morning,
I was wondering if there was a timeline when the version of Log4j will be updated when using Kafka?
Thank you,
Michael Cleveland
______________________________________________________________________
The information contained in this e-mail message and any attachments may be privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this e-mail and delete the message and any attachments from your computer.
______________________________________________________________________