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-7568) Bring window documentation up-to-date with latest changes and improve
Date Tue, 05 Sep 2017 15:29:00 GMT

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

ASF GitHub Bot commented on FLINK-7568:

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

    --- Diff: docs/dev/stream/operators/windows.md ---
    @@ -111,6 +111,11 @@ windows) assign elements to windows based on time, which can either
be processin
     time. Please take a look at our section on [event time]({{ site.baseurl }}/dev/event_time.html)
to learn
     about the difference between processing time and event time and how timestamps and watermarks
are generated.
    +Time-based windows have a *start timestamp* (inclusive) and an *end timestamp* (exclusive)
    +that together describe the size of the window. In code, Flink uses `TimeWindow` when
working with
    +time-based windows, this has methods for querying the start- and end-timestamp and also
    --- End diff --

> Bring window documentation up-to-date with latest changes and improve
> ---------------------------------------------------------------------
>                 Key: FLINK-7568
>                 URL: https://issues.apache.org/jira/browse/FLINK-7568
>             Project: Flink
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
> Off the top of my head:
>  - Make {{ProcessWindowFunction}} the primary window function, threat {{WindowFunction}}
as legacy
>  - Document more specifically how windowing behaves: window boundaries, chaining of several
windowed operations, timestamps of emitted data, what is "key" in a {{ProcessWindowFunction}}...

This message was sent by Atlassian JIRA

View raw message