+1 to add it as part of upgrade page. Users refer to the upgrade page
to access any information related to upgrades for a release as it is
expected to contain all the relevant text and references regarding the
upgrade in that particular release.
David,
On Thu, 5 Oct 2023 at 17:22, Ismael Juma
The upgrade page is the right place to add it, in my opinion.
Ismael
On Thu, Oct 5, 2023 at 5:02 PM David Arthur
wrote:
> Hey folks, we found a significant ZK migration bug today
> https://issues.apache.org/jira/browse/KAFKA-15552. Since the release is
> already voted in, the fix will wait for
Hey folks, we found a significant ZK migration bug today
https://issues.apache.org/jira/browse/KAFKA-15552. Since the release is
already voted in, the fix will wait for 3.6.1. In the meantime, do we have
a way to indicate known significant issues in the release notes? Maybe just
a note in the
Thanks Satish!
Ismael
On Thu, Sep 28, 2023 at 6:39 AM Satish Duggana
wrote:
> We do not have any pending release blockers for now. RC1 release
> blocker KAFKA-15498[1] is merged to 3.6.
> I will create RC2 by 29th Sep 12:00 pm PT and start a new RC thread.
>
> 1.
We do not have any pending release blockers for now. RC1 release
blocker KAFKA-15498[1] is merged to 3.6.
I will create RC2 by 29th Sep 12:00 pm PT and start a new RC thread.
1. https://github.com/apache/kafka/pull/14434
Thanks,
Satish.
On Wed, 27 Sept 2023 at 13:36, Divij Vaidya wrote:
>
>
Ismael,
Thank you for checking.
Multiple other folks have validated after I left the comment here that
it doesn't impact log truncation and hence won't lead to data loss. I
agree that it's not a blocker.
(ref: https://github.com/apache/kafka/pull/14457)
--
Divij Vaidya
On Wed, Sep 27, 2023 at
Doesn't look like a blocker to me.
Ismael
On Wed, Sep 27, 2023 at 2:36 AM Divij Vaidya
wrote:
> Hey team
>
> I need help in determining whether
> https://github.com/apache/kafka/pull/14457 is a release blocker bug or
> not. If someone is familiar with replication protocol (on the log
>
Hey team
I need help in determining whether
https://github.com/apache/kafka/pull/14457 is a release blocker bug or
not. If someone is familiar with replication protocol (on the log
diverange and reconciliation process), please add your comments on the
PR.
--
Divij Vaidya
On Wed, Sep 27, 2023 at
A community member reported another bug in TS feature in 3.6 -
https://issues.apache.org/jira/browse/KAFKA-15511
I don't consider it as a blocker for release because the bug occurs in
rare situations when the index on disk or in a remote store is
corrupted and fails a sanity check.
Sharing it
Found a bug while testing TS feature in 3.6 -
https://issues.apache.org/jira/browse/KAFKA-15481
I don't consider it as a blocker for release since it's a concurrency
bug that should occur rarely for a feature which is early access.
Sharing it here as FYI in case someone else thinks differently.
Thanks Divij for raising a PR for doc formatting issue.
On Thu, 21 Sep, 2023, 2:22 PM Divij Vaidya, wrote:
> Hey Satish
>
> I filed a PR to fix the website formatting bug in 3.6 documentation -
> https://github.com/apache/kafka/pull/14419
> Please take a look when you get a chance.
>
> --
>
Hey Satish
I filed a PR to fix the website formatting bug in 3.6 documentation -
https://github.com/apache/kafka/pull/14419
Please take a look when you get a chance.
--
Divij Vaidya
On Tue, Sep 19, 2023 at 5:36 PM Chris Egerton wrote:
>
> Hi Satish,
>
> I think this qualifies as a blocker.
Hi Satish,
I think this qualifies as a blocker. This API has been around for years now
and, while we don't document it as not exposing duplicates*, it has come
with that implicit contract since its inception. More importantly, it has
also never exposed plugins that cannot be used on the worker.
Hi Greg,
Is this API documented that it does not return duplicate entries?
Can we also get an opinion from PMC/Committers who have KafkaConnect
expertise on whether this issue is a release blocker?
If we agree that it is not a release blocker then we can have a
release note clarifying this
Hey Satish,
After investigating further, I believe that this is a regression, but
mostly a cosmetic one.
I don't think there is significant risk of breaking clients with this
change, but it would be confusing for users, so I'd still like to get
the fix into the next RC.
I've opened a PR here:
Hi Satish,
While validating 3.6.0-rc0, I noticed this regression as compared to
3.5.1: https://issues.apache.org/jira/browse/KAFKA-15473
Impact: The `connector-plugins` endpoint lists duplicates which may
cause confusion for users, or poor behavior in clients.
Using the other REST API endpoints
Thanks Justine for the update. I saw in the morning that these changes
are pushed to trunk and 3.6.
~Satish.
On Thu, 14 Sept 2023 at 21:54, Justine Olshan
wrote:
>
> Hi Satish,
> We were able to merge
> https://issues.apache.org/jira/browse/KAFKA-15459 yesterday
> and pick to 3.6.
>
> Hopefully
Hi Satish,
We were able to merge
https://issues.apache.org/jira/browse/KAFKA-15459 yesterday
and pick to 3.6.
Hopefully nothing more from me on this release.
Thanks,
Justine
On Wed, Sep 13, 2023 at 9:51 PM Satish Duggana
wrote:
> Thanks Luke for the update.
>
> ~Satish.
>
> On Thu, 14 Sept
Thanks Luke for the update.
~Satish.
On Thu, 14 Sept 2023 at 07:29, Luke Chen wrote:
>
> Hi Satish,
>
> Since this PR:
> https://github.com/apache/kafka/pull/14366 only changes the doc, I've
> backported to 3.6 branch. FYI.
>
> Thanks.
> Luke
>
> On Thu, Sep 14, 2023 at 12:15 AM Justine Olshan
Hi Satish,
Since this PR:
https://github.com/apache/kafka/pull/14366 only changes the doc, I've
backported to 3.6 branch. FYI.
Thanks.
Luke
On Thu, Sep 14, 2023 at 12:15 AM Justine Olshan
wrote:
> Hey Satish -- yes, you are correct. KAFKA-15459 only affects 3.6.
> PR should be finalized soon.
Hey Satish -- yes, you are correct. KAFKA-15459 only affects 3.6.
PR should be finalized soon.
Thanks,
Justine
On Wed, Sep 13, 2023 at 1:41 AM Federico Valeri
wrote:
> Hi Satish, this is a small documentation fix about ZK to KRaft
> migration, that we would like to backport to 3.5 and 3.6
Hi Satish, this is a small documentation fix about ZK to KRaft
migration, that we would like to backport to 3.5 and 3.6 branches. Are
you ok with that?
https://github.com/apache/kafka/pull/14366
On Wed, Sep 13, 2023 at 3:13 AM Satish Duggana wrote:
>
> Thanks David for the quick resolution.
>
>
Thanks David for the quick resolution.
~Satish.
On Tue, 12 Sept 2023 at 22:51, David Arthur
wrote:
>
> Satish,
>
> KAFKA-15450 is merged to 3.6 (as well as trunk, 3.5, and 3.4)
>
> Thanks!
> David
>
> On Tue, Sep 12, 2023 at 11:44 AM Ismael Juma wrote:
>
> > Justine,
> >
> > Probably best to
Hi Justine,
Thanks for the update. From JIRA[1] it looks like it affects only
3.6.0 but not for the earlier releases. Is that right?
https://issues.apache.org/jira/browse/KAFKA-15459
~Satish.
On Wed, 13 Sept 2023 at 00:42, Justine Olshan
wrote:
>
> It's me again.
> While reviewing the
It's me again.
While reviewing the previous PR, it was discovered we had a potential
breaking return code for non-java clients.
This unfortunately seems like a blocker.
https://issues.apache.org/jira/browse/KAFKA-15459
I will be able to get a PR open today.
Apologies for all the noise in the
Satish,
KAFKA-15450 is merged to 3.6 (as well as trunk, 3.5, and 3.4)
Thanks!
David
On Tue, Sep 12, 2023 at 11:44 AM Ismael Juma wrote:
> Justine,
>
> Probably best to have the conversation in the JIRA ticket vs the release
> thread. Generally, we want to only include low risk bug fixes that
Justine,
Probably best to have the conversation in the JIRA ticket vs the release
thread. Generally, we want to only include low risk bug fixes that are
fully compatible in patch releases.
Ismael
On Tue, Sep 12, 2023 at 7:16 AM Justine Olshan
wrote:
> Thanks Satish. I understand.
> Just
Thanks Satish. I understand.
Just curious, is this something that could be added to 3.6.1? It would be
nice to say that hanging transactions are fully covered in a 3.6 release.
I'm not as familiar with the rules around minor releases, but adding it
there would give more time to ensure stability.
Hi Justine,
We can skip this change into 3.6 now as it is not a blocker or
regression and it involves changes to the API implementation. Let us
plan to add the gap in the release notes as you mentioned.
Thanks,
Satish.
On Tue, 12 Sept 2023 at 04:44, Justine Olshan
wrote:
>
> Hey Satish,
>
> We
Hi David,
It looks like the PR is already accepted with a minor config change
validation, and you mentioned that the failed tests are not related.
Please merge it to 3.6 by today.
Thanks,
Satish.
On Tue, 12 Sept 2023 at 00:59, David Arthur
wrote:
>
> Another (small) ZK migration issue was
Hey Satish,
We just discovered a gap in KIP-890 part 1. We currently don't verify on
txn offset commits, so it is still possible to have hanging transactions on
the consumer offsets partitions.
I've opened a jira to wire the verification in that request.
Another (small) ZK migration issue was identified. This one isn't a
regression (it has existed since 3.4), but I think it's reasonable to
include. It's a small configuration check that could potentially save end
users from some headaches down the line.
Hi Satish,
That sounds great. I think we should aim to only allow blockers
(regressions, impactful security issues, etc.) on the 3.6 branch until
3.6.0 is out.
Ismael
On Sat, Sep 9, 2023, 12:20 AM Satish Duggana
wrote:
> Hi Ismael,
> It looks like we will publish RC0 by 14th Sep.
>
> Thanks,
Hi Ismael,
It looks like we will publish RC0 by 14th Sep.
Thanks,
Satish.
On Fri, 8 Sept 2023 at 19:23, Ismael Juma wrote:
>
> Hi Satish,
>
> Do you have a sense of when we'll publish RC0?
>
> Thanks,
> Ismael
>
> On Fri, Sep 8, 2023 at 6:27 AM David Arthur
> wrote:
>
> > Quick update on my
Thanks David for the fixes and the update.
~Satish.
On Fri, 8 Sept 2023 at 18:57, David Arthur
wrote:
>
> Quick update on my two blockers: KAFKA-15435 is merged to trunk and
> cherry-picked to 3.6. I have a PR open for KAFKA-15441 and will hopefully
> get it merged today.
>
> -David
>
> On Fri,
Hi Ivan,
This is a reasonable request. I think it is good to address now
because of the confusion the API is creating. Abhijeet agreed to
volunteer to raise PR today to address KAFKA-14993.
Thanks,
Satish.
On Fri, 8 Sept 2023 at 14:54, Ivan Yurchenko wrote:
>
> Hi Satish and all,
>
> I wonder
Hi Satish,
Do you have a sense of when we'll publish RC0?
Thanks,
Ismael
On Fri, Sep 8, 2023 at 6:27 AM David Arthur
wrote:
> Quick update on my two blockers: KAFKA-15435 is merged to trunk and
> cherry-picked to 3.6. I have a PR open for KAFKA-15441 and will hopefully
> get it merged today.
Quick update on my two blockers: KAFKA-15435 is merged to trunk and
cherry-picked to 3.6. I have a PR open for KAFKA-15441 and will hopefully
get it merged today.
-David
On Fri, Sep 8, 2023 at 5:26 AM Ivan Yurchenko wrote:
> Hi Satish and all,
>
> I wonder if
Hi Satish and all,
I wonder if https://issues.apache.org/jira/browse/KAFKA-14993 should be
included in the 3.6 release plan. I'm thinking that when implemented, it would
be a small, but still a change in the RSM contract: throw an exception instead
of returning an empty InputStream. Maybe it
Hi Jose,
Thanks for looking into this issue and resolving it with a quick fix.
~Satish.
On Thu, 7 Sept 2023 at 21:40, José Armando García Sancio
wrote:
>
> Hi Satish,
>
> On Wed, Sep 6, 2023 at 4:58 PM Satish Duggana
> wrote:
> >
> > Hi Greg,
> > It seems
Hi Satish,
On Wed, Sep 6, 2023 at 4:58 PM Satish Duggana wrote:
>
> Hi Greg,
> It seems https://issues.apache.org/jira/browse/KAFKA-14273 has been
> there in 3.5.x too.
I also agree that it should be a blocker for 3.6.0. It should have
been a blocker for those previous releases. I didn't fix it
Hi Greg,
It seems https://issues.apache.org/jira/browse/KAFKA-14273 has been
there in 3.5.x too.
David/Colin,
Do you think it is a blocker for 3.6.0?
Thanks,
Satish.
On Wed, 6 Sept 2023 at 21:34, Greg Harris wrote:
>
> Hey all,
>
> A user just experienced this problem that has already been
Hi David,
Thanks for bringing the KAFKA-15441 to this discussion thread, it
seems to be a blocker and updated the JIRA. What is the plan to
address that?
https://issues.apache.org/jira/browse/KAFKA-15411, which is about
KRaft and delegation token related test failures. It seems to be a
test env
Hey all,
A user just experienced this problem that has already been reported
for several versions and has an open PR:
https://issues.apache.org/jira/browse/KAFKA-14273
https://github.com/apache/kafka/pull/12763
Impact: In KRaft mode on Windows, Kafka crashes on startup with an IOException.
Does
Thanks, Satish! Here's another blocker
https://issues.apache.org/jira/browse/KAFKA-15441 :)
For the 3.6 release notes and announcement, I'd like to include a special
note about ZK to KRaft migrations being GA (Generally Available). We have
finished closing all the gaps from the earlier releases
Hi David,
Thanks for bringing this issue to this thread.
I marked https://issues.apache.org/jira/browse/KAFKA-15435 as a blocker.
Thanks,
Satish.
On Tue, 5 Sept 2023 at 21:29, David Arthur wrote:
>
> Hi Satish. Thanks for running the release!
>
> I'd like to raise this as a blocker for 3.6
>
Hi Satish. Thanks for running the release!
I'd like to raise this as a blocker for 3.6
https://issues.apache.org/jira/browse/KAFKA-15435.
It's a very quick fix, so I should be able to post a PR soon.
Thanks!
David
On Mon, Sep 4, 2023 at 11:44 PM Justine Olshan
wrote:
> Thanks Satish. This is
Thanks Satish. This is done
Justine
On Mon, Sep 4, 2023 at 5:16 PM Satish Duggana
wrote:
> Hey Justine,
> I went through KAFKA-15424 and the PR[1]. It seems there are no
> dependent changes missing in 3.6 branch. They seem to be low risk as
> you mentioned. Please merge it to the 3.6 branch
Hey Justine,
I went through KAFKA-15424 and the PR[1]. It seems there are no
dependent changes missing in 3.6 branch. They seem to be low risk as
you mentioned. Please merge it to the 3.6 branch as well.
1. https://github.com/apache/kafka/pull/14324.
Thanks,
Satish.
On Tue, 5 Sept 2023 at
Sorry I meant to add the jira as well.
https://issues.apache.org/jira/browse/KAFKA-15424
Justine
On Mon, Sep 4, 2023 at 4:34 PM Justine Olshan wrote:
> Hey Satish,
>
> I was working on adding dynamic configuration for
> transaction verification. The PR is approved and ready to merge into
Hey Satish,
I was working on adding dynamic configuration for transaction verification.
The PR is approved and ready to merge into trunk.
I was thinking I could also add it to 3.6 since it is fairly low risk. What
do you think?
Justine
On Sat, Sep 2, 2023 at 6:21 PM Sophie Blee-Goldman
wrote:
Thanks Satish! The fix has been merged and cherrypicked to 3.6
On Sat, Sep 2, 2023 at 6:02 AM Satish Duggana
wrote:
> Hi Sophie,
> Please feel free to add that to 3.6 branch as you say this is a minor
> change and will not cause any regressions.
>
> Thanks,
> Satish.
>
> On Sat, 2 Sept 2023 at
Hi Sophie,
Please feel free to add that to 3.6 branch as you say this is a minor
change and will not cause any regressions.
Thanks,
Satish.
On Sat, 2 Sept 2023 at 08:44, Sophie Blee-Goldman
wrote:
>
> Hey Satish, someone reported a minor bug in the Streams application
> shutdown which was a
Hey Satish, someone reported a minor bug in the Streams application
shutdown which was a recent regression, though not strictly a new one: was
introduced in 3.4 I believe.
The fix seems to be super lightweight and low-risk so I was hoping to slip
it into 3.6 if that's ok with you? They plan to
Thanks Chris for bringing this issue here and filing the new JIRA for
3.6.0[1]. It seems to be a blocker for 3.6.0.
Please help review https://github.com/apache/kafka/pull/14314 as Chris
requested.
1. https://issues.apache.org/jira/browse/KAFKA-15425
~Satish.
On Fri, 1 Sept 2023 at 03:59,
Hi all,
Quick update: I've filed a separate ticket,
https://issues.apache.org/jira/browse/KAFKA-15425, to track the behavior
change in Admin::listOffsets. For the full history of the ticket, it's
worth reading the comment thread on the old ticket at
Hi Satish,
Wanted to let you know that KAFKA-12879 (
https://issues.apache.org/jira/browse/KAFKA-12879), a breaking change in
Admin::listOffsets, has been reintroduced into the code base. Since we
haven't yet published a release with this change (at least, not the more
recent instance of it), I
Hi,
Please plan to continue merging pull requests associated with any
outstanding minor features and stabilization changes to 3.6 branch
before September 3rd. Kindly update the KIP's implementation status in
the 3.6.0 release notes.
Thanks,
Satish.
On Fri, 25 Aug 2023 at 21:37, Justine Olshan
Hey Satish,
Everything should be in 3.6, and I will update the release plan wiki.
Thanks!
On Fri, Aug 25, 2023 at 4:08 AM Satish Duggana
wrote:
> Hi Justine,
> Adding KIP-890 part-1 to 3.6.0 seems reasonable to me. This part looks
> to be addressing a critical issue of consumers getting stuck.
Hi Justine,
Adding KIP-890 part-1 to 3.6.0 seems reasonable to me. This part looks
to be addressing a critical issue of consumers getting stuck. Please
update the release plan wiki and merge all the required changes to 3.6
branch.
Thanks,
Satish.
On Thu, 24 Aug 2023 at 22:19, Justine Olshan
Hey Satish,
Does it make sense to include KIP-890 part 1? It prevents hanging
transactions for older clients. (An optimization and stronger EOS
guarantees will be included in part 2)
Thanks,
Justine
On Mon, Aug 21, 2023 at 3:29 AM Satish Duggana
wrote:
> Hi,
> 3.6 branch is created. Please
Hi,
3.6 branch is created. Please make sure any PRs targeted for 3.6.0
should be merged to 3.6 branch once those are merged to trunk.
Thanks,
Satish.
On Wed, 16 Aug 2023 at 15:58, Satish Duggana wrote:
>
> Hi,
> Please plan to merge PRs(including the major features) targeted for
> 3.6.0 by the
Hi,
Please plan to merge PRs(including the major features) targeted for
3.6.0 by the end of Aug 20th UTC. Starting from August 21st, any pull
requests intended for the 3.6.0 release must include the changes
merged into the 3.6 branch as mentioned in the release plan.
Thanks,
Satish.
On Fri, 4
Thanks for adding KIP-949, Satish!
On Fri, Aug 4, 2023 at 7:06 AM Satish Duggana
wrote:
> Hi,
> Myself and Divij discussed and added the wiki for Kafka TieredStorage
> Early Access Release[1]. If you have any comments or feedback, please
> feel free to share them.
>
> 1.
>
Hi,
Myself and Divij discussed and added the wiki for Kafka TieredStorage
Early Access Release[1]. If you have any comments or feedback, please
feel free to share them.
1.
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Tiered+Storage+Early+Access+Release+Notes
Thanks,
Satish.
On Fri,
Hi Chris,
Thanks for the update. This looks to be a minor change and is also
useful for backward compatibility. I added it to the release plan as
an exceptional case.
~Satish.
On Thu, 3 Aug 2023 at 21:34, Chris Egerton wrote:
>
> Hi Satish,
>
> Would it be possible to include KIP-949 (
>
Hi Satish,
Would it be possible to include KIP-949 (
https://cwiki.apache.org/confluence/display/KAFKA/KIP-949%3A+Add+flag+to+enable+the+usage+of+topic+separator+in+MM2+DefaultReplicationPolicy)
in the 3.6.0 release? It passed voting yesterday, and is a very small,
low-risk change that we'd like
Hi All,
Whoever has KIP entries in the 3.6.0 release plan. Please update it
with the latest status by tomorrow(end of the day 29th Jul UTC ).
Thanks
Satish.
On Fri, 28 Jul 2023 at 12:01, Satish Duggana wrote:
>
> Thanks Ismael and Divij for the suggestions.
>
> One way was to follow the earlier
Thanks Ismael and Divij for the suggestions.
One way was to follow the earlier guidelines that we set for any early
access release. It looks Ismael already mentioned the example of
KRaft.
KIP-405 mentions upgrade/downgrade and limitations sections. We can
clarify that in the release notes for
Those are great suggestions, thank you. We will continue this discussion
forward in a separate KIP for release plan for Tiered Storage.
On Thu 27. Jul 2023 at 21:46, Ismael Juma wrote:
> Hi Divij,
>
> I think the points you bring up for discussion are all good. My main
> feedback is that they
Hi Divij,
I think the points you bring up for discussion are all good. My main
feedback is that they should be discussed in the context of KIPs vs the
release template. That's why we have a backwards compatibility section for
every KIP, it's precisely to ensure we think carefully about some of
Thank you for the response, Ismael.
1. Specifically in context of 3.6, I wanted this compatibility
guarantee point to encourage a discussion on
Hi Divij,
Some of these are launch checklist items (not really goals) and some are
compatibility guarantees. More below.
On Thu, Jul 27, 2023, 12:10 PM Divij Vaidya wrote:
> Hey Satish
>
> Could we consider adding "launch goals" in the release plan. While
> some of these may be implicit, it
e waiting period.
>
> Cheers,
>
> From: dev@kafka.apache.org At: 07/26/23 12:17:10 UTC-4:00To:
> dev@kafka.apache.org
> Subject: Re: Apache Kafka 3.6.0 release
>
> Hi Hector/Yash,
> Are you planning to reach out to other committers to vote on the KIP
> and close t
Yes, still need one more binding vote to pass. I'll send a reminder if the vote
is still pending after the waiting period.
Cheers,
From: dev@kafka.apache.org At: 07/26/23 12:17:10 UTC-4:00To:
dev@kafka.apache.org
Subject: Re: Apache Kafka 3.6.0 release
Hi Hector/Yash,
Are you planning
Sorry, my bad (you can tell this is the first time one of my KIPs have made it
this far :))
From: dev@kafka.apache.org At: 07/26/23 10:38:21 UTC-4:00To:
dev@kafka.apache.org
Subject: Re: Apache Kafka 3.6.0 release
Hi Hector,
KIP-959 actually still requires 2 more binding votes to be accepted
> > Best,
> > >
> > > [1]
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-959%3A+Add+BooleanConverter+to+Kafka+Connect
> > >
> > > From: dev@kafka.apache.org At: 06/12/23 06:22:00 UTC-4:00To:
> > dev@kafka.apache.org
> > > Subject: Re: Apac
wiki.apache.org/confluence/display/KAFKA/KIP-959%3A+Add+BooleanConverter+to+Kafka+Connect
> >
> > From: dev@kafka.apache.org At: 06/12/23 06:22:00 UTC-4:00To:
> dev@kafka.apache.org
> > Subject: Re: Apache Kafka 3.6.0 release
> >
> > Hi,
> > I have created a
pache.org At: 06/12/23 06:22:00 UTC-4:00To:
> dev@kafka.apache.org
> Subject: Re: Apache Kafka 3.6.0 release
>
> Hi,
> I have created a release plan for Apache Kafka version 3.6.0 on the
> wiki. You can access the release plan and all related information by
> following this link:
&
/confluence/display/KAFKA/KIP-959%3A+Add+BooleanConverter+to+Kafka+Connect
From: dev@kafka.apache.org At: 06/12/23 06:22:00 UTC-4:00To:
dev@kafka.apache.org
Subject: Re: Apache Kafka 3.6.0 release
Hi,
I have created a release plan for Apache Kafka version 3.6.0 on the
wiki. You can access
Thanks for the update, Mayank Shekhar.
On Tue, 25 Jul 2023 at 15:48, Mayank Shekhar Narula
wrote:
>
> Hi Satish
>
> Heads up KIP-951 is under voting. This could be delayed by a day or two for
> the 3.6 KIP deadline.
>
> On Tue, Jul 25, 2023 at 4:19 AM Satish Duggana
> wrote:
>
> > Thanks Colin
Hi Satish
Heads up KIP-951 is under voting. This could be delayed by a day or two for
the 3.6 KIP deadline.
On Tue, Jul 25, 2023 at 4:19 AM Satish Duggana
wrote:
> Thanks Colin for the update on the mentioned KIPs.
>
> ~Satish.
>
> On Mon, 24 Jul 2023 at 23:09, Colin McCabe wrote:
> >
> > Hi
Thanks Colin for the update on the mentioned KIPs.
~Satish.
On Mon, 24 Jul 2023 at 23:09, Colin McCabe wrote:
>
> Hi Satish,
>
> I removed "KIP-866 ZooKeeper to KRaft Migration" from the list of pending
> KIPs, since that one was shipped in 3.4. I added "KIP-868 Metadata
> Transactions",
Hi Satish,
I removed "KIP-866 ZooKeeper to KRaft Migration" from the list of pending KIPs,
since that one was shipped in 3.4. I added "KIP-868 Metadata Transactions",
since we are planning on implementing this in 3.6. (The KIP was approved a
while ago, but not yet shipped.)
I also added
A gentle reminder on the KIP freeze date: 26th Jul. Please try to
close discussion/vote threads asap.
Thanks,
Satish.
On Sun, 23 Jul 2023 at 11:10, Satish Duggana wrote:
>
> Thanks Colov/Divij for adding the KIP-952. I do not think it is a
> blocker for 3.6.0. We can discuss the KIP in the
Thanks Colov/Divij for adding the KIP-952. I do not think it is a
blocker for 3.6.0. We can discuss the KIP in the respective thread.
~Satish.
On Sun, 23 Jul 2023 at 07:21, Satish Duggana wrote:
>
> Thanks ShunKang for the update. I added both the KIPs to the wiki.
> Please feel free to update
Thanks ShunKang for the update. I added both the KIPs to the wiki.
Please feel free to update the wiki with the latest.
~Satish.
On Sat, 22 Jul 2023 at 22:50, ShunKang Lin wrote:
>
> Hi Satish,
>
> Could we add "KIP-863: Reduce CompletedFetch#parseRecord() memory copy" [1]
> and "KIP-872: Add
Thanks Divij for adding the KIPs to the wiki.
On Sat, 22 Jul 2023 at 17:36, Divij Vaidya wrote:
>
> Hi Satish
>
> I have added the following accepted KIPs to the release plan. Please let me
> know if something requires a change.
>
> Accepted KIPs -
>
> 1.
>
Hi Satish,
Could we add "KIP-863: Reduce CompletedFetch#parseRecord() memory copy" [1]
and "KIP-872: Add Serializer#serializeToByteBuffer() to reduce memory
copying" [2] to the release plan?
Thanks!
[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=225152035
[2]
Hi Satish
I have added the following accepted KIPs to the release plan. Please let me
know if something requires a change.
Accepted KIPs -
1.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-852%3A+Optimize+calculation+of+size+for+log+in+remote+tier
2.
Thanks Hao for the update on KIP-925.
On Thu, 20 Jul 2023 at 23:05, Hao Li wrote:
>
> Hi Satish,
>
> KIP-925 was accepted and currently under implementation. I just added it to
> the release plan.
>
>
Hi Satish,
KIP-925 was accepted and currently under implementation. I just added it to
the release plan.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-925%3A+Rack+aware+task+assignment+in+Kafka+Streams
Thanks,
Hao
On Thu, Jul 20, 2023 at 6:18 AM Christo Lolov
wrote:
> Hello!
>
> A
Hello!
A couple of days ago I opened a new KIP for discussion - KIP-952 [1]. I
believe it might be a blocker for the release of 3.6.0, but I wanted to
bring it up here for a decision on its urgency with the current set of
people who are looking at Tiered Storage (Satish, Luke, Ivan, Divij) given
Hi Yash,
Thanks for the update. Added KIP-793 to the release plan. Please feel
free to update the release wiki with any other updates on the KIP.
~Satish.
On Fri, 7 Jul 2023 at 10:52, Yash Mayya wrote:
>
> Hi Satish,
>
> KIP-793 [1] just passed voting and we should be able to wrap up the
>
Hi Satish,
KIP-793 [1] just passed voting and we should be able to wrap up the
implementation in time for the 3.6.0 feature freeze. Could we add it to the
release plan?
[1] -
https://cwiki.apache.org/confluence/display/KAFKA/KIP-793%3A+Allow+sink+connectors+to+be+used+with+topic-mutating+SMTs
Hi Christo,
Please feel free to add the KIP to the release plan wiki with the
implementation status.
Thanks,
Satish.
On Fri, 30 Jun 2023 at 21:59, Christo Lolov wrote:
>
> Hello!
>
> I will add KIP-902 to the release plan. I would appreciate a few more
> reviews on the pull request
Hello!
I will add KIP-902 to the release plan. I would appreciate a few more
reviews on the pull request (https://github.com/apache/kafka/pull/13260)
for that KIP as the longer we have it in trunk with tests running against
it the more confidence we will have before the release.
Best,
Christo
Thanks Satish!
On Sat, Jun 24, 2023 at 7:34 AM Satish Duggana
wrote:
> Thanks Chris for the update. I added KIP-875 to the 3.6.0 release plan
> wiki. Please feel free to update it.
>
> ~Satish.
>
> On Fri, 23 Jun 2023 at 23:10, Chris Egerton
> wrote:
> >
> > Hi Satish,
> >
> > Could we add
Thanks Chris for the update. I added KIP-875 to the 3.6.0 release plan
wiki. Please feel free to update it.
~Satish.
On Fri, 23 Jun 2023 at 23:10, Chris Egerton wrote:
>
> Hi Satish,
>
> Could we add KIP-875 [1] to the release plan? It was partially released in
> 3.5.0 and mentioned in the
Hi Satish,
Could we add KIP-875 [1] to the release plan? It was partially released in
3.5.0 and mentioned in the release plan [2], and since the rest (APIs to
reset and alter offsets for connectors) has now been merged to trunk, we
can let people know that the remainder should be available in the
1 - 100 of 112 matches
Mail list logo
