[
https://issues.apache.org/jira/browse/KAFKA-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116358#comment-15116358
]
ASF GitHub Bot commented on KAFKA-3125:
---------------------------------------
GitHub user guozhangwang opened a pull request:
https://github.com/apache/kafka/pull/809
KAFKA-3125: Add Kafka Streams Exceptions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/guozhangwang/kafka K3125
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/809.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 #809
----
commit a23f4225609a765b12c45e982dda2a7c888f74e7
Author: Guozhang Wang <wangg...@gmail.com>
Date: 2016-01-25T22:32:19Z
re-order shutdown modules
commit 52efdbf97324eac12bfb369545a2fd29c31fd9ba
Author: Guozhang Wang <wangg...@gmail.com>
Date: 2016-01-26T00:21:27Z
add errors package and fixed a few thrown exceptions
----
> 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
>
> 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)
