[
https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388946#comment-15388946
]
ASF GitHub Bot commented on APEXCORE-494:
-----------------------------------------
Github user chaithu14 commented on the issue:
https://github.com/apache/apex-core/pull/359
@vrozov Can the definePartitions() return the current partition ? If yes,
then there might be an issue in redoPartition().
From the above example, for the logical operator C, current partition size
is 2 and new partition size is 3 which consists of current partitions {C1, C2}.
Output port of C1 (or) C2 maps to input port of Unifier.
If the physical dag as below:
A1->B1->C1->Aggregator.
Current partition size = 1
A is repartitioned to 2 then physical dag as below:
A1->B1->C1->
U -> Aggregator
A2->B2->C2->
new partition size = 2
Here, in the initial launch, Output of C1 maps to input of Aggregator and
in after repartition, output of C1 maps to unifier. The mapping of current
partition (A1) has changed in after repartition. I think, this case is not
covered in redopartitions().
Please correct it, if i am wrong.
> 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)
