Implicit Acking/Nacking in Pulsar golang functions? #22444
Unanswered
conor-nsurely
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When using golang functions (Or any functions possibly) how does acking/nacking work?
Is a message nacked implicitly when a function exits with an error code? And ack when exiting with code 0?
I am having trouble understanding the behaviour
Beta Was this translation helpful? Give feedback.
All reactions