[
https://issues.apache.org/jira/browse/FLINK-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354370#comment-17354370
]
Timo Walther commented on FLINK-22737:
--------------------------------------
As I said before, I would be fine with Long.MIN_VALUE or NULL. Long.MIN_VALUE
perfectly integrates with DataStream API and stream operators. My only concern
was that it might look weird when printing because it would show as
{{-292275055-05-16T16:47:04.192Z}} when printing a {{LocalDateTime}} or
{{Instant}}. However, we can fix this as part of FLINK-21456 where we improve
the printing and will limit the year digits to 4. This would ensure that we
don't break the contracts mentioned in the docs of {{TimestampType}}.
> Add support for CURRENT_WATERMARK to SQL
> ----------------------------------------
>
> Key: FLINK-22737
> URL: https://issues.apache.org/jira/browse/FLINK-22737
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: David Anderson
> Assignee: Ingo Bürk
> Priority: Major
>
> With a built-in function returning the current watermark, one could operate
> on late events without resorting to using the DataStream API.
> Called with zero parameters, this function returns the current watermark for
> the current row – if there is an event time attribute. Otherwise, it returns
> NULL.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
