[
https://issues.apache.org/jira/browse/STORM-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376805#comment-14376805
]
Parth Brahmbhatt commented on STORM-587:
----------------------------------------
I agree with Sriharsha. I don't see why should we impose a constraint like this
when we can easily avoid 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)
