[jira] [Updated] (FLINK-5914) remove aggregateResultType from streaming.api.datastream.aggregate

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-5914:
----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned  (was: auto-deprioritized-major auto-unassigned stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> remove aggregateResultType from streaming.api.datastream.aggregate
> ------------------------------------------------------------------
>
>                 Key: FLINK-5914
>                 URL: https://issues.apache.org/jira/browse/FLINK-5914
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>            Reporter: Shaoxuan Wang
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, auto-unassigned
>
> aggregateResultType does not seem necessary for streaming.api.datastream.aggregate. We will anyway not serialize the aggregateResult between aggregate and window function. Aggregate function itself provides a function to getResult(), window function here should just emit the same results as aggregate output. So aggregateResultType should be same as resultType. I think we can safely remove aggregateResultType, thereby user will not have to provide two same types for the streaming.api.datastream.aggregate.  
>  [~StephanEwen], what do you think?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)