[
https://issues.apache.org/jira/browse/FLINK-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627824#comment-14627824
]
ASF GitHub Bot commented on FLINK-1967:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/906#issuecomment-121559974
Yeah, we can add a way to not have timestamps. But my feeling is that this
is pre-mature optimization.
The point where this is really relevant is when people do super small
records and push the throughput to max capacity. That impacts standalone
benchmarks, but is probably not a real world issue.
> 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)
