[ https://issues.apache.org/jira/browse/HBASE-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535810#comment-13535810 ]
Hadoop QA commented on HBASE-6585: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12561667/HBASE-6885-0.94.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:red}-1 patch{color}. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3608//console This message is automatically generated. > Audit log messages should contain info about the higher level operation being > executed > -------------------------------------------------------------------------------------- > > Key: HBASE-6585 > URL: https://issues.apache.org/jira/browse/HBASE-6585 > Project: HBase > Issue Type: Improvement > Components: security > Affects Versions: 0.96.0 > Reporter: Marcelo Vanzin > Assignee: Matteo Bertozzi > Priority: Minor > Labels: acl > Fix For: 0.96.0, 0.94.4 > > Attachments: HBASE-6585-v0.patch, HBASE-6585-v1.patch, > HBASE-6585-v2.patch, HBASE-6885-0.94.patch > > > Currently, audit log messages contains the "action" for which access was > checked; this is one of READ, WRITE, CREATE or ADMIN. > These give very little information to the person digging into the logs about > what was done, though. You can't ask "who deleted rows from table x?", > because "delete" is translated to a "WRITE" action. > It would be nice if the audit logs contained the higher-level operation, > either replacing or in addition to the RWCA information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira