You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2015/09/29 09:54:05 UTC

[jira] [Commented] (FLINK-2776) Print job id to standard out on CLI job submission

    [ https://issues.apache.org/jira/browse/FLINK-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14934809#comment-14934809 ] 

Aljoscha Krettek commented on FLINK-2776:
-----------------------------------------

+2

> Print job id to standard out on CLI job submission
> --------------------------------------------------
>
>                 Key: FLINK-2776
>                 URL: https://issues.apache.org/jira/browse/FLINK-2776
>             Project: Flink
>          Issue Type: Improvement
>    Affects Versions: 0.9, 0.10
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>             Fix For: 0.10, 0.9.2
>
>
> When executing Flink jobs, the job id is printed as part of the JobClient and JobManager log messages. This information is available in the client log file but not printed to standard out by default when using the CLI client.
> Some users have requested that the job identifier should be printed to standard out such that is is available in detached execution mode. In detached execution mode, the job id is important for querying the status of a submitted job.
> We could ask users to change the log4-cli.properties settings. IMHO a better solution would be to always print the job id to standard out for submitted jobs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)