Closed rshura closed 1 month ago
I don't think we're going to take a gRPC dependency in the core (nor are the errors here defined in terms of gRPC in the first place)
I assume this is for Go.
Let's narrow this down to encoding flightsql errors as ProtobufErrorDetail
as opposed to anyErrorDetail
.
Another thing: the list of error details included one actual error detail, and also three TextErrorDetail
items with the key trailer
and respective values Grpc-Status
, Grpc-Message
and Grpc-Status-Details-Bin
. Perhaps flightsql error-packing can skip these, seeing how those values can't possibly be useful to the error-processing code.
Closing as this makes little sense outside of go. Within go I have a workable way to deal with the errors.
What feature or improvement would you like to see?
Details()
method that would decode from Any into a typed protobuf.adbc.Error
intogrpc.Status
.