[
https://issues.apache.org/jira/browse/FLINK-26032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-26032:
-----------------------------------
Labels: pull-request-available (was: )
> log job info in the ContextEnvironment
> --------------------------------------
>
> Key: FLINK-26032
> URL: https://issues.apache.org/jira/browse/FLINK-26032
> Project: Flink
> Issue Type: Improvement
> Components: Client / Job Submission
> Reporter: Jing Ge
> Assignee: Jing Ge
> Priority: Minor
> Labels: pull-request-available
>
> In Flink codebase, the {{org.apache.flink.client.program.ContextEnvironment}}
> has a static
> [Logger|https://github.com/apache/flink/blob/7f9587c723057e2b6cbaf748181c8c80a7f6703d/flink-clients/src/main/java/org/apache/flink/client/program/ContextEnvironment.java#L47]
> defined in the class, however, it doesn’t use it to print any logs. Instead,
> it prints logs with {{System.out}} and passes the Logger to
> {{ShutdownHookUtil.addShutdownHook}} and
> {{jobExecutionResultFuture.whenComplete}} for logging any hook errors. If
> customer integrated the CLI (‘FlinkYarnSessionCli’ in their case) into a
> multi-threaded program to submit jobs in parallel, does it lead to any logs
> missing/override/disorder problems?
> It is always helpful to log the status information during the job submit
> process.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
