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

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

Github user huawei-flink commented on a diff in the pull request:

    https://github.com/apache/flink/pull/3459#discussion_r104366556
  
    --- Diff: 
flink-libraries/flink-table/src/main/java/org/apache/flink/table/plan/nodes/datastream/DataStreamProcTimeTimeAggregate.java
 ---
    @@ -0,0 +1,162 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one
    + * or more contributor license agreements.  See the NOTICE file
    + * distributed with this work for additional information
    + * regarding copyright ownership.  The ASF licenses this file
    + * to you under the Apache License, Version 2.0 (the
    + * "License"); you may not use this file except in compliance
    + * with the License.  You may obtain a copy of the License at
    + *
    + *     http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +
    +package org.apache.flink.table.plan.nodes.datastream;
    +
    +import java.util.ArrayList;
    +import java.util.List;
    +
    +import org.apache.calcite.plan.RelOptCluster;
    +import org.apache.calcite.plan.RelTraitSet;
    +import org.apache.calcite.rel.RelNode;
    +import org.apache.calcite.rel.logical.LogicalWindow;
    +import org.apache.calcite.rel.type.RelDataType;
    +import org.apache.calcite.rel.type.RelDataTypeField;
    +import org.apache.flink.api.common.typeinfo.TypeInformation;
    +import org.apache.flink.api.java.typeutils.RowTypeInfo;
    +import org.apache.flink.streaming.api.datastream.DataStream;
    +import 
org.apache.flink.streaming.api.functions.AssignerWithPeriodicWatermarks;
    +import org.apache.flink.streaming.api.watermark.Watermark;
    +import org.apache.flink.streaming.api.windowing.assigners.GlobalWindows;
    +import org.apache.flink.streaming.api.windowing.evictors.TimeEvictor;
    +import org.apache.flink.streaming.api.windowing.time.Time;
    +import org.apache.flink.streaming.api.windowing.triggers.CountTrigger;
    +import org.apache.flink.table.api.StreamTableEnvironment;
    +import org.apache.flink.table.api.TableConfig;
    +import org.apache.flink.table.calcite.FlinkTypeFactory;
    +import org.apache.flink.table.plan.logical.rel.util.WindowAggregateUtil;
    +import org.apache.flink.table.plan.nodes.datastream.DataStreamRel;
    +import 
org.apache.flink.table.plan.nodes.datastream.function.DataStreamProcTimeAggregateGlobalWindowFunction;
    +import 
org.apache.flink.table.plan.nodes.datastream.function.DataStreamProcTimeAggregateWindowFunction;
    +import org.apache.flink.types.Row;
    +
    +public class DataStreamProcTimeTimeAggregate extends DataStreamRelJava {
    +
    +   private LogicalWindow windowReference;
    +   private String description;
    --- End diff --
    
    @shijinkui - thanks for the comment
     I kept 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)

Reply via email to