Thank for the advice, I will add the example.
Currently, Context.newOutputMessage uses the same producer configuration as
the function/source's default output, which is converted from the
FunctionDetails.ProducerSpec, so they will use same batching configs . To
enable different topics to use disti
This is a very useful addition. Thanks for driving this.
I'd like to request an improvement to the PIP description. The current version
of the PIP description doesn't provide an example of how this would be
configured with Pulsar Functions and Pulsar Sources by end users. I'd assume
that end us
