Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Implemented
    • 0.9
    • 0.10.0
    • Runtime / Coordination
    • None

    Description

      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

      Attachments

        Issue Links

          Activity

            People

              mxm Maximilian Michels
              sewen Stephan Ewen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: