[
https://issues.apache.org/jira/browse/ZOOKEEPER-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902352#comment-15902352
]
Hudson commented on ZOOKEEPER-2709:
-----------------------------------
FAILURE: Integrated in Jenkins build ZooKeeper-trunk #3305 (See
[https://builds.apache.org/job/ZooKeeper-trunk/3305/])
ZOOKEEPER-2709: Clarify documentation around the "auth" ACL scheme (hanm: rev
cf4f119516ca3d232fe077477c7a91b2e5825de2)
* (edit) src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml
> Clarify documentation around "auth" ACL scheme
> ----------------------------------------------
>
> Key: ZOOKEEPER-2709
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2709
> Project: ZooKeeper
> Issue Type: Task
> Components: documentation
> Reporter: Josh Elser
> Priority: Minor
> Fix For: 3.5.3, 3.6.0
>
>
> We recently found up in HBASE-17717 that we were incorrectly setting an ACL
> on our "sensitive" znodes after the output of {{getACL}} on these nodes
> didn't match what was expected.
> In referencing the documentation about how the {{auth}} ACL scheme was
> supposed to work, it was unclear if it was a ZooKeeper bug or an HBase bug.
> After reading some ZooKeeper code, we found that it was an HBase bug, but it
> would be nice to clarify the docs around this ACL scheme.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
