[
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-unassigned stale-major (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: auto-unassigned, stale-major
>
> 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.3.4#803005)
