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

Posted to jira@kafka.apache.org by "Matthias J. Sax (Jira)" <ji...@apache.org> on 2025/12/02 01:53:00 UTC

[jira] [Updated] (KAFKA-19945) StreamsGroupHearbeat response should always set the status

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

Matthias J. Sax updated KAFKA-19945:
------------------------------------
    Component/s: streams

> StreamsGroupHearbeat response should always set the status
> ----------------------------------------------------------
>
>                 Key: KAFKA-19945
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19945
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>    Affects Versions: 4.2.0
>            Reporter: Lucas Brutschy
>            Assignee: Lucas Brutschy
>            Priority: Major
>
> The status field should always set in the response, even when empty, to ensure that the status gets reset on the client.
> We are not doing this due to an oversight - it is defined as nullable, and is null when not set. So status does not clear correctly on the client, which ignores the field if it's null. 
> This mostly has no effect, since we are logging the status, but it is still confusing.



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