You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "David Jacot (Jira)" <ji...@apache.org> on 2021/10/18 07:34:00 UTC

[jira] [Commented] (KAFKA-10733) Enforce exception thrown for KafkaProducer txn APIs

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

David Jacot commented on KAFKA-10733:
-------------------------------------

[~bchen225242] Do we plan to get this on in 3.1.0? It seems that nobody works on it.

> Enforce exception thrown for KafkaProducer txn APIs
> ---------------------------------------------------
>
>                 Key: KAFKA-10733
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10733
>             Project: Kafka
>          Issue Type: Improvement
>          Components: producer , streams
>    Affects Versions: 2.5.0, 2.6.0, 2.7.0
>            Reporter: Boyang Chen
>            Priority: Major
>              Labels: need-kip
>             Fix For: 3.1.0
>
>
> 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)