Creating a default directory for managed tables
You can specify a top-level directory for managed tables when creating a Hive database.
Create a default directory for managed tables only after limiting CREATE
DATABASE and ALTER DATABASE statements to users having the Admin role, which has
hive service user permissions. Permissions to the managed
directory must be limited to the
hive service user. In addition to
restricting permissions to the
hive user, you can further secure
managed tables using Ranger fine-grained permissions, such as row-level filtering
and column masking.
hive.metastore.warehouse.dirconfiguration property to give managed tables a common location for governance policies. The managed location designates a single root directory for all tenant tables, managed and external.
metastore.warehouse.tenant.colocation property to
true allows a common location for managed tables outside the warehouse
root directory, providing a tenant-based common root for setting quotas and other
policies. To set this property, in Cloudera Manager use the Hive on Tez safety valve
for hive-site.xml as described in the next topic.
Do not set LOCATION and MANAGEDLOCATION to the same file system path.
CREATE (DATABASE|SCHEMA) [IF NOT EXISTS] database_name [COMMENT database_comment] [LOCATION external_table_path] [MANAGEDLOCATION managed_table_directory_path] [WITH DBPROPERTIES (property_name=property_value, ...)];
ALTER (DATABASE|SCHEMA) database_name SET MANAGEDLOCATION [managed_table_directory_path];
Create a database mydatabase that specifies a top level directory named sales
for managed tables.
CREATE DATABASE mydatabase MANAGEDLOCATION '/warehouse/tablespace/managed/hive/sales';
Change the abc_sales database location to the same location as mydatabase.
ALTER DATABASE abc_sales SET MANAGEDLOCATION '/warehouse/tablespace/managed/hive/sales';
Configuring a table location outside the warehouse root directory
You need to know how to set the property that allows you to establish a common location for tables.
- In Cloudera Manager, click .
- In scope, click Hive on Tez (Service-Wide).
- In Hive Service Advanced Configuration Snippet (Safety Valve) for hive-site.xml, click +.
In Name, enter
In Value, enter
- Save changes.
- In Cloudera Manager Home, restart Hive on Tez.