Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 91491 invoked from network); 22 Feb 2010 17:31:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Feb 2010 17:31:00 -0000 Received: (qmail 88668 invoked by uid 500); 22 Feb 2010 17:31:00 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 88649 invoked by uid 500); 22 Feb 2010 17:31:00 -0000 Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: zookeeper-user@hadoop.apache.org Delivered-To: mailing list zookeeper-user@hadoop.apache.org Received: (qmail 88639 invoked by uid 99); 22 Feb 2010 17:31:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2010 17:31:00 +0000 X-ASF-Spam-Status: No, hits=3.4 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.82.66] (HELO mail-ww0-f66.google.com) (74.125.82.66) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2010 17:30:51 +0000 Received: by wwb17 with SMTP id 17so273281wwb.5 for ; Mon, 22 Feb 2010 09:30:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.86.139 with SMTP id w11mr3476451wee.10.1266859828479; Mon, 22 Feb 2010 09:30:28 -0800 (PST) X-Originating-IP: [199.181.135.135] In-Reply-To: <4B82BBDC.1030104@apache.org> References: <4B82B0EA.6050804@yahoo-inc.com> <4B82BBDC.1030104@apache.org> Date: Mon, 22 Feb 2010 09:30:28 -0800 Message-ID: Subject: Re: Znode ACL watcher? From: Mark Masse To: zookeeper-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e6d77df50e85fd048033ca8b --0016e6d77df50e85fd048033ca8b Content-Type: text/plain; charset=ISO-8859-1 Thanks guys. I don't have a strong use case but it did seem something of an oddity/incompleteness when I was implementing the eclipse plug-in to dynamically respond to znode changes. Without a Watcher available, it means that ACL changes are the one instance where a user has to manually click "Refresh" to see the latest version. This is clearly a UI-centric example, but I am not aware of any *normal* use cases where this would be an issue. Regards, -- Mark Masse http://www.massedynamic.org On Mon, Feb 22, 2010 at 9:16 AM, Patrick Hunt wrote: > Feel free to enter JIRA(s) if you feel strongly. I agree with Ben in the > sense that I haven't heard of any use cases that require this, but a JIRA > with examples might strengthen the case. > > Patrick > > > Benjamin Reed wrote: > >> no, you cannot watch for ACL changes. it is one of the API/implementation >> simplifications we did since we didn't have a good use case for it. >> >> it does seem a little bit weird. we are following file system semantics >> here. i guess for ultimate security only clients with admin permission would >> be able to see an ACL. >> >> ben >> >> On 02/22/2010 08:00 AM, Mark Masse wrote: >> >>> Hi, >>> >>> Does anyone know if there's a way to get a Watcher notification when a >>> znode's ACL changes? >>> >>> I also wanted to ask if it seems weird that you can "read" a znode's ACL >>> even if you don't have permissions to read the data. >>> >>> Thanks, >>> >>> -- >>> Mark Masse >>> http://www.massedynamic.org >>> >>> >> >> --0016e6d77df50e85fd048033ca8b--