You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/09 02:52:29 UTC

[jira] [Updated] (STORM-66) taskId not sent to spout on initial handshake

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

Rick Kellogg updated STORM-66:
------------------------------
    Component/s: storm-core

> taskId not sent to spout on initial handshake
> ---------------------------------------------
>
>                 Key: STORM-66
>                 URL: https://issues.apache.org/jira/browse/STORM-66
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>            Reporter: James Xu
>            Assignee: David Losada
>             Fix For: 0.9.3
>
>
> 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.3.4#6332)