[
https://issues.apache.org/jira/browse/STORM-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902836#comment-13902836
]
ASF GitHub Bot commented on STORM-66:
-------------------------------------
GitHub user tuxpiper opened a pull request:
https://github.com/apache/incubator-storm/pull/34
STORM-66 send taskid on initial handshake
We needed this in our topologies so I just went ahead, grabbed code from
GeneralTopologyContext, and added it modified here. Hope it is fine!
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/incubator-storm STORM-66
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-storm/pull/34.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 #34
----
commit 47dba860094bbe381e0bd231a43e2501a98a855b
Author: David Losada <[email protected]>
Date: 2014-02-16T20:55:45Z
STORM-66 send taskid on initial handshake
----
> taskId not sent to spout on initial handshake
> ---------------------------------------------
>
> Key: STORM-66
> URL: https://issues.apache.org/jira/browse/STORM-66
> Project: Apache Storm (Incubating)
> Issue Type: Improvement
> Reporter: James Xu
>
> https://github.com/nathanmarz/storm/issues/645
> Contrary to the multilang protocol specification, storm does not send the
> taskId of the spout as part of the topology context.
> What is expected:
> "context": {
> "task->component": {
> "1": "example-spout",
> "2": "__acker",
> "3": "example-bolt"
> },
> "taskid": 3
> },
> What was provided:
> "context":{
> "task->component":{
> "1":"__acker",
> "2":"filter",
> "3":"filter",
> "4":"spout",
> "5":"spout",
> "6":"test"}
> }
> As is apparent, the taskId is not provided.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
