ijuma commented on PR #17843: URL: https://github.com/apache/kafka/pull/17843#issuecomment-2495260446
@ableegoldman Note that we did announce this change publicly too: https://kafka.apache.org/blog#apache_kafka_370_release_announcement I agree that we could perhaps have done more on the client side to warn, but I focused on the broker side versus the client side because it seems highly unlikely that someone would use a Kafka 4.0 client against a Kafka 2.0 (or older) broker (Kafka 2.0 was released in 2018, no kafka vendor supports it at this point, there are a number of CVEs that apply to it, etc.). The reverse where someone is using an ancient client against a newer broker is much more likely. That's also what we observed while talking to customers and users, they tend to be worried about the latter because clients are embedded in a large number of applications and are harder/slower to upgrade while I'm not aware of any of them raising concerns about the former. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
