You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (Jira)" <ji...@apache.org> on 2020/12/09 01:41:00 UTC

[jira] [Created] (KAFKA-10830) Kafka Producer API should throw unwrapped exceptions

Guozhang Wang created KAFKA-10830:
-------------------------------------

             Summary: Kafka Producer API should throw unwrapped exceptions
                 Key: KAFKA-10830
                 URL: https://issues.apache.org/jira/browse/KAFKA-10830
             Project: Kafka
          Issue Type: Improvement
          Components: producer 
            Reporter: Guozhang Wang


Today in various KafkaProducer APIs (especially send and transaction related) we wrap many of the underlying exception with a KafkaException. In some nested calls we may even wrap it more than once. Although the initial goal is to not expose the root cause directly to users, it also brings confusion to advanced user's error handling that some KafkaException wrapped root cause may be handled differently.

Since all of those exceptions are public classes anyways (since one can still get them via exception.root()) and they are all inheriting KafkaException, I'd suggest we do not do any wrapping any more and throw the exception directly. For those users who just capture all KafkaException and handle them universally it is still compatible; but for those users who want to handle exceptions differently it would introduce an easier way.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)