Support for new Producer/Consumer without Zookeeper connection

Hi,

is there any plan to support using the new Consumer / new Producer configuration without having to specify the connection to Zookeeper? http://kafka.apache.org/documentation.html#producerconfigs

It looks like it will default to localhost in KafkaBinderConfigurationProperties, and is an expected setting.

In some Kafka configurations, particularly when using ACLs, the connection to Zookeeper will be firewalled and the producer/consumer will only be allowed to connect to Kafka. This is often the case when management of topics is restricted.

[garyrussell]

Just to close this out; the upcoming 2.0 release has no dependencies on zookeeper at all. Even though the bindings have used the pure java client for a long time now, we still needed to go via Zookeeper to provision topics.

There is now a pure Java AdminClient (it was added in 0.11 but was not fully functional - for the binder’s needs - until 1.0.0).

[barrycommins]

@nitantbhartia Hi, I’ve only gotten back to looking at this today, and it looks like there’s a very simple solution.

just set spring.cloud.stream.kafka.binder.auto-create-topics=false and the binder will never attempt to connect to Zookeeper. It still sets the default to localhost, but it isn’t used.

I’ve tried this on 1.1.0.RELEASE