Hi Eric,

Thank you very much for the quick response.
Yes, I thought so, but asRuntimeException(metadata) is an experimental API
so I was wondering if there is another better way.
(Seems like StatusProto is also experimental)

Could you (or anyone) give me a hint of how much I can rely on the
experimental APIs for our production use ?
Are they going to be changed quite surely ?

Thanks,
Hiro


On Thu, Dec 12, 2019 at 3:33 AM Eric Anderson <[email protected]> wrote:
>
> You can provide additional details in the Metadata, which can be attached to 
> a StatusException/StatusRuntimeException. You would define a proto message to 
> hold the specific details you care about and then pass it in the Metadata 
> directly on in a google.rpc.Status. See 
> https://stackoverflow.com/a/48750825/4690866 for how that looks.
>
> On Tue, Dec 10, 2019 at 7:41 PM <[email protected]> wrote:
>>
>> Hello,
>>
>> I'm wondering how I can send an application specific error code to clients 
>> in grpc-java.
>>
>> I've been using gprc-java for a few years, but I haven't used onError api in 
>> a server
>> since there seems no way to return application specific error status/code to 
>> a client.
>> (Unless I serialize the code to String and pass it through description or 
>> something)
>>
>> It would be great if experts can give me some advice for this.
>>
>> Thanks,
>> Hiro
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "grpc.io" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/grpc-io/9a02e7f4-25ea-4943-8d0e-987122a99e02%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/CAPDOW77etdLtkucShviWT%2BaXyjNd199JN4ufu-gxdq54GL9_CQ%40mail.gmail.com.

Reply via email to