apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay M Pujare (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-510) Enforce DefaultOutputPort.emit() or Sink.put() thread affinity
Date Mon, 26 Sep 2016 16:52:20 GMT

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

Sanjay M Pujare commented on APEXCORE-510:
------------------------------------------

Pointer to discussion on dev@apex list: http://apache-apex-developers-list.78491.x6.nabble.com/Re-can-operators-emit-on-a-different-from-the-operator-itself-thread-tt8736.html

> 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)

Mime
View raw message