[
https://issues.apache.org/jira/browse/FLINK-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956964#comment-15956964
]
sunjincheng edited comment on FLINK-6228 at 4/5/17 2:47 PM:
------------------------------------------------------------
Yes, Your right In SQL we should be consistent with the standard SQL semantics,
I also think in SQL we only support over with {{OverWindow}} just like current
master code. About {{OverWindow}} with {{groupBy}} , it's a little confused.
Current tableAPI SlideWindow defined both
window size and trigger frequency, e.g.: {{Slide over 2.rows every 1.rows }},So
{{over}} with {{sideWindow}} dose not make sense at current time(If we want do
that we must do some changes).But how can we using overWindow expression
{{Tumble over 5.rows }} ?
was (Author: sunjincheng121):
Yes, Your right In SQL we should be consistent with the standard SQL semantics,
I also think in SQL we only support over with {{OverWindow}} just like current
master code. About {{OverWindow}} with {{groupBy}} , it's a little confused.
Current tableAPI SlideWindow defined both
window size and trigger frequency, e.g.: {{Slide over 2.rows every 1.rows }},So
{{over}} with {{sideWindow}} dose not make sense at current time.But how can we
using overWindow expression {{Tumble over 5.rows }} ?
> 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 ]] [ orderBy
> order_by_expression]
> (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 Before the
> [FLINK-5884|https://issues.apache.org/jira/browse/FLINK-5884] implementation
> orderBy may only have ‘rowtime/’proctime(for stream)/‘specific-time-field(for
> batch).
> * FOLLOWING is not supported.
> I will soon add a user interface design document.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
