[
https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417017#comment-15417017
]
ASF GitHub Bot commented on APEXCORE-494:
-----------------------------------------
Github user chaithu14 commented on a diff in the pull request:
https://github.com/apache/apex-core/pull/365#discussion_r74402121
--- Diff:
engine/src/main/java/com/datatorrent/stram/plan/physical/StreamMapping.java ---
@@ -285,6 +286,17 @@ private void redoMapping()
if (finalUnifier == null) {
finalUnifier = createUnifier(streamMeta, plan);
}
+ // detach downstream from upstream operator when no final
unifier existed previously
+ for (PTOutput unifierSource : unifierSources) {
+ Iterator<PTInput> sinks = unifierSource.sinks.iterator();
+ while (sinks.hasNext()) {
+ PTInput sink = sinks.next();
+ if (sink.target == doperEntry.first) {
+ doperEntry.first.inputs.remove(sink);
+ sinks.remove();
+ }
+ }
+ }
setInput(doperEntry.first, doperEntry.second, finalUnifier,
(pks == null) || (pks.mask == 0) ? null : pks);
--- End diff --
Same fix should be in m*n partitioning block also.
> Window id of downstream operator is not moving after dynamic partition of
> upstream operator.
> --------------------------------------------------------------------------------------------
>
> Key: APEXCORE-494
> URL: https://issues.apache.org/jira/browse/APEXCORE-494
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Chaitanya
> Assignee: Chaitanya
> Attachments: PhysicalDAGAfterKafkaRepartition.png,
> PhysicalDAGBeforeKafkaRepartition.png,
> PhysicalOperatorAfterKafkaRepartition.png
>
>
> Created the following application to reproduce this issue.
> Application has the following DAG:
> KafkaSinglePortStringInputOperator(Input) -> ConsoleOutputOperator(Output)
>
> I launched the application with below configuration:
> Kafka topic created with single partition and replication factor as 1.
> Partition Strategy: ONE_TO_ONE
> Launched the application successfully. After some time, I increased the
> topic partitions to 2. After re-partition, the window of down stream operator
> is not moving. By looking into the app Physical DAG, it looks like there is
> an issue in construction of Physical DAG after re-partition.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
