[ 
https://issues.apache.org/jira/browse/KAFKA-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ewen Cheslack-Postava resolved KAFKA-3125.
------------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9.1.0

Issue resolved by pull request 809
[https://github.com/apache/kafka/pull/809]

> Exception Hierarchy for Streams
> -------------------------------
>
>                 Key: KAFKA-3125
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3125
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Guozhang Wang
>             Fix For: 0.9.1.0
>
>
> Currently Kafka Streams do not have its own exception category: we only have 
> one TopologyException that extends from KafkaException.
> It's better to start thinking about categorizing exceptions in Streams with a 
> common parent of "StreamsException". For example:
> 1. What type of exceptions should be exposed to users at job runtime; what 
> type of exceptions should be exposed at "topology build time".
> 2. Should KafkaStreaming.start / stop ever need to throw any exceptions?
> 3. etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to