[
https://issues.apache.org/jira/browse/STORM-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718292#comment-14718292
]
ASF GitHub Bot commented on STORM-1016:
---------------------------------------
GitHub user victor-wong opened a pull request:
https://github.com/apache/storm/pull/706
STORM-1016: Generate trident bolt ids with sorted group names
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/victor-wong/storm STORM-1016
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/706.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #706
----
commit f8118e0854e49d70e75707e96ddb6524dff2a930
Author: wangjiasheng <[email protected]>
Date: 2015-08-27T06:57:27Z
STORM-1016: Generate trident bolt ids with sorted group names
----
> Generate trident bolt ids with sorted group names
> -------------------------------------------------
>
> Key: STORM-1016
> URL: https://issues.apache.org/jira/browse/STORM-1016
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: Jiasheng Wang
>
> In genBoltId() method of TridentTopology, groups are stored in HashSet.
> So everytime I submit my trident topology, I get different id for my
> component.
> For example, this time my bolt ids are (b-0-abc, b-1-def), next time they are
> (b-1-abc, b-0-def).
> It makes harder for users to track their metrics, and the bolt names in UI
> are changing too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
