You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2017/01/26 13:44:24 UTC
[jira] [Created] (FLINK-5654) Add processing time OVER RANGE
BETWEEN x PRECEDING aggregation to SQL
Fabian Hueske created FLINK-5654:
------------------------------------
Summary: 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
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
- 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.4#6332)
Re: [jira] [Created] (FLINK-5654) Add processing time OVER RANGE
BETWEEN x PRECEDING aggregation to SQL
Posted by Fabian Hueske <fa...@data-artisans.com>.
Hi Radu,
can you reply to my mail on the discussion thread and tell me you JIRA user
name?
I'll give you contributor permissions then.
Thanks, Fabian
On Thu, Jan 26, 2017 at 2:51 PM, Radu Tudoran <ra...@huawei.com>
wrote:
> Hi,
>
> Can you assign please the jira issue to me. I already can start
> integrating the implementation that for this.
>
>
> -----Original Message-----
> From: Fabian Hueske (JIRA) [mailto:jira@apache.org]
> Sent: Thursday, January 26, 2017 2:44 PM
> To: dev@flink.apache.org
> Subject: [jira] [Created] (FLINK-5654) Add processing time OVER RANGE
> BETWEEN x PRECEDING aggregation to SQL
>
> Fabian Hueske created FLINK-5654:
> ------------------------------------
>
> Summary: 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
>
>
> 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
> - 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.4#6332)
>
--
----
Data Artisans GmbH | Stresemannstraße 121a | 10963 Berlin
info@data-artisans.com
+49-(0)30-55599146
Registered at Amtsgericht Charlottenburg - HRB 158244 B
Managing Directors: Kostas Tzoumas, Stephan Ewen
RE: [jira] [Created] (FLINK-5654) Add processing time OVER RANGE
BETWEEN x PRECEDING aggregation to SQL
Posted by Radu Tudoran <ra...@huawei.com>.
Hi,
Can you assign please the jira issue to me. I already can start integrating the implementation that for this.
-----Original Message-----
From: Fabian Hueske (JIRA) [mailto:jira@apache.org]
Sent: Thursday, January 26, 2017 2:44 PM
To: dev@flink.apache.org
Subject: [jira] [Created] (FLINK-5654) Add processing time OVER RANGE BETWEEN x PRECEDING aggregation to SQL
Fabian Hueske created FLINK-5654:
------------------------------------
Summary: 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
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
- 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.4#6332)