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

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

GitHub user kl0u opened a pull request:

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

    [FLINK-4133] Reflect streaming file source changes in documentation

    The title says it all. 
    It documents the continuous file processing semantics recently introduced 
in the Streaming API.

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

    $ git pull https://github.com/kl0u/flink file_src_doc

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

    https://github.com/apache/flink/pull/2198.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 #2198
    
----
commit ed0d7168f52a3354f074b5a32943e4cdb9be86f0
Author: kl0u <[email protected]>
Date:   2016-07-04T14:17:58Z

    [FLINK-4133] Reflect streaming file source changes in documentation

----


> Reflect streaming file source changes in documentation
> ------------------------------------------------------
>
>                 Key: FLINK-4133
>                 URL: https://issues.apache.org/jira/browse/FLINK-4133
>             Project: Flink
>          Issue Type: Bug
>          Components: DataStream API, Documentation
>            Reporter: Robert Metzger
>            Assignee: Kostas Kloudas
>
> In FLINK-2314 the file sources for the DataStream API were reworked.
> The documentation doesn't explain the (new?) semantics of the file sources.
> In which order are files read?
> How are file modifications treated? (appends, in place modifications?)
> I suspect this table is also not up-to-date: 
> https://ci.apache.org/projects/flink/flink-docs-master/apis/streaming/fault_tolerance.html#fault-tolerance-guarantees-of-data-sources-and-sinks
>  



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

Reply via email to