brandboat commented on PR #18193: URL: https://github.com/apache/kafka/pull/18193#issuecomment-2562793563
> @chia7712 Kafka Streams is different - it has to handle its own state during upgrades (kind of like the broker). The same is not true for regular clients. Maintaining tests like this one is pretty painful. Things will eventually break in odd ways (since the 0.11 code is so old). Also, it's too risky to go from 0.11 to 4.x+ in one go given multiple cycles of deprecations, removals, etc. (including non intersecting supported Java versions). Sorry to interrupt the discussion and thanks for the insightful comment, I 100% agree we don't encourage user to do major bumps like 0.11 to 4.x. I have a dumb question here. If we can't guarantee Kafka Consumer can successfully upgrade from 0.11 to 4.x, how can Kafka Streams guarantee that? Especially this kind of upgrade is still valid until Kafka Streams 5.0.0 comes out? -- 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
