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 53DF0DE7F for ; Thu, 29 Nov 2012 20:58:59 +0000 (UTC) Received: (qmail 29288 invoked by uid 500); 29 Nov 2012 20:58:59 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 29252 invoked by uid 500); 29 Nov 2012 20:58:59 -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 29242 invoked by uid 99); 29 Nov 2012 20:58:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Nov 2012 20:58:59 +0000 Date: Thu, 29 Nov 2012 20:58:58 +0000 (UTC) From: "Aaron T. Myers (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <109145252.42042.1354222739054.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=3D13506= 783#comment-13506783 ]=20 Aaron T. Myers commented on HDFS-3680: -------------------------------------- +1, the latest patch looks good to me. I'm going to commit this tomorrow unless anyone has further comments in the= meantime. (Suresh?) =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: namenode > Affects Versions: 2.0.0-alpha > Reporter: Marcelo Vanzin > Assignee: Marcelo Vanzin > Priority: Minor > Attachments: accesslogger-v1.patch, accesslogger-v2.patch, hdfs-3= 680-v10.patch, hdfs-3680-v3.patch, hdfs-3680-v4.patch, hdfs-3680-v5.patch, = hdfs-3680-v6.patch, hdfs-3680-v7.patch, hdfs-3680-v8.patch, hdfs-3680-v9.pa= tch > > > 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