flowchartsman commented on pull request #9513: URL: https://github.com/apache/pulsar/pull/9513#issuecomment-781516820
> Just as you said, all send failures are fatal, but this is limited within `goInstance`’s `producer`. For user who get `producer` from `context.outputMessage()`, it might different. It depends on what the goal of the SDK is. If you look at the [python pfunc SDK example](https://pulsar.apache.org/docs/en/functions-overview/#content-based-routing-example), it is just `context.publish(topic, item)` If that is the experience you are after, then, it seems best to keep it simple and consistent. Given the way the Go pfunc SDK is structured, this seems like the option more in keeping with the intent. > A relatively simple but not very mature idea is: we have a timing task in the background to process these resources regularly, for example: 30 minutes Are there any objections to this idea? It makes sense to me. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
