[
https://issues.apache.org/jira/browse/FLINK-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950540#comment-14950540
]
ASF GitHub Bot commented on FLINK-2797:
---------------------------------------
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/1214#issuecomment-146899718
OK....now I'm confused. This PR was all about disallowing "multiple round
trips" and that's what Sachin tried to solve. Failing all interactive programs
detached is a quick solution because solving the "multiple round trips" problem
is not trivial.
How do you want to detect another execution after the current one?
Essentially we have to forbid all user code that follows execute(), collect(),
print(), count().
> 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)
