You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2016/02/26 13:08:19 UTC

[jira] [Updated] (KUDU-764) Add the errors to the KuduRpcResponse instead going via Exceptions

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

Mike Percy updated KUDU-764:
----------------------------
    Parent: KUDU-435

> Add the errors to the KuduRpcResponse instead going via Exceptions
> ------------------------------------------------------------------
>
>                 Key: KUDU-764
>                 URL: https://issues.apache.org/jira/browse/KUDU-764
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: client
>    Affects Versions: M5
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>
> A current difficulty with the Java client is that all the errors and eventually sent back to the users as either Objects in errbacks or as generic exceptions when joining on the deferreds. Since we already have per-rpc concrete classes, we should just put the errors we get back from the servers there.



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