ableegoldman commented on PR #17843: URL: https://github.com/apache/kafka/pull/17843#issuecomment-2495859713
> We did officially deprecate EOSv1, and if people did still use it, we did log a warning about it getting removed. https://github.com/apache/kafka/blob/3.9/streams/src/main/java/org/apache/kafka/streams/StreamsConfig.java#L1469-L1473 -- So there was more then enough time for people to adopt. Don't think this was rapid at all. Right -- like I said, I didn't have a problem with the eosv1 removal and didn't feel it was sudden/rapid at all. Partly also because of exactly this, ie that we took care to give users a clear warning ahead of time. I guess that's my main point in all of this: going forward we should think about how to properly warn users ahead of time @ijuma I've definitely spoken with users who ran upgraded clients against older brokers, so they do exist, though statistically you may be right that the reverse is more common. And obviously this only applies to on-prem installations, which are certainly becoming less and less frequent but shouldn't be disregarded altogether. (And yes, I've even. spoken with someone who complained about their Kafka cluster being stuck on 0.11 due to apprehension around upgrades -- but to be fair, this was like two years ago or more, so I really really hope they managed to upgrade since then) -- 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]
