[ https://issues.apache.org/jira/browse/HDFS-3680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507576#comment-13507576 ]
Aaron T. Myers commented on HDFS-3680: -------------------------------------- I've just reverted the trunk commit, but you'll still probably see some Hudson integration comments here. Please just ignore them. Suresh - thanks for taking another look. I think that Marcelo's investigation has probably addressed all of the concerns you've raised previously, but it will be good to hear your thoughts. > Allow 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-3680-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.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 require the > code to implement a log appender (and thus know what logging system is > actually being used underneath the façade), and parse the textual log message > generated by FSNamesystem. > I'm attaching a patch that introduces a cleaner interface for this use case. -- 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