showuon commented on PR #20137: URL: https://github.com/apache/kafka/pull/20137#issuecomment-3072718895
> > Regarding the error, I am not sure that a 4.1 release should mention a 4.2 metadata testing version as maximum value, something which is "in the future" and after the 4.1 itself. > > In my mental model, if I am on 4.1, the metadata version cannot go beyond 4.1. > > Yes, ideally, we should use either the latest production or latest test as the max version depending on whether the config unstable.feature.versions.enable is false or not. We could do that on the server side and in the tool where the config already exists. The only thing is that the AdminClient doesn't have that config yet and also calls `fromVersionString`. [KAFKA-19509](https://issues.apache.org/jira/browse/KAFKA-19509) is created for this improvement. -- 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
