You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by GitBox <gi...@apache.org> on 2019/06/25 18:42:31 UTC

[GitHub] [storm] JanecekPetr opened a new pull request #3034: STORM-3422: TupleCaptureBolt is not thread-safe

JanecekPetr opened a new pull request #3034: STORM-3422: TupleCaptureBolt is not thread-safe
URL: https://github.com/apache/storm/pull/3034
 
 
   Fixes [STORM-3422](https://issues.apache.org/jira/browse/STORM-3422).
   
   Note, **this is a preview PR meant as a base for more discussion**.
   
   There are two commits, two different approaches to the same problem, please take a look. The latter, I believe, is simpler and easier to understand.
   
   The synchronization is expected to be completely uncontended, we simply need a way to safely publish the changes made by one thread or the other. Either way, the usage of the class feels dirty, but there isn't much we can do now, is there?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services