You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:08:12 UTC
[jira] [Commented] (BEAM-8243) Document behavior of FlinkRunner
[ https://issues.apache.org/jira/browse/BEAM-8243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174647#comment-17174647 ]
Beam JIRA Bot commented on BEAM-8243:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> Document behavior of FlinkRunner
> --------------------------------
>
> Key: BEAM-8243
> URL: https://issues.apache.org/jira/browse/BEAM-8243
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink, website
> Reporter: Kyle Weaver
> Priority: P2
> Labels: portability-flink, stale-P2
>
> The Flink runner guide should include a couple details
> 1) FlinkRunner pulls the job server jar from Maven by default (need to make this explicit in case of firewall concerns)
> 2) how to override in case the above is a problem
--
This message was sent by Atlassian Jira
(v8.3.4#803005)