Return-Path: X-Original-To: apmail-curator-dev-archive@minotaur.apache.org Delivered-To: apmail-curator-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 14B3D18F28 for ; Mon, 18 Jan 2016 22:37:40 +0000 (UTC) Received: (qmail 49263 invoked by uid 500); 18 Jan 2016 22:37:40 -0000 Delivered-To: apmail-curator-dev-archive@curator.apache.org Received: (qmail 49182 invoked by uid 500); 18 Jan 2016 22:37:40 -0000 Mailing-List: contact dev-help@curator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@curator.apache.org Delivered-To: mailing list dev@curator.apache.org Received: (qmail 49075 invoked by uid 99); 18 Jan 2016 22:37:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jan 2016 22:37:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C61E22C1F57 for ; Mon, 18 Jan 2016 22:37:39 +0000 (UTC) Date: Mon, 18 Jan 2016 22:37:39 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@curator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CURATOR-244) Creating parents with ACLProvider puts wrong ACLs on znodes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CURATOR-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105909#comment-15105909 ] ASF GitHub Bot commented on CURATOR-244: ---------------------------------------- Github user cammckenzie commented on the pull request: https://github.com/apache/curator/pull/122#issuecomment-172672665 This looks ok to me. > Creating parents with ACLProvider puts wrong ACLs on znodes > ----------------------------------------------------------- > > Key: CURATOR-244 > URL: https://issues.apache.org/jira/browse/CURATOR-244 > Project: Apache Curator > Issue Type: Bug > Affects Versions: 2.6.0 > Reporter: John Vines > Assignee: Jordan Zimmerman > Fix For: 2.9.2 > > > Currently, if I create /foo/bar/baz and /foo doesn't exist it will create the whole hierarchy, but it will create /foo and /foo/bar with the ACLs the provider provides for /foo/bar/baz. I would expect it to consult the ACLProvider for the right znode (which seems totally doable but for some reason it passes in the wrong path to the provider when creating parents) or not ACL the parent znode. > This is similar to CURATOR-221, but I think this behavior makes for a pretty bad user experience as it's not simply a case of checking how you namespace a curatorframework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)