Cloudera Docs

Configuring Hive Metastore as a REST Catalog

To use the API endpoints provided by REST Catalog, you need to enable it in the Hive Metastore where it is deployed.

Ensure that your Cloudera Runtime is of 7.3.2 version or later in Management Console > Environments > ***YOUR-ENVIRONMENT*** > Data Lake)

  1. Log in to Cloudera Manager and click Clusters > Hive Metastore > Configuration.
  2. Search for Enable REST Catalog Service and enable it to set up the REST Catalog Service in Hive Metastore.
  3. If you use Cloudera Data Sharing with AWS Elastic MapReduce and AWS Athena notebook, add the region of AWS environment to the Hive Metastore configuration.
    1. Check your region in Cloudera Management Console > Environments > [***YOUR_ENVIRONMENT***] > Environment Details.
    2. If your region is different than the default us-west-2, go to Cloudera Manager > Clusters > Hive Metastore > Configuration > Hive Service Advanced Configuration Snippet (Safety Valve) for hive-site.xml .
    3. Add a property with your region. 
      <property><name>client.region</name><value>[***CLIENT_REGION_NAME***]</value></property>
  4. If you use Cloudera Data Sharing with Azure Data Lake Storage Gen2 (ADLS Gen2), configure the hierarchical namespace property in the Hive Metastore so that it does not attempt to auto-detect the ADLS Gen2 hierarchical namespace status. If this property is unset, namespace REST Catalog API calls fail with HTTP 500 and Invalid configuration value detected for fs.azure.account.hns.enabled.
    1. In Cloudera Manager, go to Clusters > Hive Metastore > Configuration and search for Hive Metastore Server Advanced Configuration Snippet (Safety Valve) for core-site.xml.
    2. Add the following property: 
      <property><name>fs.azure.account.hns.enabled</name><value>true</value></property>
  5. Save the changes and restart the Hive Metastore service.

Continue with Editing the Knox topologies.