hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-7648) authorization check api should provide table for create table,drop/create index, and db for create/switch db
Date Tue, 12 Aug 2014 17:43:13 GMT

     [ https://issues.apache.org/jira/browse/HIVE-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thejas M Nair updated HIVE-7648:
--------------------------------

    Description: 
For create table, the Authorizer.checkPrivileges call provides only the database name. If
the table name is passed, it will be possible for the authorization api implementation to
appropriately set the permissions of the new table.
Similarly, in case of create-database, the api call should provide database object for the
database being created.

For create and drop index, the underlying table information also should be passed.
For "use db;" , the database information should be passed.


  was:
For create table, the Authorizer.checkPrivileges call provides only the database name. If
the table name is passed, it will be possible for the authorization api implementation to
appropriately set the permissions of the new table.
Similarly, in case of create-database, the api call should provide database object for the
database being created.



> authorization check api should provide table for create table,drop/create index, and
db for create/switch db
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-7648
>                 URL: https://issues.apache.org/jira/browse/HIVE-7648
>             Project: Hive
>          Issue Type: Bug
>          Components: Authorization
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>         Attachments: HIVE-7648.1.patch, HIVE-7648.2.patch, HIVE-7648.3.patch
>
>
> For create table, the Authorizer.checkPrivileges call provides only the database name.
If the table name is passed, it will be possible for the authorization api implementation
to appropriately set the permissions of the new table.
> Similarly, in case of create-database, the api call should provide database object for
the database being created.
> For create and drop index, the underlying table information also should be passed.
> For "use db;" , the database information should be passed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message