similar to what other connectors allow for there should be an optional batching support during the processing of sink records. such a feature could be used to kind of rate limit or at least throttle throughput towards the sink. in that sense it's an upper bound defining that at most N records are written towards the sink in one go.
introduce new configuration option for batching e.g. mongodb.max.batch.size = N
make it optional and backwards compatible thus a value of 0 is neutral and does no batching at all
any value N >= 1 batches the list the of sink records accordingly which are handed to the put() method
similar to what other connectors allow for there should be an optional batching support during the processing of sink records. such a feature could be used to kind of rate limit or at least throttle throughput towards the sink. in that sense it's an upper bound defining that at most N records are written towards the sink in one go.