You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "Vlad Rozov (JIRA)" <ji...@apache.org> on 2016/11/17 17:46:00 UTC

[jira] [Updated] (APEXCORE-510) Enforce DefaultOutputPort.emit() or Sink.put() thread affinity

     [ https://issues.apache.org/jira/browse/APEXCORE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vlad Rozov updated APEXCORE-510:
--------------------------------
    Fix Version/s: 3.5.0

> 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
>            Assignee: Sanjay M Pujare
>             Fix For: 3.5.0
>
>
> 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)