[ 
https://issues.apache.org/jira/browse/FLINK-5249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15720084#comment-15720084
 ] 

ASF GitHub Bot commented on FLINK-5249:
---------------------------------------

GitHub user alpinegizmo opened a pull request:

    https://github.com/apache/flink/pull/2932

    [FLINK-5249] [docs] description of datastream rescaling doesn't match…

    In docs/dev/datastream_api.html#physical-partitioning the figure shows a 
parallelism of 2 rescaling to 6 and back to 2 – while the text assumes 4, 
rather than 6. This makes the explanation very confusing.
    
    See the figure at the end of [this 
section](https://ci.apache.org/projects/flink/flink-docs-release-1.2/dev/datastream_api.html#physical-partitioning).

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/alpinegizmo/flink rescaling-description

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2932.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 #2932
    
----
commit 7e448955180b0525bf1324c3fd4296dbc2a9a71e
Author: David Anderson <[email protected]>
Date:   2016-12-04T14:32:23Z

    [FLINK-5249] [docs] description of datastream rescaling doesn't match the 
figure

----


> description of datastream rescaling doesn't match the figure
> ------------------------------------------------------------
>
>                 Key: FLINK-5249
>                 URL: https://issues.apache.org/jira/browse/FLINK-5249
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: David Anderson
>            Priority: Minor
>
> In 
> https://ci.apache.org/projects/flink/flink-docs-release-1.2/dev/datastream_api.html#physical-partitioning
>  the figure shows a parallelism of 2 rescaling to 6 and back to 2 -- while 
> the text assumes 4, rather than 6. This makes the explanation very confusing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to