You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "TengYao Chi (Jira)" <ji...@apache.org> on 2025/04/10 14:22:00 UTC

[jira] [Resolved] (KAFKA-18935) Ensure brokers do not return null records in FetchResponse

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

TengYao Chi resolved KAFKA-18935.
---------------------------------
    Resolution: Fixed

> Ensure brokers do not return null records in FetchResponse
> ----------------------------------------------------------
>
>                 Key: KAFKA-18935
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18935
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Ismael Juma
>            Assignee: TengYao Chi
>            Priority: Major
>
> As part of KIP-896, we discovered that all known versions of librdkafka (and related clients) fail if the returned records are null. The specific example that caused a failure in their test suite was a fetch response where authorization failed.
> We fixed the code not to return null records and originally also changed the schema to make the records not nullable. However, the latter was problematic and we reverted it via [https://github.com/apache/kafka/pull/19131] (the reasons are explained there).
> In order to make sure we don't regress, we should consider introducing validation and/or tests that ensure brokers do not return null records in fetch responses.
> This issue is for changes that do not involve schema definition changes. KAFKA-18934 tracks schema related changes (which can only be done for newer versions of fetch request/response).



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