flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10037) Document details event time behavior in a single location
Date Mon, 06 Aug 2018 17:20:00 GMT

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

ASF GitHub Bot commented on FLINK-10037:

fhueske commented on issue #6481: [FLINK-10037] [Documentation] Add Event Time Details documentation
URL: https://github.com/apache/flink/pull/6481#issuecomment-410783694
   I agree, there is some overlap with the existing docs. 
   However, the document also includes a lot of valuable information that is not available
in the docs but only in code comments.
   I think we should come up with a good structure for the event-time docs and then move the
content from the different places into this structure. 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Document details event time behavior in a single location
> ---------------------------------------------------------
>                 Key: FLINK-10037
>                 URL: https://issues.apache.org/jira/browse/FLINK-10037
>             Project: Flink
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.5.2
>            Reporter: Elias Levy
>            Assignee: Elias Levy
>            Priority: Minor
>              Labels: pull-request-available
> A description of event time and watermarks, how they generated, assigned, and handled,
is spread across many pages in the documentation.  I would be useful to have it all in a
single place and includes missing information, such as how Flink assigns timestamps to new
records generated by operators.

This message was sent by Atlassian JIRA

View raw message