[ARROW-16592] [FlightRPC][Python] Regression in DoPut error handling

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 9.0.0
• Component/s: FlightRPC, Python
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/31947
• Assignee: David Li
• Reporter: Lubo Slivka
• Created: 17/May/22 08:58
• Updated: 11/Jan/23 11:45
• Resolved: 27/May/22 03:23

Description

In PyArrow 8.0.0, any error raised while handling DoPut on the server results in FlightInternalError on the client.

In PyArrow 7.0.0, errors raised while handling DoPut are propagated/converted to non-internal errors.

—

Example: on 7.0.0, raising FlightCancelledError while handling DoPut on the server would propagate that error including extra_info all the way to the FlightClient. This is not the case anymore on 8.0.0.

The FlightInternalError contains extra detail that is derived from the cancelled error though:

/arrow/cpp/src/arrow/flight/client.cc:363: Close() failed: IOError: <error message from FlightError is here>. Detail: Cancelled. gRPC client debug context: {"created":"@1652777650.446052211","description":"Error received from peer ipv4:127.0.0.1:16001","file":"/opt/vcpkg/buildtrees/grpc/src/85a295989c-6cf7bf442d.clean/src/core/lib/surface/call.cc","file_line":903,"grpc_message":"<error message from FlightError is here>. Detail: Cancelled","grpc_status":1}. Client context: OK. Detail: Cancelled
 

Note: skimming through the code, it seems this problem is not unique to PyArrow.

Issue Links

• links to: GitHub Pull Request #13191