[ https://issues.apache.org/jira/browse/STORM-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381927#comment-14381927 ]
ASF GitHub Bot commented on STORM-587: -------------------------------------- Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/475#issuecomment-86536961 Sorry I am wrong, I need to look at it more. It is convoluted the path through the code, which is why I need to look into this more. Right now it appears to be the stream id, which seems incorrect to me, but I'll read through it. > trident transactional state in zk should be namespaced with topology id > ----------------------------------------------------------------------- > > Key: STORM-587 > URL: https://issues.apache.org/jira/browse/STORM-587 > Project: Apache Storm > Issue Type: Improvement > Reporter: Parth Brahmbhatt > Assignee: Sriharsha Chintalapani > > Currently when a trident transaction spout is initialized it creates a node > in zk under /transactional with the spout name as the node's name. This is > pretty dangerous as any other topology can be submitted with same spout name > and now these 2 spouts will be overwriting each other's states. I believe it > is better to namespace this with topologyId just like all other zk entries > under /storm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)