[
https://issues.apache.org/jira/browse/KAFKA-20971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109308#comment-18109308
]
Matthias J. Sax commented on KAFKA-20971:
-----------------------------------------
Oh, I see. There is also a check client side... Well, for this case, we don't
need to include 4.3/4.2 clients against 4.4+ broker in the system test at all –
I am sure we test this guard via unit tests.
What now raises the question, if this ticket makes sense to begin with, because
we already have a 4.4-client plus 4.4-broker test. Seems there is nothing else
we need to cover via a system test for now? – Not sure if we might want to
consider to remove the client side guard for 4.3/4.2 patch releases, and add a
system test then... But technically, we should not do this, because it's not a
bug-fix... \cc [~lucasbru] WDTY?
This ticket might be a no-op after all...
> 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)