Kafka, mail # user - Re: Producer not distributing across all partitions - 2013-09-13, 20:48
Solr & Elasticsearch trainings in New York & San Fransisco [more info]
 Search Hadoop and all its subprojects:

Switch to Threaded View
Copy link to this message
-
Re: Producer not distributing across all partitions
Isn't this a bug?

I don't see why we would want users to have to code and generate random
partition keys to randomly distributed the data to partitions, that is
Kafka's job isn't it?

Or if supplying a null value tell the user this is not supported (throw
exception) in KeyedMessage like we do for topic and not treat null as a key
to hash?

My preference is to put those three lines back in and let key be null and
give folks randomness unless its not a bug and there is a good reason for
it?

Is there something about
https://issues.apache.org/jira/browse/KAFKA-691that requires the lines
taken out? I haven't had a chance to look through
it yet

My thought is a new person coming in they would expect to see the
partitions filling up in a round robin fashion as our docs says and unless
we force them in the API to know they have to-do this or give them the
ability for this to happen when passing nothing in

/*******************************************
 Joe Stein
 Founder, Principal Consultant
 Big Data Open Source Security LLC
 http://www.stealth.ly
 Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
********************************************/
On Fri, Sep 13, 2013 at 4:17 PM, Drew Goya <[EMAIL PROTECTED]> wrote:
 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB