[
https://issues.apache.org/jira/browse/KAFKA-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995766#comment-14995766
]
ASF GitHub Bot commented on KAFKA-2723:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/441
> Standardize new consumer exceptions
> -----------------------------------
>
> Key: KAFKA-2723
> URL: https://issues.apache.org/jira/browse/KAFKA-2723
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Blocker
> Fix For: 0.9.0.0
>
>
> The purpose of this ticket is to standardize and cleanup the exceptions
> thrown by the new consumer to ensure 1) that exceptions are only raised when
> there is no reasonable way of handling them internally, 2) that raised
> exceptions are documented properly, 3) that exceptions provide enough
> information for handling.
> For all blocking methods, the following exceptions are possible:
> - AuthorizationException (can only thrown if cluster is configured for
> authorization)
> - WakeupException (only thrown with an explicit call to wakeup())
> - ApiException (invalid session timeout, invalid groupId, inconsistent
> assignment strategy, etc.)
> Additionally, the following methods have special exceptions.
> poll():
> - SerializationException (problems deserializing keys/values)
> - InvalidOffsetException (only thrown if no reset policy is defined; includes
> OffsetOutOfRange and NoOffsetForPartition)
> commit():
> - CommitFailedException (only thrown if group management is enabled and a
> rebalance completed before the commit could finish)
> position():
> - InvalidOffsetException (same as above)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
