curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kanter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-58) ACLs support for ZKPaths.mkdirs()
Date Fri, 08 Nov 2013 03:21:18 GMT

    [ https://issues.apache.org/jira/browse/CURATOR-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13816953#comment-13816953
] 

Robert Kanter commented on CURATOR-58:
--------------------------------------

The locks (e.g. InterProcessReadWriteLock) also end up calling ZKPaths.mkdirs() at some point
and this causes them to always ignore the ACLProvider and set unprotected ACLs.  And I don't
think the workaround mentioned in the description is really possible to do in this case. 


I'll try to take a stab at this.

> ACLs support for ZKPaths.mkdirs()
> ---------------------------------
>
>                 Key: CURATOR-58
>                 URL: https://issues.apache.org/jira/browse/CURATOR-58
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Client, Framework
>    Affects Versions: 2.0.1-incubating
>         Environment: Ubuntu 10.10
>            Reporter: Benjamin Jaton
>            Priority: Minor
>             Fix For: TBD
>
>
> ZKPaths always creates parent node using the OPEN_ACL_UNSAFE ACL:
> line 168:
> zookeeper.create(subPath, new byte[0], ZooDefs.Ids.OPEN_ACL_UNSAFE, CreateMode.PERSISTENT);
> As a result:
> - EnsurePath.ensure(..)
> - CreateBuilderImpl.backgroundCreateParentsThenNode
> - CreateBuilderImpl.pathInForeground
> will never use the ACLProvider and will always create unprotected nodes.
> The workaround is not to use those methods and create the parents manually, node by node.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message