In 0.8, each message can optionally have a key. The key is retained as part of the message and will be stored in the broker. One can design a partition function to route the message based on the key. The default partitioner ignores the key and selects a partition at random.
On Mon, Jan 7, 2013 at 8:49 AM, Jason Huang <[EMAIL PROTECTED]> wrote:
Thanks for the response. If I understand you correctly, messages with the same key will not be automatically stored at the same partition unless I implement a partition function to route the message based on the key?
The quick start guide for 0.7 has the following: "Send a message with a partition key. Messages with the same key are sent to the same partition ProducerData<String, String> data = new ProducerData<String, String>("test-topic", "test-key", "test-message"); producer.send(data);"
So... there is no simple way to send messages to a certain default partition in 0.8?
Jason On Mon, Jan 7, 2013 at 12:04 PM, Jun Rao <[EMAIL PROTECTED]> wrote:
If you specify a key for a message but do not explicitly wire in a partitioner, messages with the same key will still land up in the same partition. This is because we use a default partitioner that does a simple hash(key) % num_partitions.
Thanks, Neha On Mon, Jan 7, 2013 at 9:30 AM, Jason Huang <[EMAIL PROTECTED]> wrote:
On Mon, Jan 7, 2013 at 1:52 PM, Neha Narkhede <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext