[
https://issues.apache.org/jira/browse/FLINK-8689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16445864#comment-16445864
]
ASF GitHub Bot commented on FLINK-8689:
---------------------------------------
Github user walterddr commented on the issue:
https://github.com/apache/flink/pull/5555
Thanks @fhueske, I had the exact same feeling. Just attaching `MapState`
towards the back of the `Row` might be a current working solution for now, but
will probably be nasty to maintain in the future.
I am planning to go ahead and create an optimization ticket further down
once I had FLINK-8690 completed. What do you think?
> 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)
