Hi, Thanks for the KIP.
Reading the discussion, I think a lot of the confusion is due to the "unstable" naming. People are then trying to figure out when we think something is stable in the "this is battle-tested" sense. But this flag should not be about that. We can have an MV for a feature that is not yet production-ready (and we did that when KRaft itself was not production ready). I think this flag is about metadata versions that are basically unsupported - if you use it, you get to keep the pieces. They exist solely to make the lives of Apache Kafka developers easier. I would even suggest that the config we introduce be of the internal variety, ie it won't show in the generated documentation and there won't be any compatibility guarantee. Thoughts? Ismael On Fri, Jan 5, 2024 at 7:33 AM Proven Provenzano <pprovenz...@confluent.io.invalid> wrote: > Hey folks, > > I am starting a discussion thread for managing unstable metadata versions > in Apache Kafka. > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1014%3A+Managing+Unstable+Metadata+Versions+in+Apache+Kafka > > This KIP is actually already implemented in 3.7 with PR > https://github.com/apache/kafka/pull/14860. > I have created this KIP to explain the motivation and how managing Metadata > Versions is expected to work. > Comments are greatly appreciated as this process can always be improved. > > -- > --Proven >
