Hi Colin, I agree that we try hard to avoid breaking compatibility. I am not questioning this at all. I also agree with your concern.
My point was about requiring users to opt-in for a feature vs having it enabled by default during the EA and the Preview phases. With KIP-1022, the only way to use a non-default version of a feature is to set the unstable config. I think that it would be nice to have the default feature version, new stable version(s) that users could opt-in to enable during EA/Preview, and the development one(s) gated by the unstable flag. This is perhaps more a discussion for KIP-1022. Best, David On Fri, Jun 28, 2024 at 7:50 AM Chia-Ping Tsai <chia7...@gmail.com> wrote: > On Wed, Jun 26, 2024, at 13:16, Jun Rao wrote: > > > > Hi, Colin, > > > > > > Thanks for the reply. > > > > > > 1. > > > https://kafka.apache.org/protocol.html#The_Messages_ConsumerGroupDescribe > > > lists ConsumerGroupDescribeRequest, whose latest version is unstable. > > > > > > > Hi Jun, > > > > I think that is a bug. > > > > I file a jira for this (https://issues.apache.org/jira/browse/KAFKA-17051) >
