You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by Ismael Juma <me...@ismaeljuma.com> on 2023/11/21 20:06:29 UTC
[VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
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 deprecated protocol api
versions.
Link:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
Thanks,
Ismael
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by Ismael Juma <me...@ismaeljuma.com>.
Thanks Jun. I updated the KIP with this information and also linked to a
JIRA that captures the items required for 3.7.
Ismael
On Tue, Nov 21, 2023 at 2:53 PM Jun Rao <ju...@confluent.io.invalid> wrote:
> Hi, Ismael,
>
> Thanks for the KIP. +1
>
> It would be useful to clarify in the KIP that the new metric and new
> request log attribute will be added in Apache 3.7.
>
> Jun
>
> On Tue, Nov 21, 2023 at 1:57 PM Colin McCabe <cm...@apache.org> wrote:
>
> > Ah. I forget that KIP-724 not only deprecated, but proposed a removal in
> > 4.0. Great.
> >
> > +1 (binding) for KIP-896
> >
> > 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/display/KAFKA/KIP-724%3A+Drop+support+for+message+formats+v0+and+v1
> > >
> > > Ismael
> > >
> > > On Tue, Nov 21, 2023, 12:21 PM Colin McCabe <cm...@apache.org>
> wrote:
> > >
> > >> Hi Ismael,
> > >>
> > >> Can we state 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 12:06, Ismael Juma wrote:
> > >> > 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 deprecated protocol
> api
> > >> > versions.
> > >> >
> > >> > Link:
> > >> >
> > >>
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
> > >> >
> > >> > Thanks,
> > >> > Ismael
> > >>
> >
>
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by José Armando García Sancio <js...@confluent.io.INVALID>.
Thanks. LGTM. +1.
On Tue, Nov 21, 2023 at 2:54 PM Jun Rao <ju...@confluent.io.invalid> wrote:
>
> Hi, Ismael,
>
> Thanks for the KIP. +1
>
> It would be useful to clarify in the KIP that the new metric and new
> request log attribute will be added in Apache 3.7.
>
> Jun
>
> On Tue, Nov 21, 2023 at 1:57 PM Colin McCabe <cm...@apache.org> wrote:
>
> > Ah. I forget that KIP-724 not only deprecated, but proposed a removal in
> > 4.0. Great.
> >
> > +1 (binding) for KIP-896
> >
> > 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/display/KAFKA/KIP-724%3A+Drop+support+for+message+formats+v0+and+v1
> > >
> > > Ismael
> > >
> > > On Tue, Nov 21, 2023, 12:21 PM Colin McCabe <cm...@apache.org> wrote:
> > >
> > >> Hi Ismael,
> > >>
> > >> Can we state 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 12:06, Ismael Juma wrote:
> > >> > 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 deprecated protocol api
> > >> > versions.
> > >> >
> > >> > Link:
> > >> >
> > >>
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
> > >> >
> > >> > Thanks,
> > >> > Ismael
> > >>
> >
--
-José
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by Jun Rao <ju...@confluent.io.INVALID>.
Hi, Ismael,
Thanks for the KIP. +1
It would be useful to clarify in the KIP that the new metric and new
request log attribute will be added in Apache 3.7.
Jun
On Tue, Nov 21, 2023 at 1:57 PM Colin McCabe <cm...@apache.org> wrote:
> Ah. I forget that KIP-724 not only deprecated, but proposed a removal in
> 4.0. Great.
>
> +1 (binding) for KIP-896
>
> 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/display/KAFKA/KIP-724%3A+Drop+support+for+message+formats+v0+and+v1
> >
> > Ismael
> >
> > On Tue, Nov 21, 2023, 12:21 PM Colin McCabe <cm...@apache.org> wrote:
> >
> >> Hi Ismael,
> >>
> >> Can we state 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 12:06, Ismael Juma wrote:
> >> > 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 deprecated protocol api
> >> > versions.
> >> >
> >> > Link:
> >> >
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
> >> >
> >> > Thanks,
> >> > Ismael
> >>
>
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by Colin McCabe <cm...@apache.org>.
Ah. I forget that KIP-724 not only deprecated, but proposed a removal in 4.0. Great.
+1 (binding) for KIP-896
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/display/KAFKA/KIP-724%3A+Drop+support+for+message+formats+v0+and+v1
>
> Ismael
>
> On Tue, Nov 21, 2023, 12:21 PM Colin McCabe <cm...@apache.org> wrote:
>
>> Hi Ismael,
>>
>> Can we state 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 12:06, Ismael Juma wrote:
>> > 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 deprecated protocol api
>> > versions.
>> >
>> > Link:
>> >
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
>> >
>> > Thanks,
>> > Ismael
>>
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by Ismael Juma <me...@ismaeljuma.com>.
Hi Colin,
That change was proposed and approved via KIP-724:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-724%3A+Drop+support+for+message+formats+v0+and+v1
Ismael
On Tue, Nov 21, 2023, 12:21 PM Colin McCabe <cm...@apache.org> wrote:
> Hi Ismael,
>
> Can we state 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 12:06, Ismael Juma wrote:
> > 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 deprecated protocol api
> > versions.
> >
> > Link:
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
> >
> > Thanks,
> > Ismael
>
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by Colin McCabe <cm...@apache.org>.
Hi Ismael,
Can we state 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 12:06, Ismael Juma wrote:
> 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 deprecated protocol api
> versions.
>
> Link:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
>
> Thanks,
> Ismael
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by Ismael Juma <me...@ismaeljuma.com>.
Hi Jason,
Thanks for bringing this up. A couple of comments:
1. Yes, we should deprecate and remove the raw SASL protocol that preceded
KIP-43 - the popular clients have supported SaslHandshake for a very long
time.
2. Yes, kafka-python still uses SaslHandshake v0 and it doesn't support
SaslAuthenticate, so we can't require SaslAuthenticate yet (KIP-152).
I updated the KIP to:
1. Note the removal of the raw SASL protocol that preceded KIP-43.
2. Keep SaslHandshake v0 in Apache Kafka 4.0 since kafka-python still
relies on it (the KIP had incorrectly stated that kafka-python supports
SaslHandshake v1 since the definition exists, but it turns out that the
code never actually uses it).
Ismael
On Thu, Dec 7, 2023 at 3:37 PM Jason Gustafson <ja...@confluent.io.invalid>
wrote:
> Minor correction: only `SaslHandshake` was introduced in KIP-43.
> `SaslAuthenticate` came later in KIP-152.
>
> On Thu, Dec 7, 2023 at 3:18 PM Jason Gustafson <ja...@confluent.io> wrote:
>
> > Hey Ismael,
> >
> > I'm considering if we can do something in this KIP for the SASL baggage
> > we've accumulated. Prior to the existence of the `SaslHandshake` API, we
> > supported the raw SASL protocol. The main gap was that it did not support
> > negotiation of the SASL method. This was fixed in
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-43:+Kafka+SASL+enhancements
> > where we added the `SaslHandshake` and `SaslAuthenticate`. This has been
> > supported in the broker since 0.10.0 and, as far as I can tell, all major
> > clients mentioned in the KIP support the `SaslHandshake` API. However, we
> > still support fallback logic on the broker, effectively assuming GSSAPI
> if
> > the initial request is not a Kafka request. Can we require SASL
> negotiation
> > through `SaslHandshake` and drop support for this fallback logic?
> >
> > I also looked at `SaslAuthenticate`, which was added in
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-152+-+Improve+diagnostics+for+SASL+authentication+failures
> .
> > 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 not implement it.
> >
> > Thanks,
> > Jason
> >
> >
> >
> > On Fri, Nov 24, 2023 at 12:07 PM Ismael Juma <me...@ismaeljuma.com> wrote:
> >
> >> 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 <me...@ismaeljuma.com> wrote:
> >>
> >> > 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 deprecated protocol api
> >> > versions.
> >> >
> >> > Link:
> >> >
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
> >> >
> >> > Thanks,
> >> > Ismael
> >> >
> >>
> >
>
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by Jason Gustafson <ja...@confluent.io.INVALID>.
Minor correction: only `SaslHandshake` was introduced in KIP-43.
`SaslAuthenticate` came later in KIP-152.
On Thu, Dec 7, 2023 at 3:18 PM Jason Gustafson <ja...@confluent.io> wrote:
> Hey Ismael,
>
> I'm considering if we can do something in this KIP for the SASL baggage
> we've accumulated. Prior to the existence of the `SaslHandshake` API, we
> supported the raw SASL protocol. The main gap was that it did not support
> negotiation of the SASL method. This was fixed in
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-43:+Kafka+SASL+enhancements
> where we added the `SaslHandshake` and `SaslAuthenticate`. This has been
> supported in the broker since 0.10.0 and, as far as I can tell, all major
> clients mentioned in the KIP support the `SaslHandshake` API. However, we
> still support fallback logic on the broker, effectively assuming GSSAPI if
> the initial request is not a Kafka request. Can we require SASL negotiation
> through `SaslHandshake` and drop support for this fallback logic?
>
> I also looked at `SaslAuthenticate`, which was added in
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-152+-+Improve+diagnostics+for+SASL+authentication+failures.
> 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 not implement it.
>
> Thanks,
> Jason
>
>
>
> On Fri, Nov 24, 2023 at 12:07 PM Ismael Juma <me...@ismaeljuma.com> wrote:
>
>> 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 <me...@ismaeljuma.com> wrote:
>>
>> > 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 deprecated protocol api
>> > versions.
>> >
>> > Link:
>> >
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
>> >
>> > Thanks,
>> > Ismael
>> >
>>
>
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by Jason Gustafson <ja...@confluent.io.INVALID>.
Hey Ismael,
I'm considering if we can do something in this KIP for the SASL baggage
we've accumulated. Prior to the existence of the `SaslHandshake` API, we
supported the raw SASL protocol. The main gap was that it did not support
negotiation of the SASL method. This was fixed in
https://cwiki.apache.org/confluence/display/KAFKA/KIP-43:+Kafka+SASL+enhancements
where we added the `SaslHandshake` and `SaslAuthenticate`. This has been
supported in the broker since 0.10.0 and, as far as I can tell, all major
clients mentioned in the KIP support the `SaslHandshake` API. However, we
still support fallback logic on the broker, effectively assuming GSSAPI if
the initial request is not a Kafka request. Can we require SASL negotiation
through `SaslHandshake` and drop support for this fallback logic?
I also looked at `SaslAuthenticate`, which was added in
https://cwiki.apache.org/confluence/display/KAFKA/KIP-152+-+Improve+diagnostics+for+SASL+authentication+failures.
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 not implement it.
Thanks,
Jason
On Fri, Nov 24, 2023 at 12:07 PM Ismael Juma <me...@ismaeljuma.com> wrote:
> 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 <me...@ismaeljuma.com> wrote:
>
> > 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 deprecated protocol api
> > versions.
> >
> > Link:
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
> >
> > Thanks,
> > Ismael
> >
>
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by Ismael Juma <me...@ismaeljuma.com>.
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 <me...@ismaeljuma.com> wrote:
> 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 deprecated protocol api
> versions.
>
> Link:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
>
> Thanks,
> Ismael
>
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by Ismael Juma <me...@ismaeljuma.com>.
Hi all,
As part of making these changes and testing the clients mentioned in the
KIP, we identified a number of adjustments required to satisfy the premise
that released versions of the clients mentioned in the KIP would work with
Apache Kafka 4.0:
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=235838251&selectedPageVersions=23&selectedPageVersions=18
So far so good, nothing too controversial.
And that leads us to the remaining piece to achieve the stated goal, we
need to workaround a bug in librdkafka where produce v0 needs to be in the
api versions response for compressed produce to work with lz4, gzip and
snappy[1]. Unfortunately, supporting produce v0 would imply supporting the
older record formats (v0 & v1), which would imply reintroducing significant
tech debt. I would rather not do that.
A better alternative, in my opinion, is to advertise support for
produce v0-v2, but return an UnsupportedVersion error if this is attempted.
Since clients pick the highest supported version by both client and broker
during version negotiation, this solves the problem with minimal tech debt
(even though it's not ideal that the protocol definition becomes
inconsistent with the actual protocol support). This workaround would be
removed in Apache Kafka 5.0.
If there are no strong concerns or better alternatives suggested, I will go
ahead with this approach as it's pretty straightforward:
https://github.com/apache/kafka/pull/18727
Ismael
[1] https://issues.apache.org/jira/browse/KAFKA-18659
On Sun, Dec 17, 2023 at 7:40 AM Ismael Juma <me...@ismaeljuma.com> wrote:
> Hi all,
>
> It turns out that kafka-python's protocol api versions support is worse
> than originally described - newer versions were defined but not actually
> supported in a few cases. I have updated the KIP to address this:
>
>
> https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=235838251&selectedPageVersions=18&selectedPageVersions=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 <me...@ismaeljuma.com> wrote:
>
>> 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 deprecated protocol api
>> versions.
>>
>> Link:
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
>>
>> Thanks,
>> Ismael
>>
>
Re: [VOTE] KIP-896: Remove old client protocol API versions in Kafka 4.0
Posted by Ismael Juma <me...@ismaeljuma.com>.
Hi all,
It turns out that kafka-python's protocol api versions support is worse
than originally described - newer versions were defined but not actually
supported in a few cases. I have updated the KIP to address this:
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=235838251&selectedPageVersions=18&selectedPageVersions=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 <me...@ismaeljuma.com> wrote:
> 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 deprecated protocol api
> versions.
>
> Link:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0
>
> Thanks,
> Ismael
>