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

ASF GitHub Bot commented on ZOOKEEPER-2709:
-------------------------------------------

GitHub user joshelser opened a pull request:

    https://github.com/apache/zookeeper/pull/182

    ZOOKEEPER-2709 Clarify documentation around the "auth" ACL scheme

    Not sure if I should include the modified files from the result of `ant 
docs`. Happy to do so if expected :)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/joshelser/zookeeper ZOOKEEPER-2709

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zookeeper/pull/182.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #182
    
----
commit 207146e8df26d3a22199725e2f36c04d473f7e37
Author: Josh Elser <josh.el...@gmail.com>
Date:   2017-03-03T21:28:50Z

    ZOOKEEPER-2709 Clarify documentation around the "auth" ACL scheme

----


> 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
>
> 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)

Reply via email to