apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator.
Date Fri, 22 Jul 2016 14:03:20 GMT

    [ https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389549#comment-15389549

ASF GitHub Bot commented on APEXCORE-494:

Github user amberarrow commented on the issue:

    @chaithu14 Yes, some or all of the current partitions (possibly augmented by new ones)
can be returned by definePartitions(). See https://issues.apache.org/jira/browse/APEXCORE-439
for a similar issue that
    was resolved.

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

This message was sent by Atlassian JIRA

View raw message