[
https://issues.apache.org/jira/browse/ARROW-6884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951408#comment-16951408
]
David Li commented on ARROW-6884:
---------------------------------
I'm a little wary of automatically mirroring server-side exceptions as that
leaks implementation details into the client (also, you don't want an exception
with a sensitive repr getting propagated on accident, though I guess that ship
has sailed). But we could do more on the server (I think we don't log
exceptions or anything, so there is nothing on the server side to tell you what
happened by default).
> [Python][Flight] Make server-side RPC exceptions more friendly?
> ---------------------------------------------------------------
>
> Key: ARROW-6884
> URL: https://issues.apache.org/jira/browse/ARROW-6884
> Project: Apache Arrow
> Issue Type: Improvement
> Components: FlightRPC, Python
> Reporter: Wes McKinney
> Priority: Major
> Fix For: 1.0.0
>
>
> Here is what an error looks like when a client RPC fails in the server
> {code}
> E pyarrow.lib.ArrowException: Unknown error: gRPC returned unknown error,
> with message: a bytes-like object is required, not 'str'
> E In ../src/arrow/python/flight.cc, line 201, code: CheckPyError(). Detail:
> Python exception: TypeError
> {code}
> The "line 201, code:" business is added by -DARROW_EXTRA_ERROR_CONTEXT=ON so
> the normal use won't see this
> It might be nice to re-raise the same exception type in the client with some
> extra context added to make clear that it is a server-side error
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
