[
https://issues.apache.org/jira/browse/FLINK-7103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091916#comment-16091916
]
ASF GitHub Bot commented on FLINK-7103:
---------------------------------------
Github user EronWright commented on the issue:
https://github.com/apache/flink/pull/4260
My take on this skeleton is that the `Dispatcher` should not use the
`JobManagerRunner` directly. My rationale is:
1. The dispatcher should never execute user code, otherwise it cannot truly
support multi-user scenarios.
2. The runner is a concrete class that acts as a bootstrap for the JM, to
be used in the same process as the JM. But the dispatcher must support remote
JM execution.
> Implement skeletal structure of dispatcher component
> ----------------------------------------------------
>
> Key: FLINK-7103
> URL: https://issues.apache.org/jira/browse/FLINK-7103
> Project: Flink
> Issue Type: Sub-task
> Components: Cluster Management
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Labels: flip-6
> Fix For: 1.4.0
>
>
> Implement the skeletal structure of the {{Dispatcher}} component. The initial
> functionality will support job submissions and listing of jobs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
