当你说你在一个批中发送100条消息时，你的意思是，你想控制消息的数量，还是让生产者批处理一定数量的消息然后再发送？
因为您不确定是否可以控制一个producer批处理中生成的消息的数量，所以api将对它们进行排队并对它们进行批处理，但不能保证将它们全部批处理在一起（不过我会检查一下）。
如果您同意让api为您批处理一定数量的消息，那么这里有一些关于如何确认消息的线索。
在与producer打交道时，kafka在写操作（也叫“批写”）方面具有某种可靠性
如本幻灯片所述：https://www.slideshare.net/miguno/apache-kafka-08-basic-training-verisign (83)

The original list of messages is partitioned (randomly if the default partitioner is used) based on their destination partitions/topics, i.e. split into smaller batches. 
Each post-split batch is sent to the respective leader broker/ISR (the individual send()’s happen sequentially), and each is acked by its respective leader broker according to request.required.acks

关于原子性。。对于上述行为，不确定整个批处理将被视为原子。也许您可以确保为每条消息使用相同的密钥来发送您的一批消息，因为它们将进入相同的分区，因此可能成为原子的
如果您需要在生成时更清楚地了解确认规则，请参阅下面的说明https://docs.confluent.io/current/clients/producer.html :

You can control the durability of messages written to Kafka through the acks setting. 
The default value of "1" requires an explicit acknowledgement from the partition leader that the write succeeded. 
The strongest guarantee that Kafka provides is with "acks=all", which guarantees that not only did the partition leader accept the write, but it was successfully replicated to all of the in-sync replicas.

如果您的目标是在生成时没有重复项，那么还可以查看producer enable.幂等行为。
扬尼克