[
https://issues.apache.org/jira/browse/APEXCORE-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384006#comment-15384006
]
ASF GitHub Bot commented on APEXCORE-494:
-----------------------------------------
GitHub user chaithu14 opened a pull request:
https://github.com/apache/apex-core/pull/359
APEXCORE-494 Fixed the dynamic partition issue in case of initial partition
size is 1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chaithu14/incubator-apex-core
APEXCORE-494-DPartIssue
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-core/pull/359.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #359
----
commit c4578818fb970580310cff1d3a24d6884645c233
Author: Chaitanya <chaita...@datatorrent.com>
Date: 2016-07-19T11:42:48Z
APEXCORE-494 Fixed the dynamic partition issue in case of initial partition
size is 1
----
> 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)
