[
https://issues.apache.org/jira/browse/BEAM-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132446#comment-17132446
]
Beam JIRA Bot commented on BEAM-1631:
-------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Flink runner: submit job to a Flink-on-YARN cluster
> ---------------------------------------------------
>
> Key: BEAM-1631
> URL: https://issues.apache.org/jira/browse/BEAM-1631
> Project: Beam
> Issue Type: New Feature
> Components: runner-flink
> Reporter: Davor Bonaci
> Assignee: Aljoscha Krettek
> Priority: P2
> Labels: stale-assigned
>
> As far as I understand, running Beam pipelines on a Flink cluster can be done
> in two ways:
> * Run directly with a Flink runner, and specifying {{--flinkMaster}} pipeline
> option via, say, {{mvn exec}}.
> * Produce a bundled JAR, and use {{bin/flink}} to submit the same pipeline.
> These two ways are equivalent, and work well on a standalone Flink cluster.
> Submitting to a Flink-on-YARN is more complicated. You can still produce a
> bundled JAR, and use {{bin/flink -yid <applicationid>}} to submit such a job.
> However, that seems impossible with a Flink runner directly.
> If so, we should add the ability to the Flink runner to submit a job to a
> Flink-on-YARN cluster directly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
