[ https://issues.apache.org/jira/browse/HBASE-6062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287243#comment-13287243 ]
Hudson commented on HBASE-6062: ------------------------------- Integrated in HBase-0.92-security #109 (See [https://builds.apache.org/job/HBase-0.92-security/109/]) HBASE-6062 preCheckAndPut/Delete() checks for READ when also a WRITE is performed (Revision 1344488) Result = SUCCESS stack : Files : * /hbase/branches/0.92/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/branches/0.92/security/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java > preCheckAndPut/Delete() checks for READ when also a WRITE is performed > ---------------------------------------------------------------------- > > Key: HBASE-6062 > URL: https://issues.apache.org/jira/browse/HBASE-6062 > Project: HBase > Issue Type: Sub-task > Components: security > Affects Versions: 0.92.1, 0.94.0, 0.96.0 > Reporter: Matteo Bertozzi > Assignee: Matteo Bertozzi > Labels: acl, security > Fix For: 0.92.2, 0.94.1 > > Attachments: HBASE-6062-0.92.patch, HBASE-6062-v0.patch, > HBASE-6062-v1.patch > > > preCheckAndPut() and preCheckAndDelete() checks for READ when they also want > to WRITE... > for me checking for WRITE permission is the right thing... > what do you say about that? keep READ, replace with WRITE? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira