You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Lucas Brutschy (Jira)" <ji...@apache.org> on 2022/09/28 11:17:00 UTC
[jira] [Updated] (KAFKA-10733) Enhance Transactional Producer Exception Handling
[ https://issues.apache.org/jira/browse/KAFKA-10733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lucas Brutschy updated KAFKA-10733:
-----------------------------------
Summary: Enhance Transactional Producer Exception Handling (was: Enforce exception thrown for KafkaProducer txn APIs)
> Enhance Transactional Producer Exception Handling
> -------------------------------------------------
>
> 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
>
> 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.20.10#820010)