Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Mon, 6 Mar 2017 08:17:32 +0000 (UTC)
From: "radu (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.13038118.1485438213000.4372.1488788252974@Atlassian.JIRA>
In-Reply-To: <JIRA.13038118.1485438213000@Atlassian.JIRA>
References: <JIRA.13038118.1485438213000@Atlassian.JIRA> <JIRA.13038118.1485438213527@jira-lw-us.apache.org>
Subject: [jira] [Commented] (FLINK-5654) Add processing time OVER RANGE
 BETWEEN x PRECEDING aggregation to SQL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 06 Mar 2017 08:17:37 -0000


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

radu commented on FLINK-5654:
-----------------------------

@shijinkui - thanks for the comment
I keeped description because all other sql operator implementation have it. It was more for uniformity. Additionally, if at some point we decide to go for compiling functions instead of working directly against the datastream API, than this is typically used for naming. Because of these I propose to keep it.

> Add processing time OVER RANGE BETWEEN x PRECEDING aggregation to SQL
> ---------------------------------------------------------------------
>
>                 Key: FLINK-5654
>                 URL: https://issues.apache.org/jira/browse/FLINK-5654
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table API & SQL
>            Reporter: Fabian Hueske
>            Assignee: radu
>
> The goal of this issue is to add support for OVER RANGE aggregations on processing time streams to the SQL interface.
> Queries similar to the following should be supported:
> {code}
> SELECT 
>   a, 
>   SUM(b) OVER (PARTITION BY c ORDER BY procTime() RANGE BETWEEN INTERVAL '1' HOUR PRECEDING AND CURRENT ROW) AS sumB,
>   MIN(b) OVER (PARTITION BY c ORDER BY procTime() RANGE BETWEEN INTERVAL '1' HOUR PRECEDING AND CURRENT ROW) AS minB
> FROM myStream
> {code}
> The following restrictions should initially apply:
> - 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 may only have procTime() as parameter. procTime() is a parameterless scalar function that just indicates processing time mode.
> - UNBOUNDED PRECEDING is not supported (see FLINK-5657)
> - FOLLOWING is not supported.
> The restrictions will be resolved in follow up issues. If we find that some of the restrictions are trivial to address, we can add the functionality in this issue as well.
> This issue includes:
> - Design of the DataStream operator to compute OVER ROW aggregates
> - Translation from Calcite's RelNode representation (LogicalProject with RexOver expression).


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