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

ASF GitHub Bot commented on BEAM-2006:
--------------------------------------

GitHub user XuMingmin opened a pull request:

    https://github.com/apache/beam/pull/2903

    [BEAM-2006] window support 

    Add support for aggregation: global, `HOP`, `TUMBLE`, `SESSION`, only 
aggregation function `COUNT`
    
    Some other changes:
    1. upgrade to Apache Calcite 1.12.0;
    2. support data type TIMESTAMP, TIME;


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/XuMingmin/beam BEAM-2006

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam/pull/2903.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2903
    
----
commit 7f487cac6ef1991bbfca6f6d00d536d09321056e
Author: mingmxu <[email protected]>
Date:   2017-05-04T21:43:36Z

    Add support for aggregation: global, `HOP`, `TUMBLE`, `SESSION`, only 
aggregation function `COUNT`
    Some other changes:
    1. upgrade to Apache Calcite 1.12.0;
    2. support data type TIMESTAMP, TIME;
    
    minor fix of `accept` validation.
    
    fix window info in project

----


> window support 
> ---------------
>
>                 Key: BEAM-2006
>                 URL: https://issues.apache.org/jira/browse/BEAM-2006
>             Project: Beam
>          Issue Type: New Feature
>          Components: dsl-sql
>            Reporter: Xu Mingmin
>            Assignee: Xu Mingmin
>            Priority: Blocker
>
> There're several methods, TUMBLE/HOP/SESSION, introduced in Calcite 1.12, 
> which represent a window-aggregation operation. 
> In BeamSQL, it's expected to leverage these methods to determine window 
> function, set trigger strategy, also handle event_time/watermark properly. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to