[
https://issues.apache.org/jira/browse/KAFKA-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans updated KAFKA-18221:
-----------------------------------
Description:
Currently KS uses the classic group protocol (while KIP-1071 completes). The
group.protocol config is explicitly set to CLASSIC in the core streams logic
but not in the streams tests.
This has been fine because the legacy KafkaConsumer (with classic protocol) is
the default one, but KS tests will break when the new consumer becomes the
default one.
We should explicitly set group.protocol (to "classic" for now) in all stream
tests that require it to avoid breaking them.
This gap showed when attempting to make the new consumer/protocol default with
[https://github.com/apache/kafka/pull/18121] (just an exercise for now, to find
this kind of gap)
was:
Currently KS uses the classic group protocol (while KIP-1071 completes). The
group.protocol config is explicitly set to CLASSIC in the core streams logic
but not in the streams tests.
This has been fine because the legacy KafkaConsumer (with classic protocol) is
the default one, but KS tests will break when the new consumer becomes the
default one.
We should explicitly set group.protocol (to "classic" for now) in all stream
tests that require it to avoid breaking them.
This gap showed when attempting to make the new consumer/protocol default with
[https://github.com/apache/kafka/pull/18121] (just an exercise for now, to find
these kind of gaps)
> Set explicit consumer group protocol in streams tests
> -----------------------------------------------------
>
> Key: KAFKA-18221
> URL: https://issues.apache.org/jira/browse/KAFKA-18221
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Major
> Fix For: 4.0.0
>
>
> Currently KS uses the classic group protocol (while KIP-1071 completes). The
> group.protocol config is explicitly set to CLASSIC in the core streams logic
> but not in the streams tests.
> This has been fine because the legacy KafkaConsumer (with classic protocol)
> is the default one, but KS tests will break when the new consumer becomes the
> default one.
> We should explicitly set group.protocol (to "classic" for now) in all stream
> tests that require it to avoid breaking them.
> This gap showed when attempting to make the new consumer/protocol default
> with [https://github.com/apache/kafka/pull/18121] (just an exercise for now,
> to find this kind of gap)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
