Many thanks Cody and contributors for the help.
On Wed, May 13, 2015 at 3:44 PM, Cody Koeninger c...@koeninger.org wrote:
Either one will work, there is no semantic difference.
The reason I designed the direct api to accept both of those keys is
because they were used to define lists of
Either one will work, there is no semantic difference.
The reason I designed the direct api to accept both of those keys is
because they were used to define lists of brokers in pre-existing Kafka
project apis. I don't know why the Kafka project chose to use 2 different
configuration keys.
On
In my mind, this isn't really a producer vs consumer distinction, this is a
broker vs zookeeper distinction.
The producer apis talk to brokers. The low level consumer api (what direct
stream uses) also talks to brokers. The high level consumer api talks to
zookeeper, at least initially.
TLDR;
Many thanks Cody!
On Wed, May 13, 2015 at 4:22 PM, Cody Koeninger c...@koeninger.org wrote:
In my mind, this isn't really a producer vs consumer distinction, this is
a broker vs zookeeper distinction.
The producer apis talk to brokers. The low level consumer api (what direct
stream uses)
Looking at Consumer Configs in
http://kafka.apache.org/documentation.html#consumerconfigs
The properties *metadata.broker.list* or *bootstrap.servers *are not
mentioned.
Should I need these for consume side?
On Wed, May 13, 2015 at 3:52 PM, James King jakwebin...@gmail.com wrote:
Many thanks