[
https://issues.apache.org/jira/browse/FLINK-36711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Woo updated FLINK-36711:
--------------------------------
Description:
When System.out and System.err are redirected to LOG or discarded, there are
some scenarios that do not match the user's expectations, leading them to be
unclear about how to view the relevant output information
# SREs that maintain Flink clusters set all jobs to be redirected or discarded
by default
# There are multiple maintainers for the same task, one of them set to
redirect and the rest are not aware of it.
Situations such as the above can cause users to add System.out or System.err
related output, but there is no related output when viewing the out or err
file, and they don't know the reason for this and don't know where to view the
related output information.
So we can add tips to optimize these situations, the effect is as follows:
!image-2024-11-13-22-57-13-739.png|width=787,height=295!
was:
When System.out and System.err are redirected to LOG or discarded, there are
some scenarios that do not match the user's expectations, leading them to be
unclear about how to view the relevant output information
# SREs that maintain Flink clusters set all jobs to be redirected or discarded
by default
# There are multiple maintainers for the same task, one of them set to
redirect and the rest are not aware of it.
Situations such as the above can cause users to add System.out or System.err
related output, but there is no related output when viewing the out or err
file, and they don't know the reason for this and don't know where to view the
related output information.
So we can add tips to optimize these situations, the effect is as follows:
!image-2024-11-13-22-57-13-739.png|width=787,height=295!
> Add tips when System out and err are redirected to LOG or discarded
> -------------------------------------------------------------------
>
> Key: FLINK-36711
> URL: https://issues.apache.org/jira/browse/FLINK-36711
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Reporter: Vincent Woo
> Assignee: Vincent Woo
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.0
>
> Attachments: image-2024-11-13-22-57-13-739.png
>
>
> When System.out and System.err are redirected to LOG or discarded, there are
> some scenarios that do not match the user's expectations, leading them to be
> unclear about how to view the relevant output information
> # SREs that maintain Flink clusters set all jobs to be redirected or
> discarded by default
> # There are multiple maintainers for the same task, one of them set to
> redirect and the rest are not aware of it.
> Situations such as the above can cause users to add System.out or System.err
> related output, but there is no related output when viewing the out or err
> file, and they don't know the reason for this and don't know where to view
> the related output information.
>
> So we can add tips to optimize these situations, the effect is as follows:
> !image-2024-11-13-22-57-13-739.png|width=787,height=295!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
