[
https://issues.apache.org/jira/browse/FLINK-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985057#comment-14985057
]
ASF GitHub Bot commented on FLINK-2797:
---------------------------------------
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/1214#issuecomment-152989560
It's fine to have separate code for detached and blocking submission where
necessary. I was more concerned with this pull request that it introduces new
code branches which distort the existing submission logic. Wherever possible we
should try to be explicit about the submission code path we're in instead of
mixing them all together.
For instance, you're setting `lastEnv´ on blocking execution but then you
never access it during blocking execution. This is not a clear code style.
> CLI: Missing option to submit jobs in detached mode
> ---------------------------------------------------
>
> Key: FLINK-2797
> URL: https://issues.apache.org/jira/browse/FLINK-2797
> Project: Flink
> Issue Type: Bug
> Components: Command-line client
> Affects Versions: 0.9, 0.10
> Reporter: Maximilian Michels
> Assignee: Sachin Goel
> Fix For: 0.10
>
>
> Jobs can only be submitted in detached mode using YARN but not on a
> standalone installation. This has been requested by users who want to submit
> a job, get the job id, and later query its status.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
