[
https://issues.apache.org/jira/browse/KAFKA-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107113#comment-18107113
]
Harsh Vasava edited comment on KAFKA-20971 at 8/23/26 1:43 PM:
---------------------------------------------------------------
I started implementing the requested cross-version system test.
The positive 4.2.1/4.3.1 client cases fail before connecting to the broker with:
*Streams rebalance protocol does not support static membership.*
*Please set group.protocol=classic or remove group.instance.id from the
configuration.*
This is client-side validation in the released 4.2/4.3 Streams clients.
Therefore a 4.4+ broker cannot enable static membership for those clients.
Could you confirm the intended positive matrix? Should it use a
post-KAFKA-20169 Streams client version, or should the old-client case verify
normal streams-protocol compatibility without static membership?
was (Author: JIRAUSER314405):
I started implementing the requested cross-version system test.
The positive 4.2.1/4.3.1 client cases fail before connecting to the broker with:
*Streams rebalance protocol does not support static membership.*
*Please set group.protocol=classic or remove group.instance.id from the
configuration.*
This is client-side validation in the released 4.2/4.3 Streams clients.
Therefore a 4.4+ broker cannot enable static membership for those clients.
Could you confirm the intended positive matrix? Should it use a
post-KAFKA-20169 Streams client version, or should the old-client case verify
normal streams-protocol compatibility without static membership?
> Add cross version system test for "streams" static group membership
> -------------------------------------------------------------------
>
> Key: KAFKA-20971
> URL: https://issues.apache.org/jira/browse/KAFKA-20971
> Project: Kafka
> Issue Type: Test
> Components: streams, system tests
> Affects Versions: 4.4.0
> Reporter: Matthias J. Sax
> Assignee: Harsh Vasava
> Priority: Minor
>
> We added support for static group membership on the "streams" protocol. This
> is a broker side fix, and thus Kafka Streams client 4.3 and 4.2 should also
> be able to use static membership against a 4.4+ broker. But we do not have a
> system test for this.
> We should also have a negative test, that a 4.4+ Kafka Streams client, agains
> an older broker 4.3/4.2 get a clear error message that static membership is
> not supported.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
