[
https://issues.apache.org/jira/browse/FLINK-7082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101380#comment-16101380
]
ASF GitHub Bot commented on FLINK-7082:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/4261
You're totally right about the current problem with inheritance when having
multiple dimensions (job vs. session, yarn vs. standalone. vs Mesos). I've
looked at the link you've posted and it looks really interesting. Once we have
ditched Java 7 support, we can change the code to use this technique in order
to reduce code duplication.
> Flip-6: Generic entry point for Flink sessions
> ----------------------------------------------
>
> Key: FLINK-7082
> URL: https://issues.apache.org/jira/browse/FLINK-7082
> Project: Flink
> Issue Type: Bug
> Components: Cluster Management
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Labels: flip-6
>
> Implement a generic entry point for Flink sessions. This
> {{ClusterEntryPoint}} has to start a {{ResourceManager}}, the {{Dispatcher}}
> component and the cluster's RESTful endpoint. This class could serve as the
> basis for a {{Mesos-}} and {{YarnEntryPoint}} to run Flink sessions.
> Maybe we can use a common base for the session and the per-job mode. The
> session has to start a dispatcher component and the per-job mode retrieves
> the {{JobGraph}} and directly starts a {{JobManager}} with this job.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
