Thanks, Chia-Ping, for the comments. I’ve addressed comments chia00 and chia01 in the KIP!
Also, thanks to Sophie for reminding me that 2.4 introduced cooperative rebalancing. I’ve added a paragraph about Kafka Streams and provided an example. By the way, I’ve also updated the Test Plan. We can now remove LATEST_0_11, LATEST_1_0, LATEST_1_1, and LATEST_2_0 from streams_upgrade_test.py, as it’s no longer recommended to directly upgrade to the latest dev version (4.x). Thanks to Matthias and Bruno for bringing up the issue of how we handle backward compatibility across multiple major versions. I feel like this topic has come up many times, but we haven’t really reached a solid consensus yet. Personally, I agree with Matthias’s point about using major versions as the baseline for compatibility guarantees as this would be easier for both developers and users to understand. As for how many major versions we should support, I agree two major versions is probably enough. The last 3.0.0 release was on September 21, 2021, and it’s already been four years since then… This KIP wasn't initially intended to discuss this issue, but I’m happy to expand the scope and maybe address these points under the "Compatibility, Deprecation, and Migration Plan" section of the KIP. What do you think? Also, thanks to Bruno for mentioning the documentation at https://kafka.apache.org/coding-guide. If the community reaches a consensus, we should make sure to clearly state how many major versions of backward compatibility we support in the Backwards Compatibility section. On 2025/01/15 13:44:09 Kuan Po Tseng wrote: > Hi all, > > I'd like to initiate a discussion thread on *KIP-1124,* which proposes a > clear upgrade path for Kafka Client, including Kafka Streams. > You can find the details here: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1124%3A+Providing+a+clear+Kafka+Client+upgrade+path > I’d appreciate it if you could take a look and share your thoughts or > feedback. > > Best regards, > Kuan-Po Tseng >
