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

ASF GitHub Bot commented on KAFKA-2723:
---------------------------------------

GitHub user hachikuji opened a pull request:

    https://github.com/apache/kafka/pull/452

    KAFKA-2723: new consumer exception cleanup (0.9.0)

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/hachikuji/kafka KAFKA-2723

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/452.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #452
    
----
commit a43e0b6aa5d3ebb97cda25884f660ce1fb8f895a
Author: Jason Gustafson <ja...@confluent.io>
Date:   2015-11-05T00:15:20Z

    KAFKA-2723: new consumer exception cleanup

commit 07baaff46498d473471f6fcf7b46dd12a11a7964
Author: Jason Gustafson <ja...@confluent.io>
Date:   2015-11-07T01:54:03Z

    address review comments

commit 087cb8db353bb2b448d39f5c093819815084ef15
Author: Jason Gustafson <ja...@confluent.io>
Date:   2015-11-08T05:56:19Z

    add package prefix to all @throws docs for consistency

----


> 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)

Reply via email to