FYI, I've been able to hack into the DefaultEventHandler#handle() method with
AspectJ.
It's really dirty, but it works for the simplest cases.
https://gist.github.com/itaifrenkel/5427416
-Original Message-
From: Itai Frenkel
Sent: Saturday, April 20, 2013 11:02 AM
To: users@kafka.ap
Afaik you only put the chroot on the end of the zk conn str...
Zk1:2181,zk2:2181,zk3;2181/Kafka
Not
Zk1:2181/kafka,zk2:2181/Kafka,zk3:2181/Kafka
Sent from my iPhone
On Apr 20, 2013, at 9:03 AM, Neha Narkhede wrote:
> Please file a bug and mention the Kafka and zookeeper versions used for th
Please file a bug and mention the Kafka and zookeeper versions used for the
test.
Thanks,
Neha
On Saturday, April 20, 2013, Ryan Chan wrote:
> Hello,
>
> Tried, still the same...
>
>
> bin/zkCli.sh -server zookeeper1:2181,zookeeper2:2181,zookeeper3:2181
> [zk: zookeeper1,zookeeper2,zookeeper3(CO
Hello,
Tried, still the same...
bin/zkCli.sh -server zookeeper1:2181,zookeeper2:2181,zookeeper3:2181
[zk: zookeeper1,zookeeper2,zookeeper3(CONNECTED) 0] ls /
[testkafka, consumers, brokers, zookeeper]
[zk: zookeeper1,zookeeper2,zookeeper3(CONNECTED) 1] rmr /testkafka
[zk: zookeeper1,zookeeper2,
>>0.8 has the same DefaultEventHandler logic as 0.7, so can you try to do the
>>same in 0.8 ? We will make this easier to achieve in 0.9.
The "event.handler" configuration from v0.7 is gone from v0.8. So I would not
be able to inject a custom event handler.
Would you consider adding some kind
