[ 
https://issues.apache.org/jira/browse/BEAM-9213?focusedWorklogId=382858&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-382858
 ]

ASF GitHub Bot logged work on BEAM-9213:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Feb/20 12:27
            Start Date: 06/Feb/20 12:27
    Worklog Time Spent: 10m 
      Work Description: kamilwu commented on issue #10708: [BEAM-9213] throw 
error when flink_submit_uber_jar and not flink_master
URL: https://github.com/apache/beam/pull/10708#issuecomment-582883307
 
 
   Just to let you know that we've just introduced Python autoformatter. Your 
merge conflict might be a result of this.
   Here you can find an instruction on how to run autoformatter: 
https://cwiki.apache.org/confluence/display/BEAM/Python+Tips, section 
Formatting.
   Sorry for inconvenience.
 
----------------------------------------------------------------
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: 382858)
    Time Spent: 1h 50m  (was: 1h 40m)

> FlinkRunner ignores --flink_submit_uber_jar when master unset
> -------------------------------------------------------------
>
>                 Key: BEAM-9213
>                 URL: https://issues.apache.org/jira/browse/BEAM-9213
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-flink
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: Minor
>              Labels: portability-flink
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Instead, an error should be thrown to let the user know that 
> flink_submit_uber_jar is incompatible with auto/local master.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to