chia7712 commented on PR #18193:
URL: https://github.com/apache/kafka/pull/18193#issuecomment-2572283545

   > Again: I am not arguing client-broker upgrades, and yes, broker 4.0 
require KS 2.1. But we need to keep both compatibility dimensions independent. 
The notion of a "bridge" version is for client-broker and yes, also applies to 
KS. But if I am on an older broker, I can still use KS 2.0.
   
   I understand. We can include a scenario in the documentation that covers 
upgrading the client to test the 4.0 broker. My primary concern is to prevent 
user confusion when selecting the appropriate bridge version. @m1a2st, please 
consider noting this special case in issue #18091? "If you plan to upgrade your 
broker to version 4.0, you may need to carefully consider avoiding the use of 
version 2.0 as a bridge version for your clients. This is because version 2.0 
may include protocols that are no longer supported in broker version 4.0."
   
   ### conclusion
   
   1. protocol matrix -> 2.1 is base line
   2. (client and streams) upgrade path -> [0.11.x - 1.x] -> [2.0 - 3.9] -> 4.x
   
   ### follow-up
   1. add 2.0 to consumer e2e upgrade test (this PR)
   2. remove 0.11, 1.0 and 1.1 from streams e2e upgrade test ( this can be 
addressed in this PR too)
   3. (optional) file a KIP to document the upgrade path (perhaps @brandboat 
could assist) and involve a wider range of kafka users
   4. review issue #18091 to ensure we have comprehensive documentation for 
both the protocol and upgrade procedures. (Thank you, @m1a2st.
   
   @ijuma @mjsax @cadonna @brandboat @m1a2st  @ableegoldman WDYT? I believe 
this is a valuable discussion, as it allows for the establishment of an 
officially supported compatibility matrix. This matrix will be a valuable 
resource for users during upgrade.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to