Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 18 Aug 2016 17:47:20 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12998260.1471542392000.347395.1471542440694@Atlassian.JIRA>
In-Reply-To: <JIRA.12998260.1471542392000@Atlassian.JIRA>
References: <JIRA.12998260.1471542392000@Atlassian.JIRA> <JIRA.12998260.1471542392562@arcas>
Subject: [jira] [Created] (HBASE-16449) Revisit AccessController audit
 logging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 18 Aug 2016 17:47:22 -0000

Andrew Purtell created HBASE-16449:
--------------------------------------

             Summary: Revisit AccessController audit logging
                 Key: HBASE-16449
                 URL: https://issues.apache.org/jira/browse/HBASE-16449
             Project: HBase
          Issue Type: Bug
            Reporter: Andrew Purtell


On Hadoop discussion lists the subject of audit logging stability came up recently, and I offered this suggestion:

{quote}
please consider freezing any changes to audit logging today, develop a formal specification, add the specification to documentation, and then take care to not break the specification between releases. 
...
You'll want to hash out what level of compatibility you'd like to offer. I'd recommend only changing on major releases. 
{quote}

This applies equally to HBase audit logging in the AccessController. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)