Hi,
Could someone give me access to the Kafka Confluence space at
https://cwiki.apache.org/confluence/display/kafka? I'd like to write a KIP.
My confluence user is s...@apache.org.
t; provider
> > selection mechanism (`-Dslf4j.provider`) as a key feature.
> > Given that, I think the current title reflects the primary technical
> > change, while the KIP details explain the resulting benefits and
> > implementation approach.
> >
> > Best
The title of the KIP seems a little odd, because if I understand correctly,
the main change you want to make is to bundle multiple logging backends
with Kafka and make them selectable via a system property, and upgrading
sfl4j is a means to achieve that, not the goal itself?
Den fre. 21. mar. 2025
I'd like to have https://github.com/apache/kafka/pull/19221 included if
possible. Do you need me to open a new ticket for the backport, separate
from the original for 4.0.0 at
https://issues.apache.org/jira/browse/KAFKA-17078?
Den tors. 27. mar. 2025 kl. 03.03 skrev Luke Chen :
> Hi Matthias,
>
>
stem/commit/53b7016a0d3b0ba04a23b4b1892e1cf7f62ba0a5
>
> On Thu, Mar 27, 2025 at 7:39 PM Luke Chen wrote:
>
> > Hi Stig,
> >
> > Thanks for bringing this to us.
> > I'm +1 for backporting to 3.9 branch since there's no workaround for Java
> > 24.
&
24. I'll try to
> make a PR to fix that, which will probably require another bump of
> Spotbugs, which may prompt another backport PR.
>
> there is already a PR (https://github.com/apache/kafka/pull/19235)
>
> Best,
> Chia-Ping
>
> Stig Rohde Døssing 於 2025年3月29日 週六 上
Hi,
Some months ago, a reflective shim was added in
https://issues.apache.org/jira/browse/KAFKA-17078, in order to support
running Kafka with SASL on JDKs that no longer support the security
manager.
This shim was added only to Kafka 4.0, but backporting was discussed in
https://lists.apache.org/
e.
Den man. 17. mar. 2025 kl. 16.43 skrev Ismael Juma :
> Hi Stig,
>
> Kafka 4.0 is likely to be released in a day or two. Even so, I think it
> makes sense to revive the backporting thread given the lack of workaround
> for Java 24.
>
> Ismael
>
> On Mon, Mar 17, 202
rsion that understands Java 24 bytecode, so
the client at least should already run fine on Java 24 on 3.9.1.
Den fre. 4. apr. 2025 kl. 02.48 skrev Luke Chen :
> Hi Stig,
>
> Thanks for the investigation.
> I'll take a look.
>
> Thanks.
> Luke
>
> On Fri, Apr 4, 2025 at 2
>
> > Mickael Maison 於 2025年3月28日 下午6:43 寫道：
> >
> > Hi,
> >
> > I'm also supportive of backporting this change to the 3.9 branch.
> >
> > Thanks,
> > Mickael
> >
> >
> >
> >> On Fri, Mar 28, 2025 at 10:16 AM Stig Rohde Dø
gt; > For the Java 24 testing, it's fine we ship 3.9 without Java 24 test if
> > gradle release is delayed since this is also the state of what Kafka v4.0
> > is.
> >
> > So we should firstly test Java 23 in CI for 3.9. @Stig, could you help
> open
> > a PR fo
ead of the version trunk uses)
which are the component parts of that branch, except for the Jenkinsfile
update.
Once these are merged, a committer can do a PR to update the Jenkinsfile to
build on Java 23 as well.
Den ons. 2. apr. 2025 kl. 17.06 skrev Stig Rohde Døssing <
stigdoess...@gmail.com
The person doing the PR to update the Jenkinsfile should include these
changes, which were in the PR for trunk that updated Github Actions to run
Java 23
https://github.com/apache/kafka/commit/76a9df47ca6088361fe707a2946827f7558d9f71
Den tors. 3. apr. 2025 kl. 20.17 skrev Stig Rohde Døssing
13 matches
Mail list logo
