[
https://issues.apache.org/jira/browse/FLINK-6159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936644#comment-15936644
]
Stephan Ewen commented on FLINK-6159:
-------------------------------------
As Robert mentioned, the original plan was to have two things:
(1) YarnExecutionEnvironment (and YarnSessionEnvironment) which can be used
to launch a job as an individual per-job-cluster (or a shared cluster)
(2) The call to env.execute() returns a {{JobControl}} object with which you
can interact with the job. Internally, this uses the {{ClusterClient}} and
{{JobClient}} to talk with the cluster/job.
> Add Java/Scala FlinkLauncher
> ----------------------------
>
> Key: FLINK-6159
> URL: https://issues.apache.org/jira/browse/FLINK-6159
> Project: Flink
> Issue Type: Improvement
> Components: Client
> Reporter: CanBin Zheng
> Labels: features
>
> Now we can use flink.sh or yarn-session.sh to submit Jobs/Applications. I
> think it's quite convenient and helpful to have pure java/scala FlinkLauncher
> for users to submit jobs/applications without any dependency of these shell
> scripts. We can do this just like MapReduce used to.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
