Re: thread safe output collector

2016-04-29 Thread Stephen Powis
Now with that said, bolt > executes should not be long running computations either, but can be longer > than the spouts nextTuple function. > > > > *From:* Stephen Powis [mailto:spo...@salesforce.com] > *Sent:* Thursday, April 28, 2016 11:59 AM > *To:* user@storm.apache.org

RE: thread safe output collector

2016-04-29 Thread Hart, James W.
To: user@storm.apache.org Subject: Re: thread safe output collector So the Spout documentation (assuming its correct...) here (http://storm.apache.org/releases/current/Concepts.html#spouts) mentions this: "The main method on spouts is nextTuple. nextTuple either emits a new

Re: thread safe output collector

2016-04-28 Thread P. Taylor Goetz
> On Apr 28, 2016, at 1:48 PM, Steven Lewis <steven.le...@walmart.com> wrote: > > We tried implementing our own thread safe output collector but it seems > ridiculous for such a concurrent system. Why don’t they implement it in core > Storm? They can have the curren

Re: thread safe output collector

2016-04-28 Thread Steven Lewis
We tried implementing our own thread safe output collector but it seems ridiculous for such a concurrent system. Why don’t they implement it in core Storm? They can have the current one, and then build a separate one called Concurrent_OutputCollector or some such. I was hoping they fixed

Re: thread safe output collector

2016-04-28 Thread Julien Nioche
Thanks for the clarification On 28 April 2016 at 15:12, P. Taylor Goetz wrote: > The documentation is wrong. See: > > https://issues.apache.org/jira/browse/STORM-841 > > At some point it looks like the change made there got reverted. I will > reopen it to make sure the

Re: thread safe output collector

2016-04-28 Thread P. Taylor Goetz
The documentation is wrong. See: https://issues.apache.org/jira/browse/STORM-841 At some point it looks like the change made there got reverted. I will reopen it to make sure the documentation is corrected. OutputCollector is NOT thread-safe.

Re: thread safe output collector

2016-04-28 Thread Stephen Powis
"Its perfectly fine to launch new threads in bolts that do processing asynchronously. OutputCollector is thread-safe and can be called at any time." >From the docs for 0.9.6:

Re: thread safe output collector

2016-04-28 Thread P. Taylor Goetz
IIRC there was discussion about making it thread safe, but I don't believe it was implemented. -Taylor > On Apr 28, 2016, at 3:52 AM, Julien Nioche > wrote: > > Hi Stephen > > I asked the same question in February but did not get a reply > >

Re: thread safe output collector

2016-04-28 Thread Julien Nioche
Hi Stephen I asked the same question in February but did not get a reply https://mail-archives.apache.org/mod_mbox/storm-user/201602.mbox/%3cca+-fm0urpf3fuerozywpzmxu-kdbgf-zj3wbyr8evsaqjc6...@mail.gmail.com%3E Anyone who could confirm this? Thanks On 27 April 2016 at 14:05, Steven Lewis

thread safe output collector

2016-04-27 Thread Steven Lewis
I have conflicting information, and have not checked personally but has the output collector finally been made thread safe for emitting in version 1.0 or 0.10? I know it was a huge problem in 0.9.5 when trying to do threading in a bolt for async future calls and emitting once it returns. This