Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 50A609097 for ; Thu, 4 Oct 2012 21:33:52 +0000 (UTC) Received: (qmail 59371 invoked by uid 500); 4 Oct 2012 21:33:50 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 59325 invoked by uid 500); 4 Oct 2012 21:33:50 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 59278 invoked by uid 99); 4 Oct 2012 21:33:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Oct 2012 21:33:50 +0000 Date: Fri, 5 Oct 2012 08:33:50 +1100 (NCT) From: "Hadoop QA (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1280732987.2105.1349386430666.JavaMail.jiratomcat@arcas> In-Reply-To: <690610644.72037.1342648416949.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HDFS-3680) Allows customized audit logging in HDFS FSNamesystem MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3680?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13469= 738#comment-13469738 ]=20 Hadoop QA commented on HDFS-3680: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest= attachment=20 http://issues.apache.org/jira/secure/attachment/12547810/hdfs-3680-v8.pat= ch 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 1 = new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the = total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any = warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:e= clipse. {color:green}+1 findbugs{color}. The patch does not introduce any new = Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not incre= ase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hado= op-hdfs-project/hadoop-hdfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit te= sts. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/3268//test= Report/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3268//co= nsole This message is automatically generated. =20 > Allows customized audit logging in HDFS FSNamesystem > ---------------------------------------------------- > > Key: HDFS-3680 > URL: https://issues.apache.org/jira/browse/HDFS-3680 > Project: Hadoop HDFS > Issue Type: Improvement > Components: name-node > Affects Versions: 2.0.0-alpha > Reporter: Marcelo Vanzin > Assignee: Marcelo Vanzin > Priority: Minor > Attachments: accesslogger-v1.patch, accesslogger-v2.patch, hdfs-3= 680-v3.patch, hdfs-3680-v4.patch, hdfs-3680-v5.patch, hdfs-3680-v6.patch, h= dfs-3680-v7.patch, hdfs-3680-v8.patch > > > Currently, FSNamesystem writes audit logs to a logger; that makes it easy= to get audit logs in some log file. But it makes it kinda tricky to store = audit logs in any other way (let's say a database), because it would requir= e the code to implement a log appender (and thus know what logging system i= s actually being used underneath the fa=C3=A7ade), and parse the textual lo= g message generated by FSNamesystem. > I'm attaching a patch that introduces a cleaner interface for this use ca= se. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira