[jira] [Created] (KAFKA-5052) We shouldn't pass the underlying exception to RetriableCommitFailedException when an async offset commit fails.

["Apurva Mehta (JIRA)" <ji...@apache.org>]

Apurva Mehta created KAFKA-5052:
-----------------------------------

             Summary: We shouldn't pass the underlying exception to RetriableCommitFailedException when an async offset commit fails.
                 Key: KAFKA-5052
                 URL: https://issues.apache.org/jira/browse/KAFKA-5052
             Project: Kafka
          Issue Type: Improvement
            Reporter: Apurva Mehta
            Assignee: Apurva Mehta


This is a follow up to : https://issues.apache.org/jira/browse/KAFKA-3527

We currently wrap retriable exceptions encountered during offset commits in a `RetriableOffsetCommitException`. The problem is that today we also pass the underlying exception on to the user. There isn't a really good reason to do this, since the user will not handle each individual exception differently: they will just retry anyway.

We should not pass on the underlying exception. It makes the API simpler, and also allows us to change things underneath with more flexibility.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)