You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Quan Shi (JIRA)" <ji...@apache.org> on 2019/04/19 02:17:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16821622#comment-16821622 ]
Quan Shi commented on FLINK-12259:
----------------------------------
Hi, [~fan_li_ya] More details needed, an example will be helpful.
> 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
> Affects Versions: 1.8.0
> Reporter: Gaurav
> Assignee: Liya Fan
> Priority: Minor
>
> 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
(v7.6.3#76005)