You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/07 17:40:20 UTC
[jira] [Commented] (FLINK-3869) WindowedStream.apply with
FoldFunction is too restrictive
[ https://issues.apache.org/jira/browse/FLINK-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318972#comment-15318972 ]
ASF GitHub Bot commented on FLINK-3869:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/1973
I think the API breaking changes preventer will reject this.
It is all public methods, and the signature changes (implicit parameters and context bounds are parameters in the bytecode)
> WindowedStream.apply with FoldFunction is too restrictive
> ---------------------------------------------------------
>
> Key: FLINK-3869
> URL: https://issues.apache.org/jira/browse/FLINK-3869
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
>
> Right now we have this signature:
> {code}
> public <R> SingleOutputStreamOperator<R> apply(R initialValue, FoldFunction<T, R> foldFunction, WindowFunction<R, R, K, W> function) {
> {code}
> but we should have this signature to allow users to return a type other than the fold accumulator type from their window function:
> {code}
> public <ACC, R> SingleOutputStreamOperator<R> apply(ACC initialValue, FoldFunction<T, ACC> foldFunction, WindowFunction<ACC, R, K, W> function) {
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)