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

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

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

    https://github.com/apache/flink/pull/5555#discussion_r170604304
  
    --- Diff: 
flink-libraries/flink-table/src/main/scala/org/apache/flink/table/runtime/aggregate/AggregateUtil.scala
 ---
    @@ -1393,6 +1393,21 @@ object AggregateUtil {
                 throw new TableException(s"unsupported Function: 
'${unSupported.getName}'")
             }
           }
    +
    +      // create distinct accumulator delegate
    +      if (aggregateCall.isDistinct) {
    --- End diff --
    
    Good point. Actually there's a very interesting question I've been thinking 
- This AggFunction literally is the distinct version of the  
`CollectAggFunction`, however it cannot exist by itself unless chained with 
other `realAgg` functions --> this means we will need to chain 
`DistinctAggFunction` with `CollectAggFunction` which just dont make sense. I 
will try some other approach and see if they work.


> Add runtime support of distinct filter using MapView 
> -----------------------------------------------------
>
>                 Key: FLINK-8689
>                 URL: https://issues.apache.org/jira/browse/FLINK-8689
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Rong Rong
>            Assignee: Rong Rong
>            Priority: Major
>
> This ticket should cover distinct aggregate function support to codegen for 
> *AggregateCall*, where *isDistinct* fields is set to true.
> This can be verified using the following SQL, which is not currently 
> producing correct results.
> {code:java}
> SELECT
>   a,
>   SUM(b) OVER (PARTITION BY a ORDER BY proctime ROWS BETWEEN 5 PRECEDING AND 
> CURRENT ROW)
> FROM
>   MyTable{code}
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to