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

Stefan Richter commented on FLINK-5985:
---------------------------------------

I think the proper solution is based on preventing those empty files from being 
written, but there must be some differentiation between stateless tasks and 
stateful tasks with (currently) empty state. For the later ones, the empty 
state indicates restores which is an exposed signal for user code.

> Flink treats every task as stateful (making topology changes impossible)
> ------------------------------------------------------------------------
>
>                 Key: FLINK-5985
>                 URL: https://issues.apache.org/jira/browse/FLINK-5985
>             Project: Flink
>          Issue Type: Bug
>          Components: State Backends, Checkpointing
>    Affects Versions: 1.2.0
>            Reporter: Gyula Fora
>            Priority: Critical
>
> It seems  that Flink treats every Task as stateful so changing the topology 
> is not possible without setting uid on every single operator.
> If the topology has an iteration this is virtually impossible (or at least 
> gets super hacky)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to