Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB51210376 for ; Tue, 3 Dec 2013 21:10:35 +0000 (UTC) Received: (qmail 66291 invoked by uid 500); 3 Dec 2013 21:10:35 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 66242 invoked by uid 500); 3 Dec 2013 21:10:35 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 66233 invoked by uid 500); 3 Dec 2013 21:10:35 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 66230 invoked by uid 99); 3 Dec 2013 21:10:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Dec 2013 21:10:35 +0000 Date: Tue, 3 Dec 2013 21:10:35 +0000 (UTC) From: "Thejas M Nair (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-5928) Add a hive authorization plugin api that does not assume privileges needed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838190#comment-13838190 ] Thejas M Nair commented on HIVE-5928: ------------------------------------- During this refactor, we need to explore how the existing access control statement update code can be re-used across both old and new authorization models. > Add a hive authorization plugin api that does not assume privileges needed > -------------------------------------------------------------------------- > > Key: HIVE-5928 > URL: https://issues.apache.org/jira/browse/HIVE-5928 > Project: Hive > Issue Type: Sub-task > Components: Authorization > Reporter: Thejas M Nair > > The existing HiveAuthorizationProvider interface implementations can be used to support custom authorization models. > But this interface limits the customization for these reasons - > 1. It has assumptions about the privileges required for an action. > 2. It does have not functions that you can implement for having custom ways of doing the actions of access control statements. > This jira proposes a new interface HiveBaseAuthorizationProvider that does not make assumptions of the privileges required for the actions. The authorize() functions will be equivalent of authorize(, ). It will also have functions that will be called from the access control statements. > The current HiveAuthorizationProvider will continue to be supported for backward compatibility. There will be a subclass of HiveBaseAuthorizationProvider that executes actions using this interface. -- This message was sent by Atlassian JIRA (v6.1#6144)