Home | About | Sematext search-lucene.com search-hadoop.com
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
 Search Hadoop and all its subprojects:

Switch to Threaded View
Zookeeper >> mail # user >> Generating Events With Incorrect types


Copy link to this message
-
Re: Generating Events With Incorrect types
Would be a good improvement, but tough from a b/w compatibility
perspective. Propose for 4.0 by entering a JIRA? Thanks!

Patrick

On Mon, Jun 11, 2012 at 10:27 AM, Grigory Dzhavadyan
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> It appears that I have mixed up the order of "event type" and
> "connection state" arguments in the handler function. Both are
> integers, so the compiler did not say anything. A hard-to-notice error
> :-). Maybe it would make sense to turn those into enums? At least the
> C++ compiler would complain, I guess.
>
> On Fri, Jun 8, 2012 at 3:51 PM, Michi Mutsuzaki <[EMAIL PROTECTED]> wrote:
>> Hi Grigory,
>>
>> Yes, you should get ZOO_CREATED_EVENT. Could you post a short program
>> that reproduces the issue?
>>
>> Thanks!
>> --Michi
>>
>> On Fri, Jun 8, 2012 at 2:15 PM, Grigory Dzhavadyan
>> <[EMAIL PROTECTED]> wrote:
>>> Hello,
>>>
>>> I'm using the Zookeeper C API to set a watch on a non-existent node
>>> using the `zoo_wexists' function.
>>>
>>> When I create that node, I'm expecting the event handler to be called
>>> with `type' equal to `ZOO_CREATED_EVENT'. However, instead it's being
>>> called with type equal to `ZOO_CHANGED_EVENT'. Why is that so and what
>>> should I do to receive the correct type in the event handler?
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