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

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

Github user aljoscha commented on a diff in the pull request:

    https://github.com/apache/flink/pull/879#discussion_r33688371
  
    --- Diff: 
flink-core/src/main/java/org/apache/flink/api/common/ExecutionConfig.java ---
    @@ -141,6 +144,25 @@ public boolean isClosureCleanerEnabled() {
        }
     
        /**
    +    * Sets the interval of the automatic watermark emission. Watermaks are 
used throughout
    +    * the streaming system to keep track of the progress of time. They are 
used, for example,
    +    * for time based windowing.
    +    */
    +   public ExecutionConfig setAutoWatermarkInterval(Duration interval) {
    --- End diff --
    
    I think it doesn't make sense right now to add documentation for this 
without a document that describes the broad concepts in Streaming. This touches 
on a lot of stuff such as event-time vs processing-time, windowing semantics 
and so on. I think @StephanEwen started the discussion on such a document 
somewhere.


> Introduce (Event)time in Streaming
> ----------------------------------
>
>                 Key: FLINK-1967
>                 URL: https://issues.apache.org/jira/browse/FLINK-1967
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>
> This requires introducing a timestamp in streaming record and a change in the 
> sources to add timestamps to records. This will also introduce punctuations 
> (or low watermarks) to allow windows to work correctly on unordered, 
> timestamped input data. In the process of this, the windowing subsystem also 
> needs to be adapted to use the punctuations. Furthermore, all operators need 
> to be made aware of punctuations and correctly forward them. Then, a new 
> operator must be introduced to to allow modification of timestamps.



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

Reply via email to