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

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

GitHub user fhueske opened a pull request:

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

    [FLINK-3333] [Documentation][DataSet] Improve documentation of DataSet 
object-reuse modes

    @ggevay, @greghogan Please have a look at this PR. 
    I basically copied the content of the [proposal in the Google 
document](https://docs.google.com/document/d/1jpPr2UuWlqq1iIDIo_1kmPL9QjA-sXAC9wkj-hE4PAc).
 

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

    $ git pull https://github.com/fhueske/flink reuseDocs

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

    https://github.com/apache/flink/pull/1721.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 #1721
    
----
commit 097e786c9b8f47a17f7a8b20e12fd79371271e47
Author: Fabian Hueske <[email protected]>
Date:   2016-02-26T13:29:25Z

    [FLINK-3333] [Documentation][DataSet] Improve documentation of DataSet 
object-reuse modes.

----


> Documentation about object reuse should be improved
> ---------------------------------------------------
>
>                 Key: FLINK-3333
>                 URL: https://issues.apache.org/jira/browse/FLINK-3333
>             Project: Flink
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.0.0
>            Reporter: Gabor Gevay
>            Assignee: Gabor Gevay
>            Priority: Critical
>             Fix For: 1.0.0
>
>
> The documentation about object reuse \[1\] has several problems, see \[2\].
> \[1\] 
> https://ci.apache.org/projects/flink/flink-docs-master/apis/batch/index.html#object-reuse-behavior
> \[2\] 
> https://docs.google.com/document/d/1cgkuttvmj4jUonG7E2RdFVjKlfQDm_hE6gvFcgAfzXg/edit



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

Reply via email to