[ 
https://issues.apache.org/jira/browse/FLINK-22737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354361#comment-17354361
 ] 

Jark Wu commented on FLINK-22737:
---------------------------------

I thought it wrong. I agree with [~qingru zhang]. The three-valued logic will 
confuse users when using condition {{rowtime >= CURRENT_WATERMARK}}, e.g. use 
it to filter out late data. 

> 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)

Reply via email to