[
https://issues.apache.org/jira/browse/APEXCORE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255617#comment-15255617
]
ASF GitHub Bot commented on APEXCORE-439:
-----------------------------------------
Github user amberarrow commented on the pull request:
https://github.com/apache/incubator-apex-core/pull/314#issuecomment-213982499
One question: if partitions P{1,2} are shuffled to Q{1,2,3} via unifiers
U{1,2.3} and Q is now repartitioned
to Q{1,4} (i.e. Q2 and Q3 are discarded, Q4 is new and Q1 is preserved),
will we have these actions:
-- U1 preserved;
-- U{2,3} be killed; and
-- new unifier U4 created and deployed ?
> 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)
