You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2016/08/19 13:07:20 UTC

[jira] [Closed] (FLINK-4390) Add throws clause verification to RpcCompletenessTest

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

Till Rohrmann closed FLINK-4390.
--------------------------------
    Resolution: Won't Fix

I think we cannot check for the throw clause consistency because the exceptions on the remote side are hidden in the returned future. They are only thrown if one extracts the result. Thus, there is no way to check at compile time whether all occurring exceptions are treated properly :-(

> Add throws clause verification to RpcCompletenessTest
> -----------------------------------------------------
>
>                 Key: FLINK-4390
>                 URL: https://issues.apache.org/jira/browse/FLINK-4390
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Distributed Coordination
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Minor
>
> We should include the check for identical throws clauses in the {{RpcEndpoint}} and the {{RpcGateway}} implementations to the {{RpcCompletenessTest}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)