[
https://issues.apache.org/jira/browse/KUDU-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Daniel Cryans resolved KUDU-764.
-------------------------------------
Resolution: Duplicate
Fix Version/s: NA
Target Version/s: (was: GA)
I'm going to resolve this. The row errors are now part of the operation
responses and we also pool them when using auto flush background. Cleaning up
all the generic Exceptions is a different problem.
> 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
> Fix For: NA
>
>
> 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)
