[
https://issues.apache.org/jira/browse/FLINK-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736574#comment-14736574
]
ASF GitHub Bot commented on FLINK-2097:
---------------------------------------
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/858#issuecomment-138860661
Thanks Max for the detailed description.
On Wed, Sep 9, 2015 at 11:12 AM, Max <[email protected]> wrote:
> Of course! The following classes have been refactored in the course of
> integrating them with the session management:
>
> *Client*
>
> - Establish connection to JobManager on creation
> - Refactor run method into runBlocking and runDetached
> - Extract helper classes to generate the Plan
> - Make Optimizer and JobGraph generation methods static
> - Pass ClassLoader correctly (do not keep one per Client but rather
> let it be passed before submission)
>
> *CliFrontend*
>
> - runBlocking and runDetached methods by analogy with the Client class
>
> *ExecutionEnvironment*, *LocalEnvironment*, *RemoteEnvironment*
>
> - modified abstract class to support sessions (timeout and jobID
> generation)
> - handle session management via Reapers and ShutdownHooks
>
> *PlanExecutor*, *LocalExecutor*, *RemoteExecutor*
>
> - modified interface
> - support session termination
> - set JobID on Plan
>
> *JobManager*
>
> - keep ExecutionGraph as long as session has not expired
>
> Future issues:
>
> - Support for sessions in streaming. Currently streaming jobs are
> agnostic of sessions.
> - Representation of sessions in the JobManager web frontend. How do we
> represent updates to the ExecutionGraph in sessions?
> - Build features on top of session management (e.g. intermediate
> results)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/flink/pull/858#issuecomment-138848287>.
>
> 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)
