david-streamlio opened a new issue, #21758: URL: https://github.com/apache/pulsar/issues/21758
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation When deploying a Pulsar Function, a user might need to override the batching behavior of the functions producer. Currently, the `ProducerConfig` [configuration](https://pulsar.apache.org/docs/3.1.x/functions-cli/#producerconfig) only provides two options; "DEFAULT", and "KEY_BASED". It would be worthwhile to allow users to disable batching entirely, or have more granular control of the batching behavior, in terms of [batchingMaxBytes](https://pulsar.apache.org/api/client/3.1.x/org/apache/pulsar/client/api/ProducerBuilder.html#batchingMaxBytes(int)),[batchingMaxMessages](https://pulsar.apache.org/api/client/3.1.x/org/apache/pulsar/client/api/ProducerBuilder.html#batchingMaxMessages(int)), and [batchingMaxPublishDelay](https://pulsar.apache.org/api/client/3.1.x/org/apache/pulsar/client/api/ProducerBuilder.html#batchingMaxPublishDelay(long,java.util.concurrent.TimeUnit)) ### Solution Add the above three fields to the `ProducerConfig` definition and have them passed through to the ProducerBuilder class when the Pulsar Function is instantiated. ### Alternatives _No response_ ### Anything else? _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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]
