[
https://issues.apache.org/jira/browse/FLINK-15504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels updated FLINK-15504:
---------------------------------------
Description:
Flink uses the {{OptimizerPlanEnvironment}} which replaces stdout/stderr during
job graph creation. This was intended only for previewing the plan, but other
parts of Flink, e.g. the Rest API have started to use this code as well.
It may be acceptable to suppress output during plan preview, but we should not
suppress the output during execution, e.g. via the REST API.
was:
Flink uses the org.apache.flink.client.program.OptimizerPlanEnvironment which
replaces stdout/stderr during job graph creation. This was intended only for
previewing the plan, but other parts of Flink, e.g. the Rest API have started
to use this code as well.
It may be acceptable to suppress output during plan preview, but we should not
suppress the output during execution, e.g. via the REST API.
> Flink suppresses stdout/stderr during JobGraph generation from JAR
> ------------------------------------------------------------------
>
> Key: FLINK-15504
> URL: https://issues.apache.org/jira/browse/FLINK-15504
> Project: Flink
> Issue Type: Bug
> Components: Client / Job Submission
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
>
> Flink uses the {{OptimizerPlanEnvironment}} which replaces stdout/stderr
> during job graph creation. This was intended only for previewing the plan,
> but other parts of Flink, e.g. the Rest API have started to use this code as
> well.
> It may be acceptable to suppress output during plan preview, but we should
> not suppress the output during execution, e.g. via the REST API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
