Hi Chris, The new producer returns a future so it works in an async manner hence no need for the producer.type property.
0.8 -> 0.10 batch.num.messages -> batch.size queue.buffering.max.ms -> linger.ms Your assumptions for the serializers look correct. Take a look at the documentation for both versions. http://kafka.apache.org/081/documentation.html and http://kafka.apache.org/081/documentation.html. Hope that helps From: users@kafka.apache.org At: 06/27/16 09:34:55 To: users@kafka.apache.org Subject: Re: Producer Properties Anybody? Chris From: Chris Barlock/Raleigh/IBM@IBMUS To: users@kafka.apache.org Date: 06/24/2016 04:56 PM Subject: Producer Properties I started porting our code from Kafka 0.8.2.1 to 0.10.0.0 and found my producer code blowing up because of some changes to the config. For example, metadata.broker.list is now bootstrap.servers. I discovered the ProducerConfig class which has, at least, some of the config keys. Before I screw this up, I'd like some confirmation of the right mappings for these config pararmeters in our 0.8.2.1 code: serializer.class Maybe value.serializer = VALUE_SERIALIZER_CLASS_CONFIG? key.serializer.class Maybe key.serializer = KEY_SERIALIZER_CLASS_CONFIG? producer.type Not in ProducerConfig batch.num.messages Not in ProducerConfig, unless maybe batch.size = BATCH_SIZE_CONFIG? queue.buffering.max.ms Not in ProducerConfig Thanks! Chris
