[
https://issues.apache.org/jira/browse/FLINK-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987370#comment-15987370
]
ASF GitHub Bot commented on FLINK-6388:
---------------------------------------
Github user rtudoran commented on the issue:
https://github.com/apache/flink/pull/3783
@fhueske @stefanobortoli
Regarding the options for solving the distinct. From my point of view the
previous approach worked:
- we keep in the processFunctions a state for each field that is used in a
distinct aggregator
- we count the occurrence of each value (meant for a distinct aggregate)
that we observed
- when a value is seen for the first time we accumulate it
- when a value is retracted we decrease the corresponding count.
-if count is 0 we retract the value from accumulator
Based on how things are implemented now - this would involved to have a
separate list of aggregatefunctions for the distinct. In order to be able to
control when to accumulate to these values.
What do you think? Do you see any disadvantage to this?
> Add support for DISTINCT into Code Generated Aggregations
> ---------------------------------------------------------
>
> Key: FLINK-6388
> URL: https://issues.apache.org/jira/browse/FLINK-6388
> Project: Flink
> Issue Type: Sub-task
> Components: DataStream API
> Affects Versions: 1.3.0
> Reporter: Stefano Bortoli
> Assignee: Stefano Bortoli
> Fix For: 1.3.0
>
>
> We should support DISTINCT in Code Generated aggrgation functions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
