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-1967) Introduce (Event)time in Streaming
Date Thu, 02 Jul 2015 09:58:04 GMT

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

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

Github user StephanEwen commented on the pull request:

    https://github.com/apache/flink/pull/879#issuecomment-117986440
  
    We may also try and think about how we assign timestamps. We have measured in some experiments
that it decreases peak throughput if you call `System.currentTimeMillis()` for every record.
Tricky thing is trying to figure out when to call it. There is no way to determine that based
on number of records, but to measure delay since the last record, well, you need to call it
as well ;-)


> 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)

Mime
View raw message