gust 2017 10:20
> *To:* Wijekoon, Manusha [ICG-IT]
> *Cc:* user@storm.apache.org
>
> *Subject:* Re: is stateful bolts production ready?
>
>
>
> If you want to use the provided state implementations, you don’t need to
> do any of what you mentioned. You bolt would be initialed with i
Hi Arun,
Could you please help me with my questions 2 and 3 if possible?
Thanks
Manusha
From: Arun Iyer [mailto:ai...@hortonworks.com] On Behalf Of Arun Mahadevan
Sent: 11 August 2017 10:20
To: Wijekoon, Manusha [ICG-IT]
Cc: user@storm.apache.org
Subject: Re: is stateful bolts production ready
rg>
Subject: Re: is stateful bolts production ready?
If you want to use the provided state implementations, you don’t need to do any
of what you mentioned. You bolt would be initialed with its last know state in
“initState” and the bolt can keep updating the state in “execute". The
framework
k...@citi.com>, "user@storm.apache.org"
<user@storm.apache.org>
Subject: Re: RE: is stateful bolts production ready?
In addition to the query, what is the intent of stateful bolt since we can just
hold state in bolt instance?
wangchunc...@outlook.com
From: Wijekoon, Man
ilto:user@storm.apache.org>
Subject: RE: is stateful bolts production ready?
In our case we prefer to use our own state implementation. After going through
the code and reading documentation, following is how I understand it. Could you
please see if my understanding is correct?
1. Derive from State
From: Arun Iyer [ai...@hortonworks.com] on behalf of Arun Mahadevan
[ar...@apache.org]
Sent: Monday, July 24, 2017 2:29 PM
To: user@storm.apache.org
Subject: Re: is stateful bolts production ready?
The bolt just needs to “put” the values into the Key-Value state that the bolt
gets
Hello
I am thinking of using stateful bolts to manage state of a bolt. From the
documentation it is not clear how to save the bolt state however. I understand
it has to be done when we process the checkpoint tuple, but how? Do I just need
to update the state object and storm pick it up during
