Re: weird partitioner behavior

2013-01-14 Thread Jane Wang
I am still confused: (1) What I observed is that not only the first msg got wrong partition number, but also the second message. (2) If kafka uses the first msg to get the correct msg. Does it mean that if we use the customized partitioner, we cannot get the right partition for this message?

Re: weird partitioner behavior

2013-01-11 Thread Jun Rao
The very first message triggers the creation of the topic. Once the topic is created, the producer can know the # of partitions. Thanks, Jun On Fri, Jan 11, 2013 at 5:20 PM, Jane Wang wrote: > I am using kafka 0.7. and I write a simple customized partitioner: > > public static class ExpertSear

weird partitioner behavior

2013-01-11 Thread Jane Wang
I am using kafka 0.7. and I write a simple customized partitioner: public static class ExpertSearchCollectionPartitioner implementsPartitioner { @Override public synchronized int partition(Long key, int numPartitions) { System.out.print("partition: " + key.hashCode() + ", " +