You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Konstantin Knauf (Jira)" <ji...@apache.org> on 2021/07/29 07:29:11 UTC

[jira] [Reopened] (FLINK-12259) Improve debuggability of method invocation failures in OptimizerPlanEnvironment

     [ https://issues.apache.org/jira/browse/FLINK-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Knauf reopened FLINK-12259:
--------------------------------------

Re-opening in accordance with https://issues.apache.org/jira/browse/FLINK-23206.

> Improve debuggability of method invocation failures in OptimizerPlanEnvironment 
> --------------------------------------------------------------------------------
>
>                 Key: FLINK-12259
>                 URL: https://issues.apache.org/jira/browse/FLINK-12259
>             Project: Flink
>          Issue Type: Improvement
>          Components: Command Line Client
>    Affects Versions: 1.8.0
>            Reporter: Gaurav
>            Assignee: Liya Fan
>            Priority: Minor
>              Labels: auto-closed, pull-request-available, stale-assigned
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In cases where method invocation fails without setting the `optimizerPlan`, Flink does not always dump the stderr/stdout. Hence, logging from the method is lost. The stacktrace alone is not always helpful.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)