t; I believe you can just call #name. E.g. persistentAggregate( ...
>> ).name( "name" )
>> --
>> From: Justin Workman
>> Sent: 6/25/2014 8:56 AM
>> To: user@storm.incubator.apache.org
>> Subject: Naming Components In
/2014 8:56 AM
> To: user@storm.incubator.apache.org
> Subject: Naming Components In Trident Topology
>
> 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
I believe you can just call #name. E.g. persistentAggregate( ... ).name( "name"
)
-Original Message-
From: "Justin Workman"
Sent: 6/25/2014 8:56 AM
To: "user@storm.incubator.apache.org"
Subject: Naming Components In Trident Topology
This is probably a
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" wrot
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 topol
