[FLINK-19135] (Stream)ExecutionEnvironment.execute() should not throw ExecutionException

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0, 1.11.0, 1.12.0
• Fix Version/s: 1.10.3, 1.11.3, 1.12.0
• Component/s: API / DataSet, API / DataStream
• Labels: pull-request-available
• Assignee: Aljoscha Krettek
• Reporter: Aljoscha Krettek
• Created: 03/Sep/20 16:43
• Updated: 15/Sep/20 10:11
• Resolved: 15/Sep/20 10:11

Description

In FLINK-14850 we changed the execute() method to be basically

final JobClient jobClient = executeAsync(...);
return jobClient.getJobExecutionResult(userClassloader).get();

Unfortunately, this means that execute() now throws an ExecutionException instead of a ProgramInvocationException or JobExecutionException as before. The ExecutionException is wrapping the other exceptions that we were throwing before.

We didn't notice this in tests because most tests use Test(Stream)Environment which overrides the execute() method and so doesn't go through the PipelineExecutor logic or the normal code path of delegating to executeAsync().

We should fix this to go back to the old behaviour.

Issue Links

• relates to: FLINK-19123 TestStreamEnvironment does not use shared MiniCluster for executeAsync()
• links to: GitHub Pull Request #13354