apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chaitanya (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator.
Date Tue, 19 Jul 2016 06:51:20 GMT

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

Chaitanya updated APEXCORE-494:
-------------------------------
    Attachment: PhysicalDAGBeforeKafkaRepartition.png
                PhysicalDAGAfterKafkaRepartition.png
                PhysicalOperatorAfterKafkaRepartition.png

Attaching some of the screenshots of sample application.

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

Mime
View raw message