[
https://issues.apache.org/jira/browse/FLINK-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels updated FLINK-2795:
--------------------------------------
Description:
{{JobExecutionResult}} s are currently not available if the Flink job is
submitted interactively via the command-line client. The reason for that is
that the execution goes through the {{ContextEnvironment}} which itself holds a
reference to the {{Client}} which it uses to submit the job.
We need to pass the JobExecutionResult back to the Client like we do it for the
JobID.
was:
{{JobExecutionResult}}s are currently not available if the Flink job is
submitted interactively via the command-line client. The reason for that is
that the execution goes through the {{ContextEnvironment}} which itself holds a
reference to the {{Client}} which it uses to submit the job.
We need to pass the JobExecutionResult back to the Client like we do it for the
JobID.
> Print JobExecutionResult for interactively invoked jobs
> -------------------------------------------------------
>
> Key: FLINK-2795
> URL: https://issues.apache.org/jira/browse/FLINK-2795
> Project: Flink
> Issue Type: Improvement
> Components: Command-line client
> Affects Versions: 0.9, 0.10
> Reporter: Maximilian Michels
> Fix For: 0.10
>
>
> {{JobExecutionResult}} s are currently not available if the Flink job is
> submitted interactively via the command-line client. The reason for that is
> that the execution goes through the {{ContextEnvironment}} which itself holds
> a reference to the {{Client}} which it uses to submit the job.
> We need to pass the JobExecutionResult back to the Client like we do it for
> the JobID.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
