[
https://issues.apache.org/jira/browse/FLINK-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972486#comment-15972486
]
Fabian Hueske commented on FLINK-6250:
--------------------------------------
Sorry for the inconvenience [~stefano.bortoli]. Code generation is required to
bring the interface of the user-defined aggregates in the final shape for the
1.3 release (e.g., to allow multiple input values).
I'm not sure if we should work around the missing support for `DISTINCT`
aggregates in Calcite by adding a non-standard compliant behavior that would
need to be removed afterwards (breaking existing queries that use the feature).
Calling a method `DIST()` on an aggregation function usually means to compute
the aggregate and apply the function on its result.
Did you check at which level, Calcite is missing support for DISTINCT? Is it
already in the parser or later in the validator?
> Distinct procTime with Rows boundaries
> --------------------------------------
>
> Key: FLINK-6250
> URL: https://issues.apache.org/jira/browse/FLINK-6250
> Project: Flink
> Issue Type: Sub-task
> Components: Table API & SQL
> Reporter: radu
> Assignee: Stefano Bortoli
>
> Support proctime with rows boundaries
> Q1.1. `SELECT SUM( DISTINCT b) OVER (ORDER BY procTime() ROWS BETWEEN 2
> PRECEDING AND CURRENT ROW) FROM stream1`
> Q1.1. `SELECT COUNT(b), SUM( DISTINCT b) OVER (ORDER BY procTime() ROWS
> BETWEEN 2 PRECEDING AND CURRENT ROW) FROM stream1`
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
