Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E81D3200B43 for ; Tue, 19 Jul 2016 08:51:34 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E6C54160A8B; Tue, 19 Jul 2016 06:51:34 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3F999160A76 for ; Tue, 19 Jul 2016 08:51:34 +0200 (CEST) Received: (qmail 12737 invoked by uid 500); 19 Jul 2016 06:51:33 -0000 Mailing-List: contact dev-help@apex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.apache.org Delivered-To: mailing list dev@apex.apache.org Received: (qmail 12726 invoked by uid 99); 19 Jul 2016 06:51:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jul 2016 06:51:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E46D6CF69E for ; Tue, 19 Jul 2016 06:51:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.507 X-Spam-Level: X-Spam-Status: No, score=-4.507 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id CbsMp2EEUm3o for ; Tue, 19 Jul 2016 06:51:32 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with SMTP id D59E65FACF for ; Tue, 19 Jul 2016 06:51:31 +0000 (UTC) Received: (qmail 11091 invoked by uid 99); 19 Jul 2016 06:51:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jul 2016 06:51:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 886192C0D59 for ; Tue, 19 Jul 2016 06:51:20 +0000 (UTC) Date: Tue, 19 Jul 2016 06:51:20 +0000 (UTC) From: "Chaitanya (JIRA)" To: dev@apex.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (APEXCORE-494) Window id of downstream operator is not moving after dynamic partition of upstream operator. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 19 Jul 2016 06:51:35 -0000 [ 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)