[
https://issues.apache.org/jira/browse/ZOOKEEPER-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laxman updated ZOOKEEPER-847:
-----------------------------
Attachment: ZOOKEEPER-847.patch
> Missing acl check in zookeeper create
> -------------------------------------
>
> Key: ZOOKEEPER-847
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-847
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.3.1
> Reporter: Patrick Datko
> Assignee: Laxman
> Attachments: ZOOKEEPER-847.patch
>
>
> I watched the source of the zookeeper class and I missed an acl check in the
> asynchronous version of the create operation. Is there any reason, that in
> the asynch version is no
> check whether the acl is valid, or did someone forget to implement it. It's
> interesting because we worked on a refactoring of the zookeeper client and
> don't want to implement a bug.
> The following code is missing:
> if (acl != null && acl.size() == 0) {
> throw new KeeperException.InvalidACLException();
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
