[
https://issues.apache.org/jira/browse/ARROW-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lidavidm updated ARROW-5681:
----------------------------
Component/s: C++
Summary: [FlightRPC] Wrap gRPC exceptions/statuses (was:
[FlightRPC][Java] Wrap gRPC exceptions)
> [FlightRPC] Wrap gRPC exceptions/statuses
> -----------------------------------------
>
> Key: ARROW-5681
> URL: https://issues.apache.org/jira/browse/ARROW-5681
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, FlightRPC, Java
> Reporter: lidavidm
> Assignee: lidavidm
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Instead of requiring users to catch/throw StatusRuntimeException in Flight
> services/clients, and thereby leaking gRPC details, we should provide our own
> set of exceptions and status codes. This way, services can provide proper
> error messages and error codes to clients, which can catch the exception and
> respond properly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
