[
https://issues.apache.org/jira/browse/KAFKA-10733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17237764#comment-17237764
]
Boyang Chen commented on KAFKA-10733:
-------------------------------------
Several agreements being made on offline sync:
1. We should catch certain fatal exceptions and throw task migrated, such as
ProducerFenced
2. We should have a new producer exception type to wrap all non-fatal exception
to let user catch them and throw as task corrupted
3. We should still crash the stream thread for certain fatal exceptions, such
as AuthorizationException
> Enforce exception thrown for KafkaProducer txn APIs
> ---------------------------------------------------
>
> Key: KAFKA-10733
> URL: https://issues.apache.org/jira/browse/KAFKA-10733
> Project: Kafka
> Issue Type: Improvement
> Reporter: Boyang Chen
> Priority: Major
> Labels: need-kip
>
> In general, KafkaProducer could throw both fatal and non-fatal errors as
> KafkaException, which makes the exception catching hard. Furthermore, not
> every single fatal exception (checked) is marked on the function signature
> yet as of 2.7.
> We should have a general supporting strategy in long term for this matter, as
> whether to declare all non-fatal exceptions as wrapped KafkaException while
> extracting all fatal ones, or just add a flag to KafkaException indicating
> fatal or not, to maintain binary compatibility.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
