You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2016/02/27 00:13:18 UTC

[jira] [Resolved] (FLINK-3521) Make Iterable part of method signature for WindowFunction

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

Robert Metzger resolved FLINK-3521.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

Resolved in http://git-wip-us.apache.org/repos/asf/flink/commit/27b5c49e

> Make Iterable part of method signature for WindowFunction
> ---------------------------------------------------------
>
>                 Key: FLINK-3521
>                 URL: https://issues.apache.org/jira/browse/FLINK-3521
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Blocker
>             Fix For: 1.0.0
>
>
> After discussion with [~StephanEwen],[~rmetzger], [~fhueske] it was decided that the signature of WindowFunction should be changed.
> Right now, the signature is {{WindowFunction<IN, OUT, KEY, WINDOW>}}. With the decision of whether the input is an {{Iterable}} nor not residing in the signature of the method on {{WindowedStream}}, for example:
>  - {{WindowedStream.apply(WindowFunction<Iterable<IN>>, OUT, KEY, WINDOW>}}
>  - {{WindowedStream.apply(ReduceFunction, WindowFunction<IN, OUT, KEY, WINDOW>}}
> The {{Iterable<>}} should be moved into the signature of the {{apply}} method, so that it is:
> {{void apply(KEY key, W window, Iterable<IN> input, Collector<OUT> out)}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)