Thanks for your feedback. Turns out, the question was related to JStorm... I guess this should be consider for the merge process.
> sorry , i find i use the jstorm. storm is no problem. but when i use > jstorm，this problem arise -Matthias On 12/16/2015 03:25 PM, Arun Iyer wrote: > TopologyContext.getComponentTasks returns the list of task ids for the > component (not executor ids). > > You could just try printing the output of getComponentTasks in the prepare > method after doing 'setNumTasks’ (with task > parallelism) > while building the topology. Worked for me. > > - Arun > > > > On 12/16/15, 6:21 PM, "Matthias J. Sax" <[email protected]> wrote: > >> Hi, >> >> today, the above question appeared on SO: >> https://stackoverflow.com/questions/34309189/how-to-get-the-task-number-and-id-not-the-executor-in-storm >> >> The problem is, that >> >> TopologyContext.getComponentTasks(<componentId>) >> >> returns the IDs of the executors (and not the tasks). The name of the >> method is not chooses very good -- I guess this dates back to the time >> before the separation of tasks and executors... >> >> My question is now: >> >> - do tasks actually have an ID? >> - if yes, can those IDs be retrieved? >> - can we get at least the number of tasks per operator somehow? >> - should the above method get renamed? >> >> As the number of tasks is fix, one could of course collect this >> information an pass it via the Config to >> StormSubmitter.submitTopology(...). However, this is quite a work-around. >> >> Please let me know what you think about it. >> >> >> -Matthias >>
signature.asc
Description: OpenPGP digital signature
