Thanks Magnus, very cool I added it to the client page
https://cwiki.apache.org/confluence/display/KAFKA/Clients
cheers!
/***
Joe Stein
Founder, Principal Consultant
Big Data Open Source Security LLC
http://www.stealth.ly
Twitter: @allthingshadoop
Magnus this worked in our scripts perfectly, thanks a bunch!!
--Ian
On Apr 9, 2014, at 8:39 PM, Magnus Edenhill wrote:
> Hey Ian,
>
> this is where a tool like kafkacat comes in handy, it will use a random
> partitioner by default (without the need for defining a key):
>
> tail -f /my/log |
Thanks Magnus! I will definitely check this out
—Ian
On Apr 9, 2014, at 8:39 PM, Magnus Edenhill wrote:
> Hey Ian,
>
> this is where a tool like kafkacat comes in handy, it will use a random
> partitioner by default (without the need for defining a key):
>
> tail -f /my/log | kafkacat -b myb
Hey Ian,
this is where a tool like kafkacat comes in handy, it will use a random
partitioner by default (without the need for defining a key):
tail -f /my/log | kafkacat -b mybroker -t mytopic
See
https://github.com/edenhill/kafkacat
2014-04-10 6:13 GMT+07:00 Ian Friedman :
> Hey guys. We
This may be because the 0.8 producer sticks to a partition during
metadata refresh intervals. You can get around that by specifying a
key:
--property parse.key=true --property key.separator=###
Each line would then be:
KEY###MESSAGE
The key is used for partitioning but will also be stored with
