Hi Andrew,
Thanks for the KIP. I have some comments/questions:
DJ1: In the motivation, you wrote the following: "You can’t see this group
in the list of consumer groups with the kafka-consumer-groups.sh tool, but
if you try to describe a consumer group called "connect-cluster" or even
use this
ently terminate another consumer, as it will always send a
> LEAVE_GROUP request upon closing, even if it hasn't received a heartbeat
> response. However, I tend to believe the risk is negligible 😀
>
> Best,
> Chia-Ping
>
>
> David Jacot 於 2024年9月23日 週一 下午9:
s the response with bumped epoch, and
> this
> > > case is recoverable.
> > >
> > > however, v1 brings a different fenced epoch scenario. Users, now, have
> > > responsibility to generate unique member id, hence clients may
> encounter
> > > infinite fenced
Hi all,
I would like to volunteer to be the release manager driving the next
release - Apache Kafka 4.0.0.
If there are no objections, I'll start building a release plan in the wiki
in the next couple of days.
Best,
David
Hi Matt,
Thanks for the KIP. I have a minor nit. Could you please explicitly mention
the new command line argument in the public interfaces section?
Otherwise, I am +1 (binding).
Best,
David
On Tue, Sep 24, 2024 at 1:48 AM Welch, Matt wrote:
> Hi Kafka Devs,
>
> Bumping VOTE thread again for
.”
> > I have updated the KIP accordingly.
> > Please take a look, and let me know if you have any thoughts or feedback.
> >
> > Thank you!
> >
> > Best regards,
> > TengYao
> >
> > Chia-Ping Tsai 於 2024年8月30日 週五 下午9:56寫道：
> >
&g
d to worry about the code duplication in
> ListConsumerGroupsResult,
> ListShareGroupsResult and ListGroupsResult because only the last of these
> would not be
> deprecated. As a result, introducing AbstractListGroupsResult now would
> not be worth the effort.
> We cannot deprecate
+1 (binding)
Thanks for the KIP!
Best,
David
On Thu, Oct 3, 2024 at 10:49 AM TengYao Chi wrote:
> Hello everyone,
> As the vote has been pending for two weeks, I would like to push it
> manually.
> Thank you for your attention.
>
> Best,
> TengYao
>
> Chris Egerton 於 2024年9月19日 週四 上午1:42寫道：
>
+1 (binding). Thanks for the KIP!
On Thu, Nov 7, 2024 at 7:51 PM Jun Rao wrote:
> Hi, Rajini,
>
> Thanks for the KIP. +1
>
> Jun
>
> On Tue, Nov 5, 2024 at 1:26 AM Rajini Sivaram
> wrote:
>
> > Hi everyone,
> >
> > I would like to start vote on KIP-1102 (
> >
> >
> https://cwiki.apache.org/conf
t;>>>>
> > >>>>>> Thanks for the review and suggestions.
> > >>>>>>
> > >>>>>> CI0: Thanks for the reminder. Update validVersions in
> > >>>>>> ConsumerGroupDescribeRequest to 0-1.
> > &
Add a new field protocol to MemberDescription,
> so the command line tool can show protocol information when users describe
> members.
>
> If there is no further suggestion, I will start a vote thread today.
>
> Thanks,
> PoAn
>
> > On Nov 15, 2024, at 11:50 PM, David
gt;
> > > [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1073%3A+Return+fenced+brokers+in+DescribeCluster+response
> > > [2] https://lists.apache.org/thread/zm5kk9st54rj6t5pw9v1dnxhk64mho4m
> > > [3] https://github.com/apache/kafka/pull/175
,
David
On Wed, Nov 20, 2024 at 12:02 PM David Jacot wrote:
> Hi Divij,
>
> I think that we can make a small exception for KIP-1030 but we cannot wait
> too long. How long do you need to close it? Ideally, we should aim for
> closing it in the next two weeks. If we cannot do it,
+1 (binding). Thanks for the KIP!
On Fri, Nov 15, 2024 at 5:48 PM Lianet M. wrote:
> Thanks for the KIP Manikumar! Nice improvement.
>
> +1 (binding)
>
> Lianet
>
> On Fri, Nov 15, 2024 at 11:46 AM David Arthur wrote:
>
> > Thanks!
> >
> > +1 binding
> >
> > On Fri, Nov 15, 2024 at 11:26 AM Man
essary giving that 4.0 will
> not remove `alterConfigs`, so I’m willing to maintain compatibility to the
> next period, for example 4.2, I will try to drive this smooth upgrade
> process.
>
> How do you think about it?
>
> Best,
> Ziming
>
>
> > On Nov 14, 2024, at 16:41,
Hi PoAn,
Thanks for the KIP! I have a few minor comments/suggestions:
DJ1: In the output of `--describe --verbose`, I would suggest putting
`GROUP-EPOCH` and `TARGET-ASSIGNMENT-EPOCH` before `#MEMBERS`.
DJ2: Continuing on the above, I assume that we will print out N/A for the
fields not supported
Hi Ziming,
I am not sure to understand the concern. What's wrong with keeping the
original plan? If I understood it correctly, the plan was to fail
directly if the incrementalAlterConfigs API is not available in 4.x
versions. The new API was introduced in AK 2.3. The likelihood of using the
update
> DJ4: It looks like DescribeGroupsResponseData only has protocol type at
> group level.
> > Both DescribeGroupsResponseData and ConsumerGroupDescribeResponseData
> don’t have protocol at member level.
> > Could we use a followup to add it?
> >
> > DJ5: Update KIP to put
> >>>> In ConsumerGroupDescription, it’s “true” when it’s a classic member.
> >>>> In ShareGroupDescription, it’s always “false”.
> >>>>
> >>>> Thanks,
> >>>> PoAn
> >>>>
> >>>>> On Nov 23, 2024,
+1 (binding)
In gmail, the discuss and the vote threads got merged somehow.
On Wed, Nov 20, 2024 at 4:47 AM Chia-Ping Tsai wrote:
> +1 (binding)
>
> On 2024/11/18 14:52:22 PoAn Yang wrote:
> > Hi All,
> >
> > I would like to start vote on KIP-1099:
> >
> https://cwiki.apache.org/confluence/disp
at his (new) consumer
> group
> >>> may have non-upgraded members yet. I wonder if we could use a boolean
> to
> >>> signal this, e.g. isLegacy. Then, in the CLI we could have a column
> which
> >>> is only displayed when they are non upgraded members. What d
ostpone doing it we can directly
> remove deprecated alterConfigs from ConfgCommand to avoid making our code
> dirty.
>
> --,
> Ziming
>
>
> > On Nov 20, 2024, at 18:04, David Jacot wrote:
> >
> > Hi all,
> >
> > This is a friendly reminder that the
gt; On Tue, Nov 26, 2024 at 4:10 PM David Jacot wrote:
>
> > Hi all,
> >
> > I just checked the release plan and it does not contain any
> > non-accepted KIPs. I added a few other accepted KIPs too.
> >
> > The feature freeze is on Dec. 11th.
> >
Hi all,
I just checked the release plan and it does not contain any
non-accepted KIPs. I added a few other accepted KIPs too.
The feature freeze is on Dec. 11th.
Best,
David
On Tue, Nov 26, 2024 at 8:38 AM David Jacot wrote:
>
> Hi PoAn/Ziming,
>
> Thanks for adding those to the
rding to Lucas’s comment, I add StreamsGroupMetadataValue update
> to this KIP.
>
> Thanks,
> PoAn
>
>
> > On Dec 20, 2024, at 3:58 PM, Chia-Ping Tsai wrote:
> >
> >> because assignors are sticky.
> >
> > I forgot about that spec again :(
> >
Hi Kamal,
It is fine to relax the constraint in StructSpec for your internal tags.
For instance, you could allow your internal tags to start from id 1. It
is very unlikely that we will ever have tags as part of the official
protocol reaching that.
Best,
David
On Mon, Feb 3, 2025 at 6:36 PM K
Hi Edoardo,
As it is a small bugfix, feel free to cherry-pick it to 4.0.
Best,
David
On Tue, Feb 11, 2025 at 11:52 AM Edoardo Comar wrote:
>
> Hi
> is it too late to cherry pick
> https://github.com/apache/kafka/pull/18833 on 4.0.0 ?
> (KAFKA-18758: NullPointerException in shutdown following
>
gt; > or
> > > >> > > so.
> > > >> > >
> > > >> > > Justine
> > > >> > >
> > > >> > > On Thu, Jan 23, 2025 at 9:55 AM Colin McCabe <
> cmcc...@apache.org>
> > &g
ints+and+default+values+for+various+configurations
> >>
> >>
> >> --
> >> Divij Vaidya
> >>
> >>
> >>
> >> On Tue, Nov 26, 2024 at 9:37 AM TengYao Chi
> wrote:
> >>
> >> > Hello D
Hi,
Thanks for the KIP. The community is pretty busy with the Apache Kafka 4.0
release so I suppose that no one really had the time to engage in reviewing
the KIP yet. Sorry for this!
I just read the motivation section. I think that it is an interesting idea.
However, I wonder if this is still ne
I have merged the PR (
>
> https://github.com/apache/kafka/commit/b37b89c6686f5270b37d39cf3144bccb4f5bceb2
> )
>
> will keep testing the related e2e
>
> Best,
> Chia-Ping
>
> David Jacot 於 2024年12月13日 週五 下午3:53寫道：
>
> > Hi Mickael/Chia-Ping,
> > Regardin
Hi PoAn,
Thanks for the KIP. I have some comments about it.
DJ01: Please, remove all the code from the KIP. We only care about public
interface changes, not about implementation details.
DJ02: Regarding the hash computation, I agree that we should use Murmur3.
However, I don't quite like the impl
Hello Kafka developers and friends,
As promised, we now have a release branch for 4.0 release.
Trunk has been bumped to 4.1.0-SNAPSHOT.
I'll be going over the JIRAs to move every non-blocker from this release to
the next release.
>From this point, most changes should go to trunk.
- Blockers (exi
hich the author is fixing. We will target to merge them this week.
>
>
> [1]
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1030%3A+Change+constraints+and+default+values+for+various+configurations
>
> --
> Divij Vaidya
>
>
>
> On Mon, Dec 16, 2024 at
Hi all,
As you may know, we've been working hard to graduate KIP-848 from
preview in Apache Kafka 3.8 to production-ready in Apache Kafka 4.0 —
exciting news!
KIP-848, the next-generation rebalance protocol, encompasses several
significant updates in the consumer and group coordinator areas,
incl
be deferred to
> next release ? For example:
> https://issues.apache.org/jira/browse/KAFKA-18034
> >
> > Best,
> > Chia-Ping
> >
> > On 2024/12/16 15:47:47 David Jacot wrote:
> >> Hello Kafka developers and friends,
> >>
> >> As promis
Hi Matthias,
You're absolutely right! Sorry for the confusion. I actually used the usual
message that we send out in all the releases. I will improve it in the
release document for the next time.
David
On Wed, Dec 18, 2024 at 8:58 AM David Jacot wrote:
> Hi Chia-Ping,
>
> Yes, w
> KIP instead, as the code for the warn log was merged with this ticket?
>
>
> -Matthias
>
>
> On 12/18/24 5:06 AM, David Jacot wrote:
> > Hi all,
> >
> > As we are past the feature freeze, I have updated the release plan [1]
> > and moved the non-ready K
ain to David. I am eagerly anticipating the release of version 4.0.0.
>
> Best,
> Chia-Ping
>
> On 2024/12/18 14:08:23 David Jacot wrote:
> > Hi all,
> >
> > As you may know, we've been working hard to graduate KIP-848 from
> > preview in Apache Kafka 3.8
ew it to determine if a quick KIP is necessary?
>
> thanks,
> Chia-Ping
>
> On 2024/12/11 08:45:54 David Jacot wrote:
> > Hi folks,
> >
> > Happy feature freeze day! Please remember that the big chunks of your
> KIPs
> > must be merged by today. In practice,
Thanks for running the release!
Le sam. 14 déc. 2024 à 00:33, Bill Bejeck a écrit :
> Thanks for running the release, Matthias!
> This one has some important fixes.
>
> -Bill
>
> On Fri, Dec 13, 2024 at 6:17 PM Matthias J. Sax wrote:
>
> > The Apache Kafka community is pleased to announce the r
1 to DJ04.
> However, the advantage of storing the topic cache in the metadata image is
> somewhat unclear to me. Could you please provide more details on what you
> mean by "tight"?Furthermore, since the metadata image is a thread-safe
> object, we need to ensure that the la
upgrade, there
> > would be extensive recomputing of old hashes.
> >
> > I believe this idea should also work for downgrades, and that's just my two
> > cents.
> >
> > Best,
> > Chia-Ping
> >
> >
> > On 2024/12/19 14:39:41 Davi
otocolType?
> >
> > This is not my comment ... sorry for the incorrect quote :(
> >
> >> A member in a classic group should report "classic".
> >
> > I completely agree. However, in this case,
> ClassicGroupDescription#protocol
> > returns 'cons
Hi David,
I think that there is a « kafka committer » team within the Apache
organization. You may be able to query it. It seems to be automatically
populated based on the roaster data.
Best,
David
Le mar. 3 déc. 2024 à 23:52, David Arthur a écrit :
> Chia-Ping,
>
> > Do we have documentation
Hi Kirk,
Thanks for raising this. In this case, the documentation is wrong so, in my
opinion, we could just fix it.
Best,
David
On Thu, Jan 9, 2025 at 2:52 AM Kirk True wrote:
> Hi all,
>
> Do we consider the CLI help/usage message as part of the publicly
> documented API?
>
> Background: Ther
s.apache.org/jira/browse/KAFKA-18627? This JIRA ticket
> > introduces a new system environment variable and (possibly) deprecates
> the
> > old one. Is it appropriate to include this change in 4.0?
> >
> > Thanks,
> > Chia-Ping
> >
> > On 2025/01/20 11:55:24
Hi all,
We are now past the code freeze. We have still a few blockers attached
to 4.0. I will review those to ensure that they are real blockers.
Please raise any new blockers in this thread.
Thanks,
David
On Thu, Dec 19, 2024 at 8:24 AM David Jacot wrote:
>
> Hi Matthias,
>
>
+1 (binding. Thanks for the KIP!
DJ
On Thu, Feb 13, 2025 at 10:57 AM Andrew Schofield <
andrew_schofield_j...@outlook.com> wrote:
> +1 (binding)
>
> Thanks for the KIP.
>
> Andrew
>
>
> From: TengYao Chi
> Sent: 13 February 2025 09:38
> To: dev@kafka.apa
Therefore, I plan to backport the fix to the 4.0.0 branch. The
> > root cause of the flakiness has been identified and documented in the jira.
> >
> > Best,
> > Chia-Ping
> >
> > On 2025/02/11 11:07:14 David Jacot wrote:
> > > Hi Edoardo,
> > >
>
Cancelling this vote because we need a new RC to include KAFKA-18979.
Best,
David
On Fri, Mar 14, 2025 at 8:30 AM Luke Chen wrote:
> Hi José,
>
> Thanks for the fix.
> The change makes sense to me.
>
> Thanks.
> Luke
>
> On Fri, Mar 14, 2025 at 8:03 AM José Armando García Sancio <
> jsan...@con
votes
* No votes
Vote thread:
https://lists.apache.org/thread/czxrsdsk9nw03rp7bzqhdjbt2wzhtjll
I'll continue with the release process and the release announcement will follow.
David Jacot
Liu, Chengyan,
Cheryl Simmons, Chia-Chuan Yu, Chia-Ping Tsai, Chirag Wadhwa, Chris
Egerton, Christo Lolov, Christopher L. Shannon, ClarkChen, Clay
Johnson, Colin P. McCabe, Colt McNealy, Danica Fine, Dániel Urbán,
David Arthur, David Jacot, David Mao, David Schlosnagle, Dejan
Stojadinović
ipse) in
> > docker container
> > - Executed all unit and integration tests
> > - Ran the quickstart successfully
> > - test console consumer and producer
> > - Tested dynamic voter with 4.0 and 3.9 controllers
> > - Tested 4.0 controller with a 3.9 broker
&
ocker Build Test Pipeline (JVM):
https://github.com/apache/kafka/actions/runs/13852844456
Docker Build Test Pipeline (Native):
https://github.com/apache/kafka/actions/runs/13853116713
/**
Thanks,
David Jacot
nsume/produce & topic management with the command line tools
> >> > >> > - Run client examples from the examples module (java 17)
> >> > >> > - Tested consuming in groups with both classic and new consumer
> >> > protocol
> &g
Hi Calvin,
Thanks for the update.
DJ03: I wonder whether we should call it `TransactionalIdPattern`. Filter
is a bit redundant in my opinion.
DJ04: The response could now return `INVALID_REGULAR_EXPRESSION` error if
the regex is invalid.
DJ05: Should we say that all transactions are returned if
n
>
> > On Apr 16, 2025, at 4:34 PM, David Jacot
> wrote:
> >
> > Hi PoAn,
> >
> > Thanks for your very detailed answers!
> >
> > DJ05: This seems reasonable. We can look into it more deeply during the
> > implementation too.
> >
> > D
+1 (binding). Thanks for the KIP!
David
On Wed, Apr 16, 2025 at 6:19 PM Andrew Schofield
wrote:
>
> +1 (binding)
>
> Thanks,
> Andrew
>
> From: Lucas Brutschy
> Sent: 16 April 2025 08:17
> To: dev@kafka.apache.org
> Subject: Re: [VOTE] KIP-1101: Trigger
ger all group rebalance at the same time.
> IMHO, I would prefer
> >> to keep the code simple.
> >>
> >> DJ08: Add ConsumerGroupHeartbeatRequestTest to test plan.
> >>
> >> LB01: Add the removal of StreamGroupPartitionMetadataKey /
> >> StreamGro
+1 (binding). Thanks for the KIP!
On Thu, Apr 24, 2025 at 5:30 PM Calvin Liu
wrote:
> Hi,
> I would like to start a vote on KIP-1152, thank you!
> KIP:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1152%3A+Add+transactional+ID+pattern+filter+to+ListTransactions+API
> Discussion threa
t; >> DJ02: As Kirk noted earlier, since the topic hash calculation is on
> > server
> > >> side (not client-side), we can safely introduce Guava as a dependency.
> > >>
> > >> If there is no other discussion, we can start voting in
> > >&g
he.kafka.coordinator.group.GroupCoordinatorShard)
> >>>>
> >>>> Not sure if that's expected or not.
> >>>>
> >>>> Thanks,
> >>>> Kirk
> >>>>
> >>>> On Wed, Feb 26, 2025, at 5:15 P
Hi Jun,
Thanks. I have cherry-picked
https://issues.apache.org/jira/browse/KAFKA-18864 to 4.0.
Best,
David
On Mon, Mar 3, 2025 at 3:18 PM David Jacot wrote:
> Hi all,
>
> I have opened https://github.com/apache/kafka/pull/19080 for Kirk's
> logging observation.
>
> B
Hi all,
I have opened https://github.com/apache/kafka/pull/19080 for Kirk's logging
observation.
Best,
David
On Mon, Mar 3, 2025 at 12:22 PM David Jacot wrote:
> Hi Bruno,
>
> Please go ahead and cherry-pick it to 4.0.
>
> Best,
> David
>
> On Mon, Mar 3, 2025 at
Test Pipeline (JVM):
https://github.com/apache/kafka/actions/runs/13735818889
Docker Build Test Pipeline (Native):
https://github.com/apache/kafka/actions/runs/13735821944
/**
Thanks,
David Jacot
PS: I used RC3 instead of RC2 by mistake.
e.
>
>
> -Matthias
>
> On 2/20/25 11:23 PM, David Jacot wrote:
> > Hi Andrew,
> >
> > Please go ahead and merge it to 4.0.
> >
> > Thanks,
> > David
> >
> > On Thu, Feb 20, 2025 at 6:25 PM Andrew Schofield <
> > andrew_schofield
potential 4.0.0 blocker since it may involve a protocol
> change.
>
> https://github.com/apache/kafka/pull/18726#discussion_r1972525165
>
> Thanks,
>
> Jun
>
> On Wed, Mar 5, 2025 at 7:38 AM David Jacot wrote:
>
> > We still have two documentation blockers:
>
Hi folks,
I have prepared the blog post for the 4.0.0 release. You can review it
here: https://github.com/apache/kafka-site/pull/668.
Best,
David
> <https://github.com/apache/kafka/pull/19172>to 4.0 branch if you don't
> have
> objections.
>
> Thanks.
> Luke
>
>
> On Mon, Mar 10, 2025 at 5:52 PM David Jacot
> wrote:
>
> > Hi Chia-Ping,
> >
> > Thanks. I will update the documentatio
Best,
> Chia-Ping
>
> On 2025/03/08 10:08:24 David Jacot wrote:
> > Hello Kafka users, developers and client-developers,
> >
> > This is the third candidate for release of Apache Kafka 4.0.0.
> >
> > - This is the first release without Apache Zookeeper
> &
me.
>
> Thanks.
> Luke
>
> On Thu, Mar 13, 2025 at 5:13 PM Chia-Ping Tsai wrote:
>
> > hi David and Josep
> >
> > I apologize for the hasty merge. Thank you, David, for promptly reverting
> > it
> >
> > Best,
> > Chia-Ping
> >
&
Awesome, thanks! I just merged it.
Best,
David
On Wed, Mar 12, 2025 at 3:33 PM 黃竣陽 wrote:
>
> Hello David,
>
> FYI, https://github.com/apache/kafka-site/pull/669 this PR resolve “1.7
> Compatibility” section is empty.
>
> Best,
> Jiunn-Yang
>
> > Dav
Hi all,
All the documentation blockers are now closed. Let's continue the
validation process. I don't expect to cut a new RC unless we find a
non-documentation blocker.
Best,
David
On Wed, Mar 12, 2025 at 3:37 PM David Jacot wrote:
>
> Awesome, thanks! I just merged it.
&
+1 (binding). Thanks for pushing this forward!
On Wed, Mar 5, 2025 at 8:30 AM Chia-Ping Tsai wrote:
> +1 (binding)
>
> On 2025/02/12 14:49:37 Kuan Po Tseng wrote:
> > Hello,
> > I'd like to initiate a vote on KIP-1124, which aims to provide a clear
> > upgrade path for Kafka clients. This propos
Build Test Pipeline (JVM):
https://github.com/apache/kafka/actions/runs/13677582256
Docker Build Test Pipeline (Native):
https://github.com/apache/kafka/actions/runs/13677587424
/**
Thanks,
David Jacot
David Jacot wrote:
>
> Hello Kafka users, developers and client-developers,
>
> This is the second candidate for release of Apache Kafka 4.0.0.
>
> - This is the first release without Apache Zookeeper
> - The Next Generation of the Consumer Rebalance Protocol is Generally
//kafka.apache.org/quickstart still has sections to
> start/stop Zookeeper (same for Streams Quickstart).
> - Also the quickstart has invalid commands to format log directories and
> start the server (pointing to wrong server.properties location under
> /kraft). It's OK on th
t;
> KT01. Will clients calculate the topic hash on the client? Based on the
> current state of the KIP and PR, I would have thought "no", but I ask based
> on the discussion around the possible use of Guava on client.
>
> Thanks,
> Kirk
>
> On Mon, Jan 6,
gain and
> > > report the results here.
> > >
> > > > * kafkatest.tests.tools.replica_verification_test - It has been
> failing
> > > for
> > > a while. The tool is deprecated and not really used so I don't consider
> >
Hi all,
FYI - I just updated the documentation. The "1.7 Compatibility"
section is empty. Looking into it.
Best,
David
On Wed, Mar 12, 2025 at 1:51 PM David Jacot wrote:
>
> Hi,
>
> Thanks for pointing that out. I will update the documentation by the end of
> the day.
>> > > - built from the source artifacts and ran into the same issue
> > Lianet
> > > >> > > described. After that I built from source using the 4.0.0-rc3
> tag.
> > > >> > > - ran unit and integration tests
> > > >> > &
u please take a look at
> https://issues.apache.org/jira/browse/KAFKA-18627? This JIRA ticket
> introduces a new system environment variable and (possibly) deprecates the
> old one. Is it appropriate to include this change in 4.0?
> >
> > Thanks,
> > Chia-Ping
> >
Hello Kafka users, developers and client-developers,
This is the first candidate for release of Apache Kafka 4.0.0. We
still have some remaining blockers but we figured that getting a first
release candidate will help the community to test this major release.
- This is the first release without A
ormation about how it failed?
>
> Many thanks
>
> Best Regards,
> TengYao
>
> David Jacot 於 2025年2月22日 週六 下午6:17寫道：
>
> > Hello Kafka users, developers and client-developers,
> >
> > This is the first candidate for release of Apache Kafka 4.0.0. We
>
Hi Calvin,
Thanks for the KIP. It is indeed a nice addition to simplify operations. I
have a few comments:
DJ01: The motivation is a bit weak in my opinion. It would be great if we
could clearly state what you want to do and the rationale behind it. For
instance, this sentence "If the transaction
Hi Pawel,
Thanks for the KIP and sorry for my late comment but I somehow missed the
discussion thread about it.
I have one minor ask: Could we change `generationId` to `memberEpoch` in
order to align with the KIP-848's new terminology? This is a good
opportunity for doing it.
Best,
David
On Fri
[
https://issues.apache.org/jira/browse/KAFKA-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot updated KAFKA-2072:
---
Status: In Progress (was: Patch Available)
> Add StopReplica request/response
[
https://issues.apache.org/jira/browse/KAFKA-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot updated KAFKA-2072:
---
Status: Patch Available (was: In Progress)
> Add StopReplica request/response
[
https://issues.apache.org/jira/browse/KAFKA-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot reassigned KAFKA-3085:
--
Assignee: David Jacot
> BrokerChangeListener computes inconsistent live/dead broker l
[
https://issues.apache.org/jira/browse/KAFKA-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot updated KAFKA-3085:
---
Status: Patch Available (was: Open)
> BrokerChangeListener computes inconsistent live/dead bro
[
https://issues.apache.org/jira/browse/KAFKA-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093334#comment-15093334
]
David Jacot commented on KAFKA-3085:
[~junrao] No worries. I'll update it ac
[
https://issues.apache.org/jira/browse/KAFKA-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot updated KAFKA-3085:
---
Status: In Progress (was: Patch Available)
> BrokerChangeListener computes inconsistent live/d
[
https://issues.apache.org/jira/browse/KAFKA-3085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot updated KAFKA-3085:
---
Status: Patch Available (was: In Progress)
> BrokerChangeListener computes inconsistent live/d
[
https://issues.apache.org/jira/browse/KAFKA-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot reassigned KAFKA-2066:
--
Assignee: David Jacot
> Replace FetchRequest / FetchResponse with th
[
https://issues.apache.org/jira/browse/KAFKA-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095678#comment-15095678
]
David Jacot commented on KAFKA-2758:
[~guozhang] I'd like to dive int
[
https://issues.apache.org/jira/browse/KAFKA-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot updated KAFKA-3098:
---
Assignee: David Jacot
Status: Patch Available (was: Open)
> "partition.assignment.
[
https://issues.apache.org/jira/browse/KAFKA-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KAFKA-2066 started by David Jacot.
--
> Replace FetchRequest / FetchResponse with th
[
https://issues.apache.org/jira/browse/KAFKA-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15104883#comment-15104883
]
David Jacot commented on KAFKA-2066:
In the current implementation, FetchResp
[
https://issues.apache.org/jira/browse/KAFKA-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107051#comment-15107051
]
David Jacot commented on KAFKA-2066:
[~ijuma],
- Inheritance might not be the
501 - 600 of 1197 matches
Mail list logo
