hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9343) Allow additional exceptions through the RPC layer
Date Thu, 28 Feb 2013 21:53:13 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589963#comment-13589963

Siddharth Seth commented on HADOOP-9343:

Agree with IPC errors being defined via codes and enums (along with a string description and
maybe the existing exception name). Had mentioned something along these lines for easier cross
language usage in MAPREDUCE-4067 - which included error codes in exceptions - but that seems
unnecessary, and somehow got lost. Since we already have layers, converting such errors over
to Java exceptions for the existing clients should be reasonably straightforward.

My understanding of the impact. I'm not sure if the proto files will be sufficiently self-documenting,
or we'll need to define the complete API specification somewhere else. IAC, looks like the
core API (which is currently split between protos and errors defined by the Java interfaces)
will be defined by the wire protocol definition (and the Hadoop RPC extras) . The existing
Java interfaces would become language specific interfaces. Does that sound right ?

If we do take such a route, which version would be targeted ?

For now, I'd like to get the change posted in this JIRA committed for the YARN api fixes.

> Allow additional exceptions through the RPC layer
> -------------------------------------------------
>                 Key: HADOOP-9343
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9343
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.0.3-alpha
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: HADOOP-9343.txt
> The RPC layer currently only allows IOException, RuntimeException, InterruptedException
and their derivatives - which limits exceptions declared by protocols.
> Other exceptions end up at the client as an UndeclaredThrowableException wrapped in RemoteException.
> Additional exception types should be allowed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message