thanks Patrick, I want to know all watches set by all clients.
I would open a jira and write some design think about it later.
On Tue, Nov 2, 2010 at 11:53 PM, Patrick Hunt ph...@apache.org wrote:
Hi Qian Ye, yes you should open a JIRA for this. If you want to work
on a patch we could advise
Definitely checkout the 4letter words then (wch*). Keep in mind
getting this data may be expensive (if there's alot of it) and that
watches are locak, so servers only know about the watches from
sessions est through it (server 1 doesn't know about watches of
sessions connected on server 2, 3,
Hi all,
Is there any progress about this issue? Should we open a new JIRA for it? We
really need a way to know who set watchers on a specific node.
thanks~
On Thu, Aug 6, 2009 at 11:01 PM, Qian Ye yeqian@gmail.com wrote:
Thanks Mahadev, I think it is a useful feature for many scenarios.
Hi Qian Ye, yes you should open a JIRA for this. If you want to work
on a patch we could advise you. One thing not clear to me, are you
interested in just the watches set by the particular client, or all
watches set by all clients? The first should be relatively easy to
get, the second would be
Thanks Mahadev, I think it is a useful feature for many scenarios.
On Thu, Aug 6, 2009 at 12:59 PM, Mahadev Konar maha...@yahoo-inc.comwrote:
Hi Qian,
There isnt any such api. We have been thinking abt adding an api on
cancelling a cleints watches. We have been thinking about adding a proc
Hi Qian,
There isnt any such api. We have been thinking abt adding an api on
cancelling a cleints watches. We have been thinking about adding a proc
filesystem wherein a cleintt will have a list of all the watches. This data
can be used to know which clients are watching what znode, but this has
