flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5985) Flink treats every task as stateful (making topology changes impossible)
Date Wed, 15 Mar 2017 19:43:42 GMT

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

ASF GitHub Bot commented on FLINK-5985:
---------------------------------------

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/3523
  
    Can we slightly adapt the test to target more the typical use case:
      - Original job has some stateless ops (no uid), and some stateful ones (with uid)
      - Create a modified job that has the same stateful ones (same uids) but different stateless
ones
    
    Otherwise this looks good.


> 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)

Mime
View raw message