I'm now in the process of building the project from git, and I noticed it's already using the new consumer and properties. I will try it out to see if it works for me.
On Wed, Mar 16, 2016 at 1:18 PM Gerard Klijs <[email protected]> wrote: > The current version of the camel-kafka component already has the latest > released (0.9.0.1) kafka client included. To be able to use one of the new > features, mutual ssl authentication with the broker, the > current camel-kafka component needs some changes: > - Start using the new kafka consumer (), this changes a lot, different > properties are needed to create the connection, and a different mechanism > is used to subscribe to topics, and to get them. > - Allow at least 5 (preferably all) properties having to do with the ssl > configuration to be used for the ssl connection, both by the consumer and > the producer. > > I was wondering if anyone is thinking about doing this. We are currently > considering camel to connect non-java applications to our kafka cluster. We > are required to use ssl, both for the encryption, and for use with the > SimpleAclAuthorizer. It might be an option for us to do it ourselves and > summit the patch. > > I just started to take a look at camel, used it to read an xml, and send > it to kafka as avro, using the confluent schema registry. >
