Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 16 Feb 2012 22:33:00 +0000 (UTC)
From: "Enis Soztutar (Created) (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <4947439.48487.1329431580634.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HIVE-2809) StorageHandler authorization providers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

StorageHandler authorization providers
--------------------------------------

                 Key: HIVE-2809
                 URL: https://issues.apache.org/jira/browse/HIVE-2809
             Project: Hive
          Issue Type: New Feature
    Affects Versions: 0.9.0
            Reporter: Enis Soztutar
            Assignee: Enis Soztutar


In this issue, we would like to discuss the possibility of supplementing the Hive authorization model with authorization at the storage level. As discussed in HIVE-1943, Hive should also check for operation permissions in hdfs and hbase, since otherwise, data and metadata can be in an inconsistent state or be orphaned. Going a step further, some of the setups might not need the full featured auth model by Hive, but want to rely on managing the permissions at the data layer. In this model, the metadata operations are checked first from hdfs/hbase and it is allowed only if they are allowed at the data layer. The semantics are documented at https://cwiki.apache.org/confluence/display/HCATALOG/Hcat+Security+Design. 

So, the goals of this issue are: 
 - Port storage handler specific authorization providers, and the StorageDelegationAuthorizationProvider from HCATALOG-245 and HCATALOG-260 to Hive. 
 - Keep current Hive's default authorization provider, and enable user to use this and/or the storage one. auth providers are already configurable.
 - Move the manual checks that had to be performed about authorization in Hcat to Hive, specifically:
  -- CREATE DATABASE/TABLE, ADD PARTITION statements does not call 
   HiveAuthorizationProvider.authorize() with the candidate objects, which means that
   we cannot do checks against defined LOCATION.
  -- HiveOperation does not define sufficient Privileges for most of the operations, 
    especially database operations. 
  -- For some of the operations, Hive SemanticAnalyzer does not add the changed 
    object as a WriteEntity or ReadEntity.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira