[
https://issues.apache.org/jira/browse/APEXCORE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255662#comment-15255662
]
ASF GitHub Bot commented on APEXCORE-439:
-----------------------------------------
GitHub user PramodSSImmaneni opened a pull request:
https://github.com/apache/incubator-apex-core/pull/316
APEXCORE-439 Fix for operator re-deployment during dynamic partitioning
Continuing from a previous pull request
https://github.com/apache/incubator-apex-core/pull/314
@tweise @amberarrow please see
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/316.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 #316
----
commit d788fea96ac174d54b3fa683ec1221ef415d9297
Author: Pramod Immaneni <[email protected]>
Date: 2016-04-23T17:52:52Z
APEXCORE-439 Added re-deploying of dependencies of new operators generated
as a result of dynamic re-partitioning
----
> 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)
