Naming Components In Trident Topology

[Justin Workman <ju...@gmail.com>]

This is probably a silly question, that I am just overlooking the answer
to. We are playing with our first trident topology running under storm
0.9.1. Is there a way to descriptively name the components so they are
meaningful in the UI. Similar to how the components appear in the normal
storm topology.

Currently the UI shows

$mastercoord-bg0 for the spout

then the following for the bolts
$spoutcoord-spout0
b-1
b-0

Is there anyway to make this more friendly.

Thanks
Justin

Re: Naming Components In Trident Topology

["Cody A. Ray" <co...@gmail.com>]

There's a method on steam called name () which will let you do this.

For example

stream
    .each(...)
    .name("Transform")
    .parallelismHint(12)
    .groupBy(...)
    .persistent aggregate(...)
    .name("Aggregator")
    .parallelismHint(3);
On Jun 25, 2014 10:56 AM, "Justin Workman" <ju...@gmail.com> wrote:

> This is probably a silly question, that I am just overlooking the answer
> to. We are playing with our first trident topology running under storm
> 0.9.1. Is there a way to descriptively name the components so they are
> meaningful in the UI. Similar to how the components appear in the normal
> storm topology.
>
> Currently the UI shows
>
> $mastercoord-bg0 for the spout
>
> then the following for the bolts
> $spoutcoord-spout0
> b-1
> b-0
>
> Is there anyway to make this more friendly.
>
> Thanks
> Justin
>