[
https://issues.apache.org/jira/browse/APEXCORE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255594#comment-15255594
]
ASF GitHub Bot commented on APEXCORE-439:
-----------------------------------------
Github user amberarrow commented on a diff in the pull request:
https://github.com/apache/incubator-apex-core/pull/314#discussion_r60845111
--- Diff:
engine/src/main/java/com/datatorrent/stram/plan/physical/PhysicalPlan.java ---
@@ -979,6 +998,14 @@ public void deployChanges() {
this.undeployOpers.removeAll(newOpers.keySet());
--- End diff --
For consistency, prefix getDependents() with "this." (though I find the
unnecessary use of "this" distracting -- my mind immediately starts to scan the
code for possible ambiguities when there are none).
> 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)
