[
https://issues.apache.org/jira/browse/APEXCORE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254001#comment-15254001
]
ASF GitHub Bot commented on APEXCORE-439:
-----------------------------------------
GitHub user PramodSSImmaneni opened a pull request:
https://github.com/apache/incubator-apex-core/pull/314
APEXCORE-439 Fixing operator redeploy
Just for perusal, need to add unit test.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PramodSSImmaneni/incubator-apex-core
APEXCORE-439
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-apex-core/pull/314.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 #314
----
commit 6cad40e165c29c97c0c11d248058d75d76245649
Author: Pramod Immaneni <[email protected]>
Date: 2016-04-22T14:05:39Z
Setting correct state to redeploy operator, operator will be undeployed
first followed by a deploy
----
> 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)
