[
https://issues.apache.org/jira/browse/FLINK-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17353228#comment-17353228
]
Timo Walther commented on FLINK-22737:
--------------------------------------
Small correction: The alternative would be to return BIGINT, so users would
need to call another function to convert it to the target timestamp type.
TIMESTAMP_LTZ fits better to CURRENT_TIMESTAMP, CURRENT_ROW_TIMESTAMP and
PROCTIME. Also LTZ is the recommended event-time timestamp type that we
recommend to users. If we would go with BIGINT, it would actually be better to
let `SOURCE_WATERMARK()` also return BIGINT for consistency.
> 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)
