You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Arvid Heise (Jira)" <ji...@apache.org> on 2024/07/10 07:53:00 UTC
[jira] [Commented] (FLINK-35796) Ensure that MailboxExecutor.submit is used correctly
[ https://issues.apache.org/jira/browse/FLINK-35796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864521#comment-17864521 ]
Arvid Heise commented on FLINK-35796:
-------------------------------------
Merged into master as 0bf2aaac0e38e7f322968094562d4f1e85318879.
> Ensure that MailboxExecutor.submit is used correctly
> ----------------------------------------------------
>
> Key: FLINK-35796
> URL: https://issues.apache.org/jira/browse/FLINK-35796
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
> Affects Versions: 2.0.0
> Reporter: Arvid Heise
> Assignee: Arvid Heise
> Priority: Major
> Labels: pull-request-available
>
> https://issues.apache.org/jira/browse/FLINK-34470 showed that MailboxExecutor.submit may result in unexpected exception handling: while {{execute}} will bubble up the exception in the task thread and result in some fault, {{submit}} can hide the exception because the API assumes that the returned {{Future}} is checked for it explicitly or implicitly.
> We can solve the situation by improving the doc of MailboxExecutor and double-check the internal usages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)