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

ASF GitHub Bot commented on FLINK-6584:
---------------------------------------

Github user fhueske commented on a diff in the pull request:

    https://github.com/apache/flink/pull/4199#discussion_r124630671
  
    --- Diff: 
flink-libraries/flink-table/src/main/java/org/apache/calcite/sql/fun/SqlGroupFunction.java
 ---
    @@ -50,7 +50,8 @@
      * GROUP BY HOP(rowtime, INTERVAL '1' HOUR), productId
      * </pre></blockquote>
      */
    -class SqlGroupFunction extends SqlFunction {
    +// FLINK QUICK FIX
    +public class SqlGroupFunction extends SqlFunction {
    --- End diff --
    
    Calcite 1.13 was released and we are planning to update the dependency. 
    I guess we cannot simply drop this file and use Calcite's version, if we 
start modifying the code. 
    
    Do we have plans to contribute the changes back or do we want to keep this 
file?


> Support multiple consecutive windows in SQL
> -------------------------------------------
>
>                 Key: FLINK-6584
>                 URL: https://issues.apache.org/jira/browse/FLINK-6584
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table API & SQL
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>
> Right now, the Table API supports multiple consecutive windows as follows:
> {code}
> val table = stream.toTable(tEnv, 'rowtime.rowtime, 'int, 'double, 'float, 
> 'bigdec, 'string)
> val t = table
>   .window(Tumble over 2.millis on 'rowtime as 'w)
>   .groupBy('w)
>   .select('w.rowtime as 'rowtime, 'int.count as 'int)
>   .window(Tumble over 4.millis on 'rowtime as 'w2)
>   .groupBy('w2)
>   .select('w2.rowtime, 'w2.end, 'int.count)
> {code}
> Similar behavior should be supported by the SQL API as well. We need to 
> introduce a new auxiliary group function, but this should happen in sync with 
> Apache Calcite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to