[
https://issues.apache.org/jira/browse/KAFKA-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666928#comment-15666928
]
ASF GitHub Bot commented on KAFKA-3637:
---------------------------------------
GitHub user enothereska opened a pull request:
https://github.com/apache/kafka/pull/2135
KAFKA-3637: Added initial states
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/enothereska/kafka KAFKA-3637-streams-state
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2135.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 #2135
----
commit 80548e1179adfae5d41a90c9bd43cd60ae37d5bf
Author: Eno Thereska <eno.there...@gmail.com>
Date: 2016-11-15T11:42:34Z
Added initial states
----
> Add method that checks if streams are initialised
> -------------------------------------------------
>
> Key: KAFKA-3637
> URL: https://issues.apache.org/jira/browse/KAFKA-3637
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 0.10.1.0
> Reporter: Eno Thereska
> Assignee: Eno Thereska
> Labels: newbie
> Fix For: 0.10.2.0
>
>
> Currently when streams are initialised and started with streams.start(),
> there is no way for the caller to know if the initialisation procedure
> (including starting tasks) is complete or not. Hence, the caller is forced to
> guess for how long to wait. It would be good to have a way to return the
> state of the streams to the caller.
> One option would be to follow a similar approach in Kafka Server
> (BrokerStates.scala).
> Would be good for example, to keep track of whether Kafka Streams is
> starting/running/rebalancing
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
