You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Gary Malouf (Created) (JIRA)" <ji...@apache.org> on 2012/02/15 20:12:59 UTC

[jira] [Created] (ZOOKEEPER-1393) ZooKeeper client exists() javadoc incorrectly states watcher(s) will be triggered on node deletion

ZooKeeper client exists() javadoc incorrectly states watcher(s) will be triggered on node deletion
--------------------------------------------------------------------------------------------------

                 Key: ZOOKEEPER-1393
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1393
             Project: ZooKeeper
          Issue Type: Bug
          Components: java client
    Affects Versions: 3.4.2, 3.3.4
            Reporter: Gary Malouf
            Priority: Minor


I found it very misleading that the javadoc for the exists() calls that take a boolean or a Watcher state that 'The watch will be triggered by a successful operation that creates/delete the node or sets the data on the node.'

What I've seen from descriptions of bugs (older but this is this references it http://zookeeper-user.578899.n2.nabble.com/Exists-Watch-Triggered-by-Delete-td1490893.html) and my own personal usage is that watchers set on exists() are triggered when a non-existing node is now created or an existing node is changed.  They are NOT triggered when the node already exists and is deleted.

http://zookeeper.apache.org/doc/r3.4.3/api/index.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (ZOOKEEPER-1393) ZooKeeper client exists() javadoc incorrectly states watcher(s) will be triggered on node deletion

Posted by "Gary Malouf (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Malouf resolved ZOOKEEPER-1393.
------------------------------------

    Resolution: Invalid

It turned out to be an issue related to the client wrapper I was using.
                
> ZooKeeper client exists() javadoc incorrectly states watcher(s) will be triggered on node deletion
> --------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1393
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1393
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.3.4, 3.4.2
>            Reporter: Gary Malouf
>            Priority: Minor
>   Original Estimate: 20m
>  Remaining Estimate: 20m
>
> I found it very misleading that the javadoc for the exists() calls that take a boolean or a Watcher state that 'The watch will be triggered by a successful operation that creates/delete the node or sets the data on the node.'
> What I've seen from descriptions of bugs (older but this is this references it http://zookeeper-user.578899.n2.nabble.com/Exists-Watch-Triggered-by-Delete-td1490893.html) and my own personal usage is that watchers set on exists() are triggered when a non-existing node is now created or an existing node is changed.  They are NOT triggered when the node already exists and is deleted.
> http://zookeeper.apache.org/doc/r3.4.3/api/index.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira