[jira] [Commented] (FLINK-2097) Add support for JobSessions

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

Github user mxm commented on the pull request:

    https://github.com/apache/flink/pull/858#issuecomment-138625172
  
    I've ported this pull request to the latest master. It was a lot more work than I anticipated because some classes had diverged significantly and merging them was a bit hard.
    
    Due to some refactoring, the changes have grown quite large again and I know that makes reviewing hard. Despite that, I wouldn't delay merging this pull request much further. We can disable the session management until it is integrated with the rest of the system (intermediate results) by throwing an exception on the interface methods. If we decide later, that we want to delay this feature, we could also remove the session code. In that case, it would still make sense to merge this pull request because it contains a lot of nice refactoring.
    
    With the session management in place, we can reuse already computed intermediate results with not too much effort. Actually, only some API changes are remaining to expose the session management to the user in production.


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