[
https://issues.apache.org/jira/browse/KAFKA-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017511#comment-18017511
]
Uladzislau Blok commented on KAFKA-19613:
-----------------------------------------
About CRC checksum validation, that's depend I guess. This issue was created
based on original one for Kafka Streams (btw, this is a reason why I'm also
thinking / asking about validation) and exception was thrown from
FetchCollector#initialize method, so this is not about reading records and fail
with CRC check error, but about getting FetchResponse with error from broker.
You can check AbstractFetch#handleFetchSuccess method, if I missed something,
but I don't see any validation of broker response before
FetchCollector#initialize method
> Expose consumer CorruptRecordException as case of KafkaException
> ----------------------------------------------------------------
>
> 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 analysis of KAFKA-19430 , we decided it would be useful to expose
> root case of consumer request failure (e.g. currently we see just
> KafkaException instead of CorruptRecordException)
> The idea is to not change public API, but expose root case as a filed of
> KafkaException
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
