Hi,
According to the auto.create.topics.enable description, 1). attempts to
produce, 2), consume, 3), fetch metadata for a non-existent topic will
automatically create the topic with default config. I set the
auto.create.topics.enable to true, and only 3) fetch metadata will creates the
topic.
Hi,
According to the auto.create.topics.enable description, 1). attempts to
produce, 2), consume, 3), fetch metadata for a non-existent topic will
automatically create the topic with default config. I set the
auto.create.topics.enable to true, and only 3) fetch metadata will creates the
topic.
Hi,
I have 2 questions about the partition number and key.
1. The produceRequest will explicitly include a partitionNumber, and
messageSet which contains messages with key(can be NULL, used to calculate
partitionNumber when specified). I am assuming all the messages in the
messageSet will be
Thanks for the reply! If the broker does not make the decision, then where and
how the key is used to calculate the partition number?
On Mar 5, 2014, at 5:42 PM, Joel Koshy wrote:
>> I have 2 questions about the partition number and key.
>> 1. The produceRequest will explicitly include a part
equest.
>
> On Thu, Mar 06, 2014 at 10:17:22AM -0800, Churu Tang wrote:
>> Thanks for the reply! If the broker does not make the decision, then where
>> and how the key is used to calculate the partition number?
>>
>> On Mar 5, 2014, at 5:42 PM, Joel Koshy wrote:
&
Hi,
I am building kafka client using C++ Client API. The offsetRequest API is based
on
https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-OffsetRequest
According to the documentation, the “Time” field in offsetRequest is used
e unix timestamp, except for the 2 special
> values for getting earliest and latest offsets.
>
> Thanks
> Neha
>
> On Thursday, March 13, 2014, Churu Tang wrote:
>
>> Hi,
>> I am building kafka client using C++ Client API. The offsetRequest API is
>> based
Hi,
“Consumers label themselves with a consumer group name”, and consumer group
name should be global across each Kafka cluster. However, when I check the API,
there is no “consumer group name” included in any kind of request(metadata,
produce, fetch, offset). Does the broker know about the con
ching requests to
> the brokers. Brokers on the other hand will just blindly respond to the
> fetch requests.
>
> Hope this helps.
>
> Guozhang
>
>
> On Fri, Mar 14, 2014 at 4:50 PM, Churu Tang wrote:
>
>> Hi,
>>
>> "Consumers label themsel
he
> consumers since the decision algorithm is deterministic.
>
> In the coming Kafka 0.9, this logic will be moved to the brokers so
> consumer clients will be thinner: no ZK dependency and no coordination
> logic at all.
>
> Guozhang
>
>
>
>
>
>
> On
Hi,
In java you provide some nice API for high-level consumer as well as simple
consumer. However, in C++, I only see 4 kinds of requests(meta, produce,
offset, fetch). Will C++ also include those high-level and simple consumer API
as well in the future?
A consumer will do lots of registration
ps://github.com/adobe-research/libkafka
> * for 0.8: librdkafka: https://github.com/edenhill/librdkafka
>
> Which one are you referring to?
>
> Regards,
> Magnus
>
>
> 2014-03-22 0:56 GMT+07:00 Churu Tang :
>
>> Hi,
>>
>> In java you provide some
Now I understand that. Thank you very much for your explanation!
Cheers,
Churu
On Mar 21, 2014, at 7:27 PM, Magnus Edenhill wrote:
> Hi,
>
> most third party clients don't feature the zookeeper and consumer group
> logic of the official scala/java clients due to the complexity of it.
> There a
Hi,
1. In documentation 0.8.1, the mirror maker command is:
bin/kafka-run-class.sh kafka.tools.MirrorMaker --zookeeper zk_host:port/chroot
--consumer.config consumer-1.properties --consumer.config
consumer-2.properties
--producer.config producer.properties --whitelist my-topic
How
14 matches
Mail list logo