[
https://issues.apache.org/jira/browse/HBASE-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547290#comment-13547290
]
Hadoop QA commented on HBASE-6393:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12563812/HBASE-6393-v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/3935//console
This message is automatically generated.
> Decouple audit event creation from storage in AccessController
> --------------------------------------------------------------
>
> Key: HBASE-6393
> URL: https://issues.apache.org/jira/browse/HBASE-6393
> Project: HBase
> Issue Type: Brainstorming
> Components: security
> Affects Versions: 0.96.0
> Reporter: Marcelo Vanzin
> Attachments: hbase-6393-v1.patch, HBASE-6393-v2.patch,
> HBASE-6393-v3.patch
>
>
> Currently, AccessControler takes care of both generating audit events (by
> performing access checks) and storing them (by creating a log message and
> writing it to the AUDITLOG logger).
> This makes the logging system the only way to catch audit events. It means
> that if someone wants to do something fancier (like writing these records to
> a database somewhere), they need to hack through the logging system, and
> parse the messages generated by AccessController, which is not optimal.
> The attached patch decouples generation and storage by introducing a new
> interface, used by AccessController, to log the audit events. The current,
> log-based storage is kept in place so that current users won't be affected by
> the change.
> I'm filing this as an RFC at this point, so the patch is not totally clean;
> it's on top of HBase 0.92 (which is easier for me to test) and doesn't have
> any unit tests, for starters. But the changes should be very similar on trunk
> - I don't remember changes in this particular area of the code between those
> versions.
--
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
