How to Enable Hive's Strict Mode Configuration and Metastore Authorization Configuration after Upgrade to BDA 3.* from BDA 2.* (Doc ID 1916565.1)

Last updated on AUGUST 12, 2014

Applies to:

Big Data Appliance Integrated Software - Version 3.0.1 and later
x86_64

Goal

In BDA V2.*/CDH 4.*  releases the the CM Hive service:  "Service Configuration Safety Valve for hive-site.xml" property is used to enable Hive's strict mode setting and enable Hive's metastore authorization storage checks with the following configuration update:

 

<property>
  <name>hive.mapred.mode</name>
  <value>strict</value>
  <description>The mode in which the hive operations are being performed. In strict mode, some risky queries are not allowed to run</description>
</property>

<property>
<name>hive.metastore.authorization.storage.checks</name>
<value>true</value>
<description>Should the metastore do authorization checks against the underlying storage for operations like drop-partition (disallow the drop-partition if the user in question doesn't have permissions to delete the corresponding directory on the storage).</description>
</property>
 

After upgrading to BDA 3.* / CDH 5.* Hive's "Service Configuration Safety Valve for hive-site.xml" property is no longer present. 

The goal here is to define what configuration can be used in to specify these properties in BDA 3.* / CDH 5.*.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms