[
https://issues.apache.org/jira/browse/BEAM-8372?focusedWorklogId=334357&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-334357
]
ASF GitHub Bot logged work on BEAM-8372:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Oct/19 20:38
Start Date: 25/Oct/19 20:38
Worklog Time Spent: 10m
Work Description: mxm commented on issue #9844: [BEAM-8372] Support both
flink_master and flink_master_url parameter
URL: https://github.com/apache/beam/pull/9844#issuecomment-546504944
>`flink_master_url` is very new, I think we can consolidate on one option
for now.
The instance in `FlinkJobServerDriver` has been there for over a year. It
might be sufficient to convert it to an alias only there.
>I think it would be good to get this resolved in the current release, if
possible.
+1
>So, if I understand correctly, if `flink_master` is just host:port, there
is no way to (simultaneously) submit a job to two different clusters (one with
ssl, one without) without editing the config file in the middle? This seems
quite unfortunate. Also, the code here does not read the config file.
The `FlinkJobServerDriver` reads the config file before it submits the Flink
job to the cluster. So the Python code does not have to worry about it. Yes,
there is no way to submit against two clusters without changing the
configuration file. You can start a second job server though, which uses a
different configuration file.
>What if, instead, we made the `http[s]://` part optional, where it would be
stripped in Java and assumed to be just `http://` in Python if not specified?
(Or it could try https and then fall back to http on failure.)
That would be a new feature. Flink does not accept any url schemas like
`http://`. It just expects host:port. The config file determines whether the
Rest service running at the port uses SSL or not.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 334357)
Time Spent: 6h 40m (was: 6.5h)
> Allow submission of Flink UberJar directly to flink cluster.
> ------------------------------------------------------------
>
> Key: BEAM-8372
> URL: https://issues.apache.org/jira/browse/BEAM-8372
> Project: Beam
> Issue Type: New Feature
> Components: sdk-py-core
> Reporter: Robert Bradshaw
> Assignee: Robert Bradshaw
> Priority: Major
> Time Spent: 6h 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
