[FLINK-19135] Strip ExecutionException in (Stream)ExecutionEnvironment.execute() #13354
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In FLINK-14850 we changed the
execute()
method to be basicallyUnfortunately, this means that
execute()
now throws anExecutionException
instead of aProgramInvocationException
orJobExecutionException
as before. TheExecutionException
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 theexecute()
method and so doesn't go through the PipelineExecutor logic or the normal code path of delegating toexecuteAsync()
.This change brings us back to the previous behaviour.
Brief changelog
Verifying this change
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: yesDocumentation