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

[jira] [Commented] (KAFKA-19613) Expose consumer CorruptRecordException

    [ https://issues.apache.org/jira/browse/KAFKA-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023272#comment-18023272 ] 

Uladzislau Blok commented on KAFKA-19613:
-----------------------------------------

[~lianetm] [~mjsax] 
Hello All,
KIP is already prepared. Could you please take a look?
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-1218%3A+Expose+consumer+CorruptRecordException|http://example.com]

> Expose consumer CorruptRecordException
> --------------------------------------
>
>                 Key: KAFKA-19613
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19613
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients
>            Reporter: Uladzislau Blok
>            Assignee: Uladzislau Blok
>            Priority: Minor
>              Labels: need-kip
>         Attachments: corrupted_records.excalidraw.png
>
>
> As part of our analysis around KAFKA-19430, we realized it's not possible to handle a {{CorruptRecordException}} in Streams because it's not exposed to the client; instead, a generic {{KafkaException}} ** is thrown
> The proposed solution is to expose {{CorruptRecordException}} with information about affected TopicPartition and offset we're trying read from
> KIP: https://cwiki.apache.org/confluence/x/NQrxFg



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