t;user@storm.apache.org"
Date: Thursday, December 4, 2014 at 11:40 AM
To: "user@storm.apache.org"
Subject: Re: Shared static data between bolts
Thanks!
All the answers give me good idea.
Here's why I need this list be sharable.
One bolt needs the list for computation.
Anoth
initialization, will bolts of type B see the same instance?
>>>>>
>>>>> Sent from my Android phone
>>>>> On Dec 4, 2014 10:26 PM, "Eyal Golan" wrote:
>>>>>
>>>>>> Thanks Michael and Ben !
>>>>>>
>>
>>>> Sent from my Android phone
>>>> On Dec 4, 2014 10:26 PM, "Eyal Golan" wrote:
>>>>
>>>>> Thanks Michael and Ben !
>>>>>
>>>>> Sent from my Android phone
>>>>> On Dec 4, 2014 9:53 PM, "
tforward to implement a distributed data structure.
From: Eyal Golan
Reply-To: "user@storm.apache.org"
Date: Thursday, December 4, 2014 at 11:40 AM
To: "user@storm.apache.org"
Subject: Re: Shared static data between bolts
Thanks!
All the answers give me good id
ser@storm.apache.org"
Date: Thursday, December 4, 2014 at 11:40 AM
To: "user@storm.apache.org"
Subject: Re: Shared static data between bolts
Thanks!
All the answers give me good idea.
Here's why I need this list be sharable.
One bolt needs the list for computation.
A
Thanks Michael and Ben !
>>>>
>>>> Sent from my Android phone
>>>> On Dec 4, 2014 9:53 PM, "Flint, Ben" wrote:
>>>>
>>>>> I’ve used Hazelcast for use cases like this with great success. It
>>>>> makes it relatively straigh
On Dec 4, 2014 9:53 PM, "Flint, Ben" wrote:
>>>
>>>> I’ve used Hazelcast for use cases like this with great success. It
>>>> makes it relatively straightforward to implement a distributed data
>>>> structure.
>>>>
>>>
ke this with great success. It
>>>> makes it relatively straightforward to implement a distributed data
>>>> structure.
>>>>
>>>> From: Eyal Golan
>>>> Reply-To: "user@storm.apache.org"
>>>> Date: Thursday, December
"Flint, Ben" wrote:
>>
>>> I’ve used Hazelcast for use cases like this with great success. It
>>> makes it relatively straightforward to implement a distributed data
>>> structure.
>>>
>>> From: Eyal Golan
>>> Reply-To: "
t;user@storm.apache.org"
>> Date: Thursday, December 4, 2014 at 11:40 AM
>> To: "user@storm.apache.org"
>> Subject: Re: Shared static data between bolts
>>
>> Thanks!
>> All the answers give me good idea.
>> Here's why I need
Golan
> Reply-To: "user@storm.apache.org"
> Date: Thursday, December 4, 2014 at 11:40 AM
> To: "user@storm.apache.org"
> Subject: Re: Shared static data between bolts
>
> Thanks!
> All the answers give me good idea.
> Here's why I need this list b
ser@storm.apache.org>>
Date: Thursday, December 4, 2014 at 11:40 AM
To: "user@storm.apache.org<mailto:user@storm.apache.org>"
mailto:user@storm.apache.org>>
Subject: Re: Shared static data between bolts
Thanks!
All the answers give me good idea.
Here's why I need th
Hazelcast is killing a cockroach with a sledgehammer in this case. Have
your singleton able to initialize its self, then in prepare() of your bolts
call out to init it. Whichever one gets there first will lock it, then
it'll initialize and unlock. Other bolts will call init, find it already
initial
Thanks!
All the answers give me good idea.
Here's why I need this list be sharable.
One bolt needs the list for computation.
Another bolt will periodically update the list.
In other words, the list is changeable.
I tried passing it in conf but there are some 3rd party libs in the wrapper.
Anyway,
Hi Eyal,
I had the similar issue earlier. Static objects are not a good way of
passing the variables around in Storm due to clustered nature of the Storm.
You will see null for all the static variables.
This is how I implemented mine, for instance I wanted to pass around the
server properties suc
Eyal,
Don't instantiate it in the main method just set it when you are defining
the variable.
private static List SHARED_LIST = Arrays.asList("item1","item2");
On Thu, Dec 4, 2014 at 2:01 PM, Eyal Golan wrote:
> Hi all,
> I am newbie with Storm and having some issues with static objects in the
Hi Eyal,
you should be instantiating it on first access instead, then (preferably)
getting one of the bolts to do so in the prepare method.
Rules of singletons still apply, do your double-check locking to ensure you
don't do it twice.
Doing it in the main method will initialize it on the machine
Hi all,
I am newbie with Storm and having some issues with static objects in the
topology.
In the main class, where I set the topology, I also set a static object.
It's actually a wrapper for a collection of strings.
This object needs to he shared between different bolts.
It's big so I want it to b
18 matches
Mail list logo