[
https://issues.apache.org/jira/browse/FLINK-19449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294063#comment-17294063
]
Benchao Li commented on FLINK-19449:
------------------------------------
[~laiyijie] Thanks for your comment, please use English in Jira issues.
And for your comment, yes, your observation is correct. For now, lead/lag is
only correctly implemented in Batch SQL, and they are special from other
aggregate functions. In Streaming SQL, I think we can support LAG firstly, and
throw Exception for LEAD.
> LEAD/LAG cannot work correctly in streaming mode
> ------------------------------------------------
>
> Key: FLINK-19449
> URL: https://issues.apache.org/jira/browse/FLINK-19449
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API, Table SQL / Runtime
> Affects Versions: 1.10.2, 1.11.2
> Reporter: Benchao Li
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
