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

Flink Jira Bot updated FLINK-20020:
-----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned 
pull-request-available  (was: auto-deprioritized-major auto-unassigned 
pull-request-available stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any 
updates so it is being deprioritized. If this ticket is actually Minor, please 
raise the priority and ask a committer to assign you the issue or revive the 
public discussion.


> Make UnsuccessfulExecutionException part of the 
> JobClient.getJobExecutionResult() contract.
> -------------------------------------------------------------------------------------------
>
>                 Key: FLINK-20020
>                 URL: https://issues.apache.org/jira/browse/FLINK-20020
>             Project: Flink
>          Issue Type: Improvement
>          Components: Client / Job Submission
>    Affects Versions: 1.12.0
>            Reporter: Kostas Kloudas
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, 
> auto-unassigned, pull-request-available
>
> Currently, different implementations of the {{JobClient}} throw different 
> exceptions. The {{ClusterClientJobClientAdapter}} wraps the exception from 
> the {{JobResult.toJobExecutionResult()}} into a 
> {{ProgramInvocationException}}, the {{MiniClusterJobClient}} simply wraps it 
> in a {{CompletionException}} and the {{EmbeddedJobClient}} wraps it into an 
> {{UnsuccessfulExecutionException}}. 
> With this issue I would like to propose making the exception uniform and part 
> of the contract and as a candidate I would propose the behaviour of the 
> {{EmbeddedJobClient}} which throws an {{UnsuccessfulExecutionException}}. The 
> reason is that this exception also includes the status of the application.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to