[CURATOR-221] ACLProvider is not respected on parent nodes after calling CuratorFramework.usingNamespace

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Delivered
• Affects Version/s: 2.7.1
• Component/s: Framework
• Assignee: Unassigned
• Reporter: Gregory Chanan
• Created: 18/May/15 21:33
• Updated: 19/Aug/24 05:03
• Resolved: 19/Aug/24 05:03

Description

See HADOOP-11973 for some background information.

Here's a high level overview of the issue I'm seeing:
1) I create a CuratorFramework with a non-default ACLProvider
2) I call framework.usingNamespace("/solr/zkdtsm") on the curator framework
3) I do some action, like starting a new SharedCount on a subnode of the namespace /testPath/ZKDTSMRoot/ZKDTSMSeqNumRoot

Result: the tree is created, but neither /solr nor /solr/zkdtsm have ACLs, while /testPath/ZKDTSMRoot/ZKDTSMSeqNumRoot does. I would expect all those nodes would have ACLs because I only performed zookeeper actions on a CuratorFramework with an ACLProvider specified.

This seems to happen because NamespaceImpl does not save the ACLProvider, see this line:
https://github.com/apache/curator/blob/7f2098654a26e2f593801a586ce68300f54abf15/curator-framework/src/main/java/org/apache/curator/framework/imps/NamespaceImpl.java#L47

Then, when an action is performed on the namespace, fixForNamespace is called:
https://github.com/apache/curator/blob/7f2098654a26e2f593801a586ce68300f54abf15/curator-framework/src/main/java/org/apache/curator/framework/imps/NamespaceImpl.java#L74
resulting in the parents being created without an ACL.

Issue Links

• is fixed by: CURATOR-222 Support Container Nodes
• is superceded by: CURATOR-714 Add tests to ensure that ACLProvider is respect in CuratorFramework.usingNamespace
• relates to: HADOOP-11973 Ensure ZkDelegationTokenSecretManager namespace znodes get created with ACLs