[Bug] unable to achieve MANUAL semantics on pulsar-function-go SDK

[rohithg145]

Search before asking

• I searched in the issues and found nothing similar.

Read release policy

• I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version

pulsar: v4.0.0

Minimal reproduce step

1. use pulsar-function-go SDK to create a sample function using go runtime.
2. try to use MANUAL delivery method, where user has to handle the Ack() and Nack() of each message.
3. inside the created sample function, get FunctionContexted from the context object.
4. use the FunctionContext to Ack() or Nack() the current record/message manually

What did you expect to see?

according to documentation: "A function to acknowledge the message being processed (if auto-ack is disabled)"
it is expected from SDK, to provide an API/method through FunctionContext, that has consumer information, so that Ack() & Nack() is possible

What did you see instead?

fctx.GetCurrentRecord() returns a pulsar.Message instead of pulsar.ConsumerMessage, and not other way to access the consumer to Ack() / Nack() the records

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!