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-2097) Add support for JobSessions
Date Wed, 22 Jul 2015 15:19:05 GMT

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

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

Github user mxm commented on the pull request:

    https://github.com/apache/flink/pull/858#issuecomment-123755792
  
    It should just add more nodes to the ExecutionGraph. Existing ones should not be modified.
For batch, I think the assumption is that it needs to be finished. For streaming, I could
also picture attaching nodes at runtime but this has to be carefully implemented..


> Add support for JobSessions
> ---------------------------
>
>                 Key: FLINK-2097
>                 URL: https://issues.apache.org/jira/browse/FLINK-2097
>             Project: Flink
>          Issue Type: Sub-task
>          Components: JobManager
>    Affects Versions: 0.9
>            Reporter: Stephan Ewen
>            Assignee: Maximilian Michels
>             Fix For: 0.9
>
>
> Sessions make sure that the JobManager does not immediately discard a JobGraph after
execution, but keeps it around for further operations to be attached to the graph. By keeping
the JobGraph around, the cached streams (intermediate data) are also kept,
> That is the way of realizing interactive sessions on top of a streaming dataflow abstraction.
> ExecutionGraphs should be kept as long as
> - no timeout occurred or
> - the session has not been explicitly ended



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

Mime
View raw message