On Tue, Apr 8, 2025, at 09:55, Justine Olshan wrote: > Hey PoAn, > > Just wanted to make a clarification. TV2 doesn't need to be downgraded if > the MV is lower than the bootstrap MV for the TV. > The bootstrap MV is only used when the cluster is created to get the > default feature versions. As long as the TV version is a production version > for the Kafka release, you can change MV to whatever you choose. It is > decoupled from the MV at this point. > > Thanks, > Justine >
Hi Justine, Thanks for the clarification. Yes, the "default versions" of features don't necessarily imply hard dependencies. But if there are hard dependencies (where a feature needs a certain MV), we will enforce that. best, Colin > On Tue, Apr 8, 2025 at 2:01 AM PoAn Yang <yangp...@gmail.com> wrote: > >> Hi Colin, >> >> Thanks for the KIP. It’s good to give users more flexibility to downgrade >> metadata.version. >> >> PY1: Each feature has bootstrapMetadataVersion. For example, TV_2 is >> IBP_4_0_IV2. >> Assume that a cluster uses TV_2 and metadata.version 4.0-IV2. If a user >> downgrades >> metadata.version to 3.9-IV0, will the controller check TransactionVersion >> and reject >> the request? >> >> PY2: After users downgrade metadata.version, can they also restart server >> with old binary >> version? If they can, we need to add related end-to-end ducktape test. >> >> Thanks, >> PoAn >> >> > On Apr 8, 2025, at 6:04 AM, Colin McCabe <cmcc...@apache.org> wrote: >> > >> > Hi all, >> > >> > I posted a new KIP about support metadata.version downgrades. Take a >> look here: >> > >> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1155%3A+Metadata+Version+Downgrades >> > >> > thanks, >> > Colin >> >>
