[
https://issues.apache.org/jira/browse/ARROW-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058727#comment-17058727
]
Antoine Pitrou commented on ARROW-8112:
---------------------------------------
Well, we can do both: map as much as we can for third-party clients (as a best
effort), but also pass a custom header for the Arrow C++ client to read from
and faithfully reproduce the original error.
> [FlightRPC][C++] Some status codes don't round-trip through gRPC
> ----------------------------------------------------------------
>
> Key: ARROW-8112
> URL: https://issues.apache.org/jira/browse/ARROW-8112
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++, FlightRPC
> Affects Versions: 0.16.0
> Reporter: David Li
> Assignee: David Li
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> KeyError and AlreadyExists don't fully round-trip, instead becoming UNKNOWN.
> There are others, but we don't attempt to map all the Arrow status to a gRPC
> status, only the ones that closely correspond to a gRPC error.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
