Hi Viktor, Thanks for the feedback. See inline.
I was gonna ask about whether you think it would be useful to automate > protocol deprecation but I see you'll have a separate KIP for that so I'll > just wait :). > With regards to the follow-up KIP, if you are interested in submitting that, please go ahead. My high level idea was something like the following: Starting with Apache Kafka 5.0, the broker only keeps the latest protocol API version from the first release in previous major version series or a minor release that is at least n years old, whichever is oldest. Reasonable values for `n` could be `3` or `4`. Let's assume `n` is 3 and we release Apache Kafka 5.0 4 years after Apache Kafka 4.0, then we'd keep the highest protocol API version for each protocol from Apache Kafka 4.0. However, if Apache Kafka 5.0 was released 2 years after Apache Kafka 4.0, then we'd pick the relevant 3.x release as the baseline instead. If you do decide to write the KIP, feel free to suggest what you think is best, of course. With that said, let's leave further discussions on this future KIP idea to the future KIP thread. :) I see that in multiple places clients have older than baseline > implementation. Would it make sense in your opinion to also document that > those protocols below the baseline will be deprecated in 4.0 and possibly > go away in next versions (with maybe the deprecation/removal automation) > I considered that, but I thought it would be handled more cleanly by the mechanical policy of the future KIP while this KIP focuses only on what happens in 4.0. Ismael On Wed, Jan 4, 2023 at 7:42 AM Viktor Somogyi-Vass <viktor.somo...@cloudera.com.invalid> wrote: > Hi Ismael, > > I think this is a good idea, it can also simplify the code quite a bit. > I was gonna ask about whether you think it would be useful to automate > protocol deprecation but I see you'll have a separate KIP for that so I'll > just wait :). > > I see that in multiple places clients have older than baseline > implementation. Would it make sense in your opinion to also document that > those protocols below the baseline will be deprecated in 4.0 and possibly > go away in next versions (with maybe the deprecation/removal automation)? > > Viktor > > On Tue, Jan 3, 2023 at 5:18 PM Ismael Juma <ism...@juma.me.uk> wrote: > > > Hi all, > > > > I would like to start a discussion regarding the removal of very old > client > > protocol API versions in Apache Kafka 4.0 to improve maintainability & > > supportability of Kafka. Please take a look at the proposal: > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-896%3A+Remove+old+client+protocol+API+versions+in+Kafka+4.0 > > > > Ismael > > >
