You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "Chaitanya (JIRA)" <ji...@apache.org> on 2016/07/19 11:48:20 UTC

[jira] [Assigned] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator.

     [ https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chaitanya reassigned APEXCORE-494:
----------------------------------

    Assignee: Chaitanya

> 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)