[
https://issues.apache.org/jira/browse/KAFKA-18422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914736#comment-17914736
]
Ismael Juma edited comment on KAFKA-18422 at 1/20/25 5:15 PM:
--------------------------------------------------------------
To be clear, we cannot change the client upgrade guarantees outside of a major
release. So, we should discuss whether we do it now or in 5.0.
My take is that it's a no brainer to do what the KIP is proposing: it's good
for everyone (less maintenance for us, reduced risk for users). Also, no code
changes are required for this KIP. So, I think we should consider making an
exception.
was (Author: ijuma):
To be clear, we cannot change the client upgrade guarantees outside of a major
release. So, we should discuss whether we do it now or in 5.0.
My take is that it's a no brainer to do what the KIP is proposing: it's good
for everyone (less maintenance for us, reduced risk for users). Also, no code
changes are required for this KIP. So, I think we should consider making it an
exception.
> add Kafka client upgrade path
> -----------------------------
>
> Key: KAFKA-18422
> URL: https://issues.apache.org/jira/browse/KAFKA-18422
> Project: Kafka
> Issue Type: Improvement
> Reporter: Chia-Ping Tsai
> Assignee: Kuan Po Tseng
> Priority: Blocker
> Labels: need-kip
> Fix For: 4.1.0
>
>
> https://github.com/apache/kafka/pull/18193#issuecomment-2572283545
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
