[ 
https://issues.apache.org/jira/browse/APEXCORE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15586280#comment-15586280
 ] 

ASF GitHub Bot commented on APEXCORE-510:
-----------------------------------------

GitHub user sanjaypujare opened a pull request:

    https://github.com/apache/apex-core/pull/411

    APEXCORE-510  Implement check in DefaultOutputPort for thread affinity 
between setup and emit

    @vrozov  pls review and merge as appropriate

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sanjaypujare/apex-core 
malhar-510.thread_affinity

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/apex-core/pull/411.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #411
    
----
commit 41f0c94409891f37478ca5e3f72daefaddc1fcaf
Author: Sanjay Pujare <san...@datatorrent.com>
Date:   2016-09-29T00:23:06Z

    ALEXCORE-510 thread affinity check
    also implement a property to suppress thread affinity checks:

----


> Enforce DefaultOutputPort.emit() or Sink.put() thread affinity
> --------------------------------------------------------------
>
>                 Key: APEXCORE-510
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-510
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Vlad Rozov
>
> Apex platform assumes that an operator interacts with the platform using the 
> dedicated operator thread. Currently, operators may create worker threads and 
> emit tuples from a worker thread. This leads to undefined behavior and hard 
> to find bugs, so it should be possible to enforce that 
> DefaultOutputPort.emit() and/or Sink.put() are called on the operator thread.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to