[
https://issues.apache.org/jira/browse/FLINK-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17353485#comment-17353485
]
Ingo Bürk commented on FLINK-22737:
-----------------------------------
I have to admit that I find it quite odd to return 1/1/1970 for "no watermark
yet", it seems rather random to me to allow that to happen and NULL feels much
more semantically correct. But I understand that returning the epoch can make
things easier. Timo and I had discussed this as well and decided to propose
NULL because e.g. the Flink UI also doesn't show the Long.MIN_VALUE in this
case. But ultimately I am also fine with returning the epoch, I think Timo was
also kind of on the fence for this. [~twalthr] Should we just return the epoch
then or do you feel strongly about the NULL now?
> 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)
