[
https://issues.apache.org/jira/browse/FLINK-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950712#comment-15950712
]
Fabian Hueske commented on FLINK-6228:
--------------------------------------
Hi, [~sunjincheng121],
Thanks for opening the JIRA and working on this issue.
I think we need an explicit and mandatory {{orderBy}} because it will be
required for batch queries.
Thanks, Fabian
> Integrating the OVER windows in the Table API
> ---------------------------------------------
>
> Key: FLINK-6228
> URL: https://issues.apache.org/jira/browse/FLINK-6228
> Project: Flink
> Issue Type: Sub-task
> Components: Table API & SQL
> Reporter: sunjincheng
> Assignee: sunjincheng
>
> Syntax:
> {code}
> table
> .overWindows(
> (Rows|Range [ partitionBy value_expression , ... [ n ]]
> (preceding
> UNBOUNDED|value_specification.(rows|milli|second|minute|hour|day|month|year)|CURRENTROW)
> [following
> UNBOUNDED|value_specification.(rows|milli|second|minute|hour|day|month|year)|CURRENTROW]
> as alias,...[n])
> )
> .select( [col1,...[n]], (agg(col1) OVER overWindowAlias, … [n])
> {code}
> Implement restrictions:
> ** All OVER clauses in the same SELECT clause must be exactly the same.
> ** The PARTITION BY clause is optional (no partitioning results in single
> threaded execution).
> ** The ORDER BY clause is hidden in tableApi, According to time
> characteristic automatic identification.
> ** FOLLOWING is not supported.
> I will soon add a user interface design document.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
