[jira] [Commented] (STORM-587) trident transactional state in zk should be namespaced with topology id

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STORM-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083869#comment-15083869 ] 

ASF GitHub Bot commented on STORM-587:
--------------------------------------

Github user revans2 commented on the pull request:

    https://github.com/apache/storm/pull/475#issuecomment-169142720
  
    @harshach is this still something that you want?  If not please close the pull request if so I am happy to talk about a migration plan from one state layout to another.


> 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
>          Components: storm-core
>            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)