You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2016/01/27 08:10:39 UTC
[jira] [Assigned] (KAFKA-3125) Exception Hierarchy for Streams
[ https://issues.apache.org/jira/browse/KAFKA-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guozhang Wang reassigned KAFKA-3125:
------------------------------------
Assignee: Guozhang Wang
> 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
> Assignee: 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)