[
https://issues.apache.org/jira/browse/FLINK-12259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329506#comment-17329506
]
Flink Jira Bot commented on FLINK-12259:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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: pull-request-available, stale-assigned, stale-minor
> 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)
