[
https://issues.apache.org/jira/browse/APEXCORE-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086692#comment-16086692
]
Pramod Immaneni commented on APEXCORE-759:
------------------------------------------
Wait a minute. Why would 1 x N with thread local not be a valid case? All
downstream partitions along with the upstream operator in a single thread. It
is an unusual case but would be useful in cases where just one downstream
partition cannot be used, for example, an operator where each partition can
only write to one table and multiple partitions are needed to write to multiple
tables.
> Operators connected using THREAD_LOCAL stream locality should enforce
> parallel partition scheme
> -----------------------------------------------------------------------------------------------
>
> Key: APEXCORE-759
> URL: https://issues.apache.org/jira/browse/APEXCORE-759
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Vinay Bangalore Srikanth
> Attachments: apex (1).log, apex.log
>
>
> In my application -
> http://node0.morado.com:9090/static/#/ops/apps/application_1499808956620_0190
> , I have set the locality to be THREAD_LOCAL.
> Upstream operator - Random string generator (with 4 partitions)
> Downstream operator - Custom console operator (with 5 partitions)
> The containers are getting killed. Exceptions from container-launch are seen.
> Logical message has to be displayed by handling exceptions.
> Logs are attached for one of the containers - Id: 01_000126 that was killed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
