[
https://issues.apache.org/jira/browse/FLINK-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354876#comment-17354876
]
Leonard Xu commented on FLINK-22737:
------------------------------------
* -1 for using *NULL* which will bring the three value logic which makes user
confused very much in some cases like filtering out the non-late data.
* slightly +0 for using *Long.MIN_VALUE* to represent a timepoint. Although
it's a meaningless timepoint and may overflow under some timezones when we
subtract time zone offset, we can check the reasonable range in FLINK-21456.
> 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
> Attachments: screenshot-2021-05-31_14-22-43.png
>
>
> 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)
