The KIP freeze is just about having the KIP accepted. Not sure why we would
need an exception for that.
Ismael
On Wed, May 15, 2024 at 9:20 AM Chris Egerton
wrote:
> FWIW I think that the low blast radius for KIP-1028 should allow it to
> proceed without adhering to the usual KIP and feature
Hi Christopher,
Thanks for raising this. Moving to the new namespace makes sense - would
you be willing to submit a KIP? The point you raised regarding Jetty 11 EOL
and Jetty 12 requiring Java 17 is a good one and is worth discussing the
trade-offs in more detail. I originally did not propose
Hi team,
We should focus on regressions and cve fixes for releases like this one
(second bug fix and it's not the most recently released version). The idea
is to reduce the risk of regressions since it may well be the last official
release on this branch.
Ismael
On Thu, Mar 14, 2024, 1:39 AM
An alternative would be to have a convention for personal branches. For
example "tmp/ijuma/blah". I don't have a strong opinion, but it seems
useful if people want to collaborate on a branch.
Ismael
On Wed, Mar 13, 2024 at 11:02 AM Mickael Maison
wrote:
> Hi,
>
> We have accumulated a number
[
https://issues.apache.org/jira/browse/KAFKA-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-16226.
-
Resolution: Fixed
> Java client: Performance regression in Trogdor benchmark with h
+1 (binding)
Thanks for the KIP.
On Sun, Nov 19, 2023, 10:28 PM Krishna Agarwal
wrote:
> Hi,
> I'd like to call a vote on KIP-974 which aims to publish a docker image for
> GraalVM based Native Kafka Broker.
>
> KIP -
>
>
Hi,
mvnrepository doesn't matter, we should update the guidelines to remove it.
All that matters is that it has reached the maven central repository.
Ismael
On Tue, Feb 27, 2024 at 9:49 AM Stanislav Kozlovski
wrote:
> The thinking is that it is available for use - and it is in maven central -
nformation is not at all in the Jenkins report. I am still
> experimenting with printing the flaky tests somewhere. I will update this
> thread if I get something working. In the meantime, I wanted to gauge
> whether there is support for it.
>
> Cheers,
> David
>
> On Mon, Feb 12, 20
Hi David,
Your message didn't make this clear, but you are saying that Jenkins does
_not_ support the flakyFailure element and hence this information will be
completely missing from the Jenkins report. Have we considered including
the flakyFailure information ourselves? I have seen that being
Also, on the mockito stubbings point, we did upgrade to Mockito 5.8 for the
Java 11 and newer builds:
https://github.com/apache/kafka/blob/trunk/gradle/dependencies.gradle#L64
So, we should be good when it comes to that too.
Ismael
On Fri, Feb 9, 2024 at 4:15 PM Ismael Juma wrote:
> N
unit tests that we aren't running today.
>
> Thanks!
> Greg
>
> [1] https://github.com/apache/kafka/pull/15349
>
> On Fri, Feb 9, 2024 at 9:25 AM Ismael Juma wrote:
> >
> > Please check https://github.com/apache/kafka/pull/14186 before making
> the
> > `
those suites", can we run these 2 tasks in the
> same machine? So they won't need to compile classes twice for the same
> exact code?
>
> On Fri, Feb 9, 2024 at 6:05 PM Ismael Juma wrote:
>
> > Why can't we add @Tag("integration") for all of those tests?
PR (these we have definitely more than 8 per day)
> and
> > > this should be used to ensure changes are safe and sound. I'm not sure
> if
> > > having unit tests run as well before the merge itself would cause too
> much
> > > of an extra load on the CI machines
Hi David,
I think this is a helpful thing (and something I hoped we would use when I
learned about it), but it does require the validation checks to be reliable
(or else the PR won't be merged). Sounds like you are suggesting to skip
the tests for the merge queue validation. Could we perhaps
Hi Ziming,
Have you verified that the issue only impacts append/subtract? The way I
read the JIRA is that the issue currently affects all operations for
plugins, but it can be fixed to only affect append/subtract (where it would
be harder to fix). It would be good to verify the current state.
complexities of unstable metadata
> versions (and their risks).
>
> I am ok with options 2 and 2 as well by the way.
>
> Justine
>
> On Fri, Jan 12, 2024 at 7:36 AM Ismael Juma wrote:
>
> > Hi,
> >
> > Thanks for the KIP.
> >
> > Reading the
Hi,
Thanks for the KIP.
Reading the discussion, I think a lot of the confusion is due to the
"unstable" naming. People are then trying to figure out when we think
something is stable in the "this is battle-tested" sense. But this flag
should not be about that. We can have an MV for a feature
ed, Jan 10, 2024 at 3:58 PM Mickael Maison
> wrote:
>
> > I asked for details about the future of log4j2 on the logging user list:
> > https://lists.apache.org/thread/6n6bkgwj8tglgdgzz8wxhkx1p1xpwodl
> >
> > Let's see what they say.
> >
> >
Hi Mickael,
Thanks for starting the discussion and for summarizing the state of play. I
agree with you that it would be important to understand how long log4j2
will be supported for. An alternative would be sl4fj 2.x and logback.
Ismael
On Wed, Jan 10, 2024 at 2:17 PM Mickael Maison
wrote:
>
large.
> > >
> > > Yes log4j3 was on my mind as it's expected to be compatible with
> > > log4j2 and bring significant improvements.
> > >
> > > 0: https://github.com/apache/kafka/pull/10244
> > > 1: https://github.com/apache/kafka/pull/7898
Ismael Juma created KAFKA-16096:
---
Summary: Drop broker and tools support for Java 11 in Kafka 4.0
(deprecate in 3.7) (KIP-1013)
Key: KAFKA-16096
URL: https://issues.apache.org/jira/browse/KAFKA-16096
Hi all,
The vote passes with:
* 8 binding votes (Justine Olshan, Satish Duggana, Viktor Somogyi-Vass,
Divij Vaidya, Mickael Maison, Greg Harris, David Arthur, myself)
* 1 non-binding vote (Kamal Chandraprakash)
Thanks,
Ismael
On Wed, Jan 3, 2024 at 2:28 AM Ismael Juma wrote:
> Hi all,
&g
modules are getting published.
>
> This seems bad. Is there a reason to publish modules that are only used by
> the server on Sonatype?
>
> best,
> Colin
>
>
> On Mon, Jan 8, 2024, at 12:50, Ismael Juma wrote:
> > Hi Colin,
> >
> > I think you may have
Hi Colin,
I think you may have misunderstood what they mean by gradle metadata - it's
not the Kafka metadata module.
Ismael
On Mon, Jan 8, 2024 at 9:45 PM Colin McCabe wrote:
> Oops, hit send too soon. I see that #15127 was already merged. So we
> should no longer be publishing :metadata as
I agree with Colin. Also, 4.0 would be started after 3.8 is branched (not
after 3.8.0 is released). The rest looks good.
Thanks!
Ismael
On Fri, Jan 5, 2024 at 11:27 PM Colin McCabe wrote:
> Hi,
>
> Thanks for calling the vote, Josep.
>
> I re-checked this, and saw something that we missed
Hi Mickael,
Given that KIP-653 was accepted, the current position is that we would move
to log4j2 - provided that someone is available to drive that. It's also
worth noting that log4j3 is now a thing (but not yet final):
https://logging.apache.org/log4j/3.x/
Ismael
On Thu, Jan 4, 2024 at 2:15
Hi Ziming,
Why is the flag required at all? Can we use incremental and fallback
automatically if it's not supported by the broker? At this point, the vast
majority of clusters should support it.
Ismael
On Mon, Dec 18, 2023 at 7:58 PM ziming deng
wrote:
>
> Hello, I want to start a discussion
nd has reached a
> > > > > level of maturity that has led to its adoption by several other
> major
> > > > > projects, signifying its reliability and effectiveness.
> > > > >
> > > > > +1 (binding)
> > > > >
> > > > >
> > >
Hi all,
I would like to start a vote on KIP-1013.
As stated in the discussion thread, this KIP was proposed after the KIP
freeze for Apache Kafka 3.7, but it is purely a documentation update (if we
decide to adopt it) and I believe it would serve our users best if we
communicate the deprecation
It seems like people are generally in favor, I'll start a vote thread.
Ismael
On Fri, Dec 22, 2023 at 10:39 AM Ismael Juma wrote:
> Hi all,
>
> I was watching the Java Highlights of 2023 from Nicolai Parlog[1] and it
> became clear that many projects are moving to Java 17 for i
I should also clarify that Chia-Ping took it over from me originally and
improved the proposal significantly. I think he also got busy and hasn't
been able to spend time on it for a while though.
Ismael
On Tue, Jan 2, 2024 at 4:08 PM Ismael Juma wrote:
> I had written a KIP a while b
I had written a KIP a while back:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=100829459
Happy for someone to pick it up and drive it forward.
Ismael
On Tue, Jan 2, 2024 at 2:00 PM Justine Olshan
wrote:
> Hey folks --
> I think this is a good conversation. Given we plan
Congratulations Divij!
Ismael
On Wed, Dec 27, 2023 at 3:46 AM Luke Chen wrote:
> Hi, Everyone,
>
> Divij has been a Kafka committer since June, 2023. He has remained very
> active and instructive in the community since becoming a committer. It's my
> pleasure to announce that Divij is now a
c 26, 2023 at 3:57 PM Ismael Juma wrote:
>
> > Hi Colin,
> >
> > A couple of comments:
> >
> > 1. It is true that full support for OpenJDK 11 from Red Hat will end on
> > October 2024 (extended life support will continue beyond that), but
> Temurin
>
to JDK 21 instead with 4.0, instead of JDK 17.
>
> (As a one-off anecdote, a recent performance regression was found in 17,
> https://bugs.openjdk.org/browse/JDK-8317960, which was already fixed in
> 21)
>
> --
> Divij Vaidya
>
>
>
> On Tue, Dec 26, 2023 at 9:58 PM I
just that module with JDK11 would be a good
> idea? I'm not sure what the easiest way to build just one module is --
> hopefully we don't have to go through maven or something.
>
> best,
> Colin
>
>
> On Fri, Dec 22, 2023, at 10:39, Ismael Juma wrote:
> > Hi all,
> &g
[
https://issues.apache.org/jira/browse/KAFKA-15493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-15493.
-
Resolution: Fixed
We can mark this as fixed. I ran the system tests with Java 21
+1. I don't think we need a full vote for a change like this btw. :)
Ismael
On Tue, Dec 26, 2023, 9:04 AM Greg Harris
wrote:
> Hi Connect Developers,
>
> I noticed recently that we had two Jira components: "KafkaConnect" and
> "connect", one with >1000 issues and one with 20 issues. I merged
Hi all,
I was watching the Java Highlights of 2023 from Nicolai Parlog[1] and it
became clear that many projects are moving to Java 17 for its developer
productivity improvements. It occurred to me that there is also an
opportunity for the Apache Kafka project and I wrote a quick KIP with the
ring Director, aivenjosep.p...@aiven.io |
> +491715557497 | aiven.io
> Aiven Deutschland GmbH
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>
> On Thu, Dec 21, 2023, 17:58 Ismael Juma wrote:
&g
volunteers?
Ismael
On Tue, Nov 21, 2023 at 8:18 PM Ismael Juma wrote:
> Hi Luke,
>
> I think we're conflating different things here. There are 3 separate
> points in your email, but only 1 of them requires 3.8:
>
> 1. JBOD may have some bugs in 3.7.0. Whatever bugs exist can be fi
Hi Divij,
Comments inline.
On Thu, Dec 21, 2023 at 7:00 AM Divij Vaidya
wrote:
> 1\ Durability/availability bugs in kraft - Even though kraft has been
> around for a while, we keep finding bugs that impact availability and data
> durability in it almost with every release [1] [2]. It's a
we never shipped
> it.
>
> Thanks,
> Mickael
>
>
> On Wed, Dec 20, 2023 at 4:28 PM Ismael Juma wrote:
> >
> > Hi Mickael,
> >
> > A couple of comments inline.
> >
> > On Wed, Dec 20, 2023 at 3:34 AM Mickael Maison >
> > wrote:
> >
&
Hi Mickael,
A couple of comments inline.
On Wed, Dec 20, 2023 at 3:34 AM Mickael Maison
wrote:
> When you say, "we have opted to take a different approach", who is
> "we"? I think this decision should be made by the committers.
>
Changes can only be merged by committers, so I think it's
t; > >>> before I open a PR.
> > >>>
> > >>> Regards,
> > >>> Nick
> > >>>
> > >>> On Tue, 21 Nov 2023 at 11:27, Mayank Shekhar Narula <
> > >>> mayanks.nar...@gmail.com> wrote:
> > >&g
Thanks for the KIP. I think one of the main benefits of the change isn't
listed: sensitive configs make it impossible to make updates with the
current cli tool because sensitive config values are never returned.
Ismael
On Mon, Dec 18, 2023 at 7:58 PM ziming deng
wrote:
>
> Hello, I want to
=235838251=18=17
The main impact is that we will deprecate and remove fewer consumer related
api versions - fetch, group and offset management primarily (fetch was the
most impacted).
Ismael
On Tue, Nov 21, 2023 at 12:06 PM Ismael Juma wrote:
> Hi all,
>
> I would like to start a vote o
es
> .
> > Once method negotiation is complete using `SaslHandshake`, then we still
> > support direct authentication using the SASL protocol (i.e. without the
> > wrapped `SaslAuthenticate`). It would be nice to drop this as well, but
> it
> > looks like kafka-python may n
Ismael Juma created KAFKA-15959:
---
Summary: Replace byte handling classes with synchronized methods
Key: KAFKA-15959
URL: https://issues.apache.org/jira/browse/KAFKA-15959
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-14527.
-
Resolution: Won't Do
Closing as "Won't do" for now. We'll start with K
Ismael Juma created KAFKA-15899:
---
Summary: Move kafka.security package from core to server module
Key: KAFKA-15899
URL: https://issues.apache.org/jira/browse/KAFKA-15899
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-14526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-14526.
-
Resolution: Won't Do
Marking this as "Won't do" for now in favor of KAFKA-15852. O
[
https://issues.apache.org/jira/browse/KAFKA-14528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-14528.
-
Resolution: Won't Do
Marking this as "Won't Do" for now in favor of KAFKA-1
Hi all,
I also vote +1.
The vote passes with 4 binding +1s:
1. Colin McCabe
2. Jun Rao
3. Jose Sancio
4. Ismael Juma
Thanks,
Ismael
On Tue, Nov 21, 2023 at 12:06 PM Ismael Juma wrote:
> Hi all,
>
> I would like to start a vote on KIP-896. Please take a look and let us
> know wh
quot;validVersions"?
>
> Thanks and BR,
> Anton
>
> [1]: https://github.com/Aiven-Open/kio
>
> On 2023/01/03 16:17:24 Ismael Juma wrote:
> > Hi all,
> >
> > I would like to start a discussion regarding the removal of very old
> client
> > protoco
A-15552?jql=project%20%3D%20KAFKA%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%203.6.1%20ORDER%20BY%20priority%20DESC%2C%20status%20DESC%2C%20updated%20DESC
> > > > > >
> > > > > > Thanks,
> > > > > > Mickael
>
> and installing the missing packages(glibc and bash), I have proposed the
> alpine image as the base image. Let me know if you have any suggestions.
> I have added a detailed section for the same in the KIP.
>
> Regards,
> Krishna
>
> On Wed, Nov 22, 2023 at 8:08 PM Ismae
Hi,
One question I have is regarding the choice to use alpine - it would be
good to clarify if there are downsides (the upside was explained - images
are smaller).
Ismael
On Fri, Sep 8, 2023, 12:17 AM Krishna Agarwal
wrote:
> Hi,
> I want to submit a KIP to deliver an experimental Apache
lugin and we could use
> gradle enterprise for this. Or do you think that reporting the flaky tests
> in the build results is required?
>
> David
>
> On Wed, Nov 22, 2023 at 9:35 AM Ismael Juma wrote:
>
> > Hi David,
> >
> > Did you take a look at https://
vid
>
> [1]
> https://docs.gradle.org/current/userguide/java_testing.html#mergereruns
> [2] https://github.com/gradle/gradle/issues/23324
> [3] https://github.com/apache/kafka/pull/14687
>
>
> On Wed, Nov 22, 2023 at 4:10 AM Ismael Juma wrote:
>
> > Hi,
> >
&g
Hi Luke,
I think we're conflating different things here. There are 3 separate points
in your email, but only 1 of them requires 3.8:
1. JBOD may have some bugs in 3.7.0. Whatever bugs exist can be fixed in
3.7.x. We have already said that we will backport critical fixes to 3.7.x
for some time.
=17767394=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17767394
>
>
>
> > 15 нояб. 2023 г., в 09:18, Ismael Juma написал(а):
> >
> > To use the pain analogy, people seem to have really good painkillers and
> > hence they somehow don't feel the pa
t; >
> > best,
> > Colin
> >
> > On Tue, Nov 21, 2023, at 12:36, Ismael Juma wrote:
> > > Hi Colin,
> > >
> > > That change was proposed and approved via KIP-724:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/d
Ismael Juma created KAFKA-15874:
---
Summary: Add metric and request log attribute for deprecated
request api versions
Key: KAFKA-15874
URL: https://issues.apache.org/jira/browse/KAFKA-15874
Project
somewhere that the message.format.version configuration will
> be gone in 4.0? We only will support one message format version (for now,
> at least). If we do want more versions later, I don't think we'll want to
> configure them via a static config.
>
> best,
> Colin
>
>
> On Tue, Nov 21, 2023, at
I started a vote thread for this since I addressed the comments so far and
it doesn't seem like there were any major concerns.
Ismael
On Tue, Jan 3, 2023 at 8:17 AM Ismael Juma wrote:
> Hi all,
>
> I would like to start a discussion regarding the removal of very old
> client
Hi all,
I would like to start a vote on KIP-896. Please take a look and let us know
what you think.
Even though most of the changes in this KIP will be done for Apache Kafka
4.0, I would like to introduce a new metric and new request log attribute
in Apache 3.7 to help users identify usage of
Hi Jose,
I updated the KIP to include a new metric for deprecated request api
versions and also a new attribute in the request log to make it easy to
find such entries,
Thanks,
Ismael
On Thu, Jan 12, 2023 at 1:03 AM Ismael Juma wrote:
> Hi Jose,
>
> I think it's reasonable to add
[
https://issues.apache.org/jira/browse/KAFKA-15854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-15854.
-
Fix Version/s: 3.7.0
Resolution: Fixed
> Move Java classes from kafka.ser
[
https://issues.apache.org/jira/browse/KAFKA-14819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-14819.
-
Fix Version/s: (was: 4.0.0)
Resolution: Won't Fix
As described in the KIP, we're
Ismael Juma created KAFKA-15854:
---
Summary: Move Java classes from kafka.server to the server module
Key: KAFKA-15854
URL: https://issues.apache.org/jira/browse/KAFKA-15854
Project: Kafka
Issue
Ismael Juma created KAFKA-15853:
---
Summary: Move KafkaConfig to server module
Key: KAFKA-15853
URL: https://issues.apache.org/jira/browse/KAFKA-15853
Project: Kafka
Issue Type: Sub-task
Ismael Juma created KAFKA-15852:
---
Summary: Move broker code from `core` to `broker` module
Key: KAFKA-15852
URL: https://issues.apache.org/jira/browse/KAFKA-15852
Project: Kafka
Issue Type
file a blocker JIRA so
> the pain surfaces on a release forcing us to do something about it.
>
> If there is no forcing function, it basically means we are willing to
> accept test gaps forever.
>
>
> -Matthias
>
> On 11/14/23 9:09 PM, Ismael Juma wrote:
> > Matthia
Nov 12, 2023 at 2:58 AM Justine Olshan
> >>>
> >>>> wrote:
> >>>>
> >>>>> I will say that I have also seen tests that seem to be more flaky
> >>>>> intermittently. It may be ok for some time and suddenly the CI is
> >>>
r to this timeline, I
> > would be happy to ceed the RM role to them but in the worst case
> scenario,
> > my offer to volunteer for Jan release could be considered as a backup.
> >
> > --
> > Divij Vaidya
> >
> >
> >
> > On Mon, Nov 13, 2023 at
gt; --
> Divij Vaidya
>
>
>
> On Mon, Nov 13, 2023 at 3:40 PM Ismael Juma wrote:
>
> > Hi Divij,
> >
> > I think we should be releasing 3.6.1 this year rather than next. There
> are
> > some critical bugs in 3.6.0 and I don't think we should be wa
Hi Divij,
I think we should be releasing 3.6.1 this year rather than next. There are
some critical bugs in 3.6.0 and I don't think we should be waiting that
long to fix them. What do you think?
Ismael
On Mon, Nov 13, 2023 at 6:32 AM Divij Vaidya
wrote:
> Hey folks,
>
>
> I'd like to volunteer
On Sat, Nov 11, 2023 at 10:32 AM John Roesler wrote:
> In other words, I’m biased to think that new flakiness indicates
> non-deterministic bugs more often than it indicates a bad test.
>
My experience is exactly the opposite. As someone who has tracked many of
the flaky fixes, the vast
One more thing:
3. If test flakiness is introduced by a recent PR, it's appropriate to
revert said PR vs disabling the flaky tests.
Ismael
On Sat, Nov 11, 2023, 8:45 AM Ismael Juma wrote:
> Hi David,
>
> I would be fine with:
> 1. Only allowing merges if the build is green
> 2
Hi David,
I would be fine with:
1. Only allowing merges if the build is green
2. Disabling all flaky tests that aren't fixed within a week. That is, if a
test is flaky for more than a week, it should be automatically disabled (it
doesn't add any value since it gets ignored).
We need both to make
rent, but still, they
> don't need public access because they can extend `ProducerConfig`, too
> for this case). -- To me, this falls into the category "simple thing
> should be easy, and hard things should be possible).
>
>
> -Matthias
>
>
> On 11/3/23 6:06 AM,
Hi Sophie,
I was trying to understand the goal of the change and it's not totally
clear to me. If the goal is to allow third party applications to customize
the logging behavior, why is the method protected instead of public?
Ismael
On Thu, Nov 2, 2023 at 9:55 PM Sophie Blee-Goldman
wrote:
>
; > > > >> any
> > > > >> > > last-minute without eating into the time people usually take
> > > > >> holidays. It
> > > > >> > > comes 12 days after the Feature Freeze.This is two days
> shorter
> > > than
> > > > >> the
> > &g
Thanks Sameer. My take is that we're better off waiting until after the 3.7
branch is created so that we can simply replace the zk mode with kraft mode
for each of these tests. We're only 1.5 months away from that.
Ismael
On Sun, Oct 29, 2023 at 4:27 PM Sameer Tejani
wrote:
> Hi everyone,
>
>
I think kafka-native is clearer. Over time, the graalvm images may be used
for production too.
Ismael
On Sat, Oct 28, 2023, 11:52 PM Manikumar wrote:
> Thanks for the explanation. I am fine with using ""kafka-local" as the
> image name.
>
> On Fri, Oct 27, 2023 at 11:47 AM Krishna Agarwal <
>
Thanks for the KIP Krishna - looking forward to this. +1 (binding).
On Thu, Oct 26, 2023 at 9:36 PM Krishna Agarwal <
krishna0608agar...@gmail.com> wrote:
> Hi,
> I'd like to call a vote on KIP-975 which aims to publish an official docker
> image for Apache Kafka.
>
> KIP -
>
>
CDS, which have also
> been detailed in the KIP.
>
> Thanks and regards,
> Vedarth
>
> On Wed, Oct 25, 2023 at 10:56 AM Ismael Juma wrote:
>
> > The reference I meant to include:
> >
> > https://docs.oracle.com/en/java/javase/17/vm/class-data-sharing.html
&g
The reference I meant to include:
https://docs.oracle.com/en/java/javase/17/vm/class-data-sharing.html
On Tue, Oct 24, 2023, 10:25 PM Ismael Juma wrote:
> Hi Krishna,
>
> One last question from me, did we confuse using AppCDS or Dynamic CDS?
>
> Thanks,
> Ismael
>
> On
Hi Krishna,
One last question from me, did we confuse using AppCDS or Dynamic CDS?
Thanks,
Ismael
On Tue, Oct 24, 2023, 9:54 PM Krishna Agarwal
wrote:
> Hi,
> Thanks for the insightful feedback on this KIP. If there are no further
> questions, I'm considering wrapping up this discussion
Greg,
Thanks for making the change and sharing the benefit with the overall group.
Ismael
On Mon, Oct 23, 2023 at 10:03 AM Greg Harris
wrote:
> Hey Kafka Developers,
>
> This is a small announcement that the gradle build now supports the
> git-worktree subcommand [1] on the 3.4, 3.5, 3.6, and
sing a new version
> of
>Kafka for the affected branch in such a scenario is a much cleaner
>approach. Added this as the accepted approach in the KIP.
>2. EOL policy: Updated in the KIP.
>
> Thanks and regards,
> Vedarth
>
> On Sun, Oct 22, 2023 at 11:20 PM Ismael Juma wr
>> development, but would it aim at production use cases too
> > > > > (docker-compose,
> > > > > >> Kubernetes, etc.)?
> > > > > >> 2. How do you plan to forward configs to the broker? Do we
> expect
> > a
> > > >
Ismael Juma created KAFKA-15623:
---
Summary: Migrate remaining tests in streams module to JUnit 5
Key: KAFKA-15623
URL: https://issues.apache.org/jira/browse/KAFKA-15623
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-12220.
-
Resolution: Fixed
> Replace PowerMock by Mock
[
https://issues.apache.org/jira/browse/KAFKA-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-12220:
-
> Replace PowerMock by Mockito
>
>
> Key:
[
https://issues.apache.org/jira/browse/KAFKA-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-12220.
-
Resolution: Duplicate
The remaining connect tests that need to be migrated are being tracked
[
https://issues.apache.org/jira/browse/KAFKA-13414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-13414.
-
Resolution: Fixed
KafkaConfigBackingStoreTest is being tracked via KAFKA-14132, marking
[
https://issues.apache.org/jira/browse/KAFKA-7686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-7686.
Resolution: Duplicate
> Remove PowerMock from Connect Te
Ismael Juma created KAFKA-15610:
---
Summary: Fix `CoreUtils.swallow()` test gaps
Key: KAFKA-15610
URL: https://issues.apache.org/jira/browse/KAFKA-15610
Project: Kafka
Issue Type: Bug
1 - 100 of 5342 matches
Mail list logo
