Yes, a better API to differentiate the two is proposed in https://issues.apache.org/jira/browse/ARROW-16023
The 'missing' status codes are covered by standard exceptions (ValueError should map to INVALID_ARGUMENT), note that gRPC is not meant to be directly exposed so some gRPC codes do not have a direct equivalent. -David On Fri, Oct 7, 2022, at 00:28, Steve Kim wrote: > I am writing a Flight server using pyarrow.flight. I want the client to > receive INVALID_ARGUMENT status code when it sends an invalid ticket to the > server. I see that there are some FlightError subclasses that are associated > with status codes, but the set of covered status codes is incomplete. It > feels awkward to rely on exceptions to control the server's response instead > of explicitly aborting the Flight with a status code. Do I misunderstand how > this ought to work? If pyarrow.flight is missing something, I am willing to > contribute. > > Thanks in advance for any help! > Steve
