[KAFKA-2723] Standardize new consumer exceptions

• Type: Improvement
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 0.9.0.0
• Assignee: Jason Gustafson
• Reporter: Jason Gustafson
• Created: 02/Nov/15 05:19
• Updated: 08/Nov/15 19:57
• Resolved: 08/Nov/15 19:26

Description

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)