nextTupleeither emits a new tuple into the topology or simply returns if there are no new tuples to emit. It is imperative that
nextTupledoes not block for any spout implementation, because Storm calls all the spout methods on the same thread."
Thanks for the clarificationOn 28 April 2016 at 15:12, P. Taylor Goetz <email@example.com> wrote:The documentation is wrong. See: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.-TaylorOn Apr 28, 2016, at 9:06 AM, Stephen Powis <firstname.lastname@example.org> wrote:
"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: http://storm.apache.org/releases/0.9.6/Concepts.html#boltsOn Thu, Apr 28, 2016 at 9:03 AM, P. Taylor Goetz <email@example.com> wrote: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 <firstname.lastname@example.org> wrote:Hi StephenI asked the same question in February but did not get a replyhttps://mail-archives.apache.org/mod_mbox/storm-user/201602.mbox/%3CCA+-fM0urPf3FUERoZywPzmxu-KDbGF-Zj3wbYr8evsAQJC6u_g@mail.gmail.com%3EAnyone who could confirm this?ThanksOn 27 April 2016 at 14:05, Steven Lewis <Steven.Lewis@walmart.com> wrote: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 email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. *** Walmart Confidential ***