=kafka.serializer.StringEncoder
/
Many thanks
Alan
--
View this message in context:
http://camel.465427.n5.nabble.com/kafka-producer-multiple-brokers-tp5765174.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc
=2181amp;topic=testamp;partitioner=camel.myPartitioneramp;serializerClass=kafka.serializer.DefaultEncoderamp;keySerializerClass=kafka.serializer.StringEncoder
/
Many thanks
Alan
--
View this message in context:
http://camel.465427.n5.nabble.com/kafka-producer-multiple-brokers-tp5765174.html
=kafka.serializer.DefaultEncoderamp;keySerializerClass=kafka.serializer.StringEncoder
/
Many thanks
Alan
--
View this message in context:
http://camel.465427.n5.nabble.com/kafka-producer-multiple-brokers-tp5765174.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
My current thinking is to try leaving the code as-is, create multiple kafka
endpoints (one per broker) and then use the load-balancer EIP processor to
determine which endpoint(s) to send traffic through.
--
View this message in context:
http://camel.465427.n5.nabble.com/kafka-producer-multiple
=kafka.serializer.DefaultEncoderamp;keySerializerClass=kafka.serializer.StringEncoder
/
Many thanks
Alan
--
View this message in context:
http://camel.465427.n5.nabble.com/kafka-producer-multiple-brokers-tp5765174.html
Sent from the Camel - Users mailing list archive at Nabble.com.