[
https://issues.apache.org/jira/browse/FLINK-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972574#comment-15972574
]
Stefano Bortoli commented on FLINK-6250:
----------------------------------------
Hi [~fhueske],
we are working with Calcite to bring in the support to DISTINCT. I think that
[~rtudoran] implemented a first version and we are under core review. Still,
the time to get that support through Calcite is far away (release, + inclusion
in Flink).
I agree with you that it is not optimal, but at least we are moving ahead. I
will push the branch without the code generation. Then you can have a look at
the implementation. We keep it for when DISTINCT is officially supported then.
Code generation aggregation interfaces do no include specific parameters for
distinct aggregation and retraction, thus those will have to be reworked
anyway. Should I open a JIRA for those?
> 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)
