[
https://issues.apache.org/jira/browse/KAFKA-19613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016004#comment-18016004
]
Lianet Magrans commented on KAFKA-19613:
----------------------------------------
Agree it sounds useful to expose a Corrupt error including TP and offset (with
KIP), but just to be clear, this info is not passed to the client at the
moment, so it's not only about changing the client poll API, we need to sort
out if the info is available when generating the error on the broker side? Just
to be sure that this is doable, and that we can determine a corrupt/helpful
offset to pass back in the error
> 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
>
> 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)
