tisonkun commented on issue #1142: URL: https://github.com/apache/pulsar-client-go/issues/1142#issuecomment-1844678398
Thanks for reporting this case @WoWsj! I agree that currently almost all errors pulsar-client-go returns are opaque and we may expose the error in the public API or define some common categories (is_fatal? is_retriable?). Can you share a bit more details what methods you want to handle its errors and what errors you want handle specifically? Besides, I remember that @flowchartsman ever had a similar idea to expose client errors API in https://github.com/apache/pulsar-client-go/issues/1075. May you can share the design thoughts here to find a consensus. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
