[
https://issues.apache.org/jira/browse/FLINK-15504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17025334#comment-17025334
]
Gary Yao edited comment on FLINK-15504 at 1/28/20 5:51 PM:
-----------------------------------------------------------
There are some examples here
[https://ci.apache.org/projects/flink/flink-docs-release-1.9/#release-notes]
If you expect existing setups to break due to this change, we should include
your original release note. I have just created a PR for all the release notes:
https://github.com/apache/flink/pull/10937
was (Author: gjy):
There are some examples here
[https://ci.apache.org/projects/flink/flink-docs-release-1.9/#release-notes]
If you expect existing setups to break due to this change, we should include
your original release note. I have just created a PR
https://github.com/apache/flink/pull/10937
> 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
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
