Expected Behavior

In a feast application that has a remote Offline Store configured, when a feast client invokes an API on the Offline store using the arrow client that throws an error, the expectation is that the client will raises the same error that the offline store threw

Current Behavior

When an error occurs a response with the error:
pyarrow._flight.FlightServerError: Feature view test does not exist in project test_remote_offline. Detail: Python exception: FeatureViewNotFoundException. gRPC client debug context: UNKNOWN:Error received from peer ipv4:0.0.0.0:54370 {created_time:"2024-09-16T12:53:49.002639-04:00", grpc_status:2, grpc_message:"Feature view test does not exist in project test_remote_offline. Detail: Python exception: FeatureViewNotFoundException"}. Client context: OK

Steps to reproduce

See Expected Behavior section.

Specifications

• Version: 0.40.0
• Platform: any
• Subsystem: offline store server

Possible Solution

The offline store server can wrap the original exception in an error status message that the remote offline store client can catch and translate into the original exception: