chia7712 commented on PR #18193:
URL: https://github.com/apache/kafka/pull/18193#issuecomment-2592880931
> I see this jira marked as a blocker for 4.0 and at the same time it says
that it needs a KIP. We have a dead lock here. Can we remove it as a blocker?
Could we consider this KIP as an exception? The primary changes introduced
by this KIP are the addition of related end-to-end tests and the update of
upgrade paths in the documentation. These changes primarily pertain to testing
and documentation, and do not directly impact production code. Given that we
have nearly reached a consensus on the associated PR, perhaps we could proceed
with direct voting for this KIP.
Alternatively, we could defer the KIP (along with the related upgrade/matrix
documentation) to the 4.1 release. The streams end-to-end tests already include
support for 2.0, suggesting that there are no immediate critical upgrade issues
at this time. If Kafka users inquire about client upgrade paths for 4.0, we can
direct them to this PR.
> The discussion was about testing the upgrades of the consumer with the
classic protocol, because currently Streams only works with the classic
protocol. However, the test is about upgrading from classic to consumer
protocol.
While `consumer_protocol_migration_test.py` currently lacks a dedicated test
for the classic protocol, the file provides numerous helpful utilities that
could facilitate the addition of such a test.
--
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
