You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Thomas Weise (JIRA)" <ji...@apache.org> on 2016/04/21 03:41:25 UTC

[jira] [Commented] (APEXCORE-439) After dynamic repartition application appears blocked

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

Thomas Weise commented on APEXCORE-439:
---------------------------------------

Pramod, I just spoke to Ram about this (he showed me the problem yesterday). The issue is that the unifier is not redeployed after partition change as expected. The most difficult part is to write a unit test that reproduces the issue. I can look into fixing it if you have such a test case or let me know if you need any pointers. It may also help to share the application code.


> After dynamic repartition application appears blocked
> -----------------------------------------------------
>
>                 Key: APEXCORE-439
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-439
>             Project: Apache Apex Core
>          Issue Type: Bug
>    Affects Versions: 3.3.0
>            Reporter: Munagala V. Ramanath
>            Assignee: Munagala V. Ramanath
>
> When a file input operator (subclass of AbstractFileInputOperator) is dynamically repartitioned, some downstream unifiers are not identified as needing to be redeployed causing the window id to not advance and all downstream operators to be killed and restarted.



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