[ 
https://issues.apache.org/jira/browse/FLINK-4016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318226#comment-15318226
 ] 

RWenden commented on FLINK-4016:
--------------------------------

Isn't it a better idea to close Jira 3977 and re-open 4016 ?


On Tue, Jun 7, 2016 at 10:54 AM, ASF GitHub Bot (JIRA) <j...@apache.org>



> FoldApplyWindowFunction is not properly initialized
> ---------------------------------------------------
>
>                 Key: FLINK-4016
>                 URL: https://issues.apache.org/jira/browse/FLINK-4016
>             Project: Flink
>          Issue Type: Bug
>          Components: DataStream API
>    Affects Versions: 1.0.3
>            Reporter: RWenden
>            Priority: Blocker
>              Labels: easyfix
>             Fix For: 1.1.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> FoldApplyWindowFunction's outputtype is not set.
> We're using constructions like (excerpt):
>       .keyBy(0)
>       .countWindow(10, 5)
>       .fold(...)
> Running this stream gives an runtime exception in FoldApplyWindowFunction:
> "No initial value was serialized for the fold window function. Probably the 
> setOutputType method was not called."
> This can be easily fixed in WindowedStream.java by (around line# 449):
>             FoldApplyWindowFunction foldApplyWindowFunction = new 
> FoldApplyWindowFunction<>(initialValue, foldFunction, function);
>             foldApplyWindowFunction.setOutputType(resultType, 
> input.getExecutionConfig());
>             operator = new EvictingWindowOperator<>(windowAssigner,
>                     
> windowAssigner.getWindowSerializer(getExecutionEnvironment().getConfig()),
>                     keySel,
>                     
> input.getKeyType().createSerializer(getExecutionEnvironment().getConfig()),
>                     stateDesc,
>                     new 
> InternalIterableWindowFunction<>(foldApplyWindowFunction),
>                     trigger,
>                     evictor);



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

Reply via email to