You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Kirk True (Jira)" <ji...@apache.org> on 2023/12/19 02:51:00 UTC

[jira] [Updated] (KAFKA-15840) Correct initialization of ConsumerGroupHeartbeat by client

     [ https://issues.apache.org/jira/browse/KAFKA-15840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kirk True updated KAFKA-15840:
------------------------------
    Labels: kip-848 kip-848-client-support kip-848-e2e kip-848-preview  (was: kip-848-client-support kip-848-e2e kip-848-preview)

> Correct initialization of ConsumerGroupHeartbeat by client
> ----------------------------------------------------------
>
>                 Key: KAFKA-15840
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15840
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, consumer
>            Reporter: Andrew Schofield
>            Assignee: Andrew Schofield
>            Priority: Major
>              Labels: kip-848, kip-848-client-support, kip-848-e2e, kip-848-preview
>
> The new consumer using the KIP-848 protocol currently leaves the TopicPartitions set to null for the ConsumerGroupHeartbeat request, even when the MemberEpoch is zero. This violates the KIP which expects the list to be empty (but not null).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)