[
https://issues.apache.org/jira/browse/FLINK-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354893#comment-17354893
]
Ingo Bürk commented on FLINK-22737:
-----------------------------------
I would really like avoiding going back to BIGINT. This puts an even bigger
burden on the user to always explicitly convert to an (appropriate) timestamp
type first, and it doesn't really address the question of "MIN_VALUE vs NULL",
it just changes the type with which this is returned. If we expect users to
just convert it to a timestamp, which I think they will do, they'll also end up
with the same timestamp, and nothing is really gained.
> 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)
