WoWsj commented on issue #1142: URL: https://github.com/apache/pulsar-client-go/issues/1142#issuecomment-1857147104
> Still, user cases that need to handle concrete errors specially help us formalize the API. I am trying to use `pulser-client-go` for streaming process application. In some cases, some errors can be handled by just printing errors(like format issues or something like just informational error), but other cases which needs specific action like recreating client needs to be handled by application side. However, when I checked the code, 1. Basically, errors are not exposed to users 2. Some errors can not be exposed to user because it is only handled internally. So, In my cases, I want: 1. Expose errors to let users easily handle it. 3. It is good to separate errors into external errors(can be exposed to users) and internal errors(not exposed to users). -- 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]
