Thanks for the clarification

On 28 April 2016 at 15:12, P. Taylor Goetz <[email protected]> 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 documentation is corrected.
>
> OutputCollector is NOT thread-safe.
>
> -Taylor
>
> On Apr 28, 2016, at 9:06 AM, Stephen Powis <[email protected]> wrote:
>
> "Its perfectly fine to launch new threads in bolts that do processing
> asynchronously. OutputCollector
> <http://storm.apache.org/releases/current/javadocs/org/apache/storm/task/OutputCollector.html>
> 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#bolts
>
> On Thu, Apr 28, 2016 at 9:03 AM, P. Taylor Goetz <[email protected]>
> 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 <[email protected]>
>> wrote:
>>
>> 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 <[email protected]> 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 ***
>>>
>>
>>
>>
>> --
>>
>> *Open Source Solutions for Text Engineering*
>>
>> http://www.digitalpebble.com
>> http://digitalpebble.blogspot.com/
>> #digitalpebble <http://twitter.com/digitalpebble>
>>
>>
>
>


-- 

*Open Source Solutions for Text Engineering*

http://www.digitalpebble.com
http://digitalpebble.blogspot.com/
#digitalpebble <http://twitter.com/digitalpebble>

Reply via email to