zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2709) Clarify documentation around "auth" ACL scheme
Date Wed, 08 Mar 2017 18:49:38 GMT

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

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

Github user joshelser commented on the issue:

    https://github.com/apache/zookeeper/pull/182
  
    @hanm @afine let's try out 4d7b712 (didn't squash so it's easier to see what was changed
-- sans the line-wrapping, sorry in advance).
    
    I tried to consistently (and correctly) use the terms "id" and "expression" throughout.
I hope it's more clear now :D


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

Mime
View raw message