Enabling Hue Applications Using Cloudera Manager

Minimum Required Role: Configurator (also provided by Cluster Administrator, Full Administrator)

Most Hue applications are configured by default, based on the services you have installed. Cloudera Manager selects the service instance that Hue depends on. If you have more than one service, you may want to verify or change the service dependency for Hue. Also, if you add a service such as Sqoop 2 or Oozie after you have set up Hue, you need to set the dependency because it is not done automatically. To add a dependency:
  1. Go to the Hue service.
  2. Click the Configuration tab.
  3. Select Scope > Hue (Service-Wide).
  4. Select Category > Main.
  5. Select each service name Service property to set the dependency. Select none to remove the dependency.
  6. Click Save Changes to commit the changes.
  7. Restart the Hue service.

Enabling the Sqoop 2 Application

If you are upgrading Cloudera Manager from a release 4.6 or lower, you need to set the Hue dependency to enable the Sqoop 2 application.

Enabling the HBase Browser Application with doAs Impersonation

Minimum Required Role: Full Administrator

The Hue HBase application communicates through a proxy server called the HBase Thrift Server, which then forwards commands to HBase. Because Hue stands between the Thrift server and the actual user, all HBase operations appear to come from the hue user and not the actual user. To secure these interactions, you must do the following:
  • Ensure that users logged into Hue perform operations with their own privileges, and not those of the impersonating hue user.
  • Once Hue can impersonate other users, ensure that only the Hue server can send commands to the HBase Thrift server. To ensure this, use Kerberos to authenticate the hue user to the HBase Thrift server.
To enable the HBase browser application:
  1. Add the HBase Thrift Server role.
  2. If you have a Kerberos-enabled cluster, enable impersonation by configuring the following HBase properties:
    1. Select the HBase service.
    2. Click the Configuration tab.
    3. Select Scope > Service-Wide.
    4. Select Category > Security.
    5. For the HBase Thrift Authentication property, make sure it is set to one of the following values:
      • auth-conf: authentication, integrity and confidentiality checking
      • auth-int: authentication and integrity checking
      • auth: authentication only
    6. Select Category > Main.
    7. Check the Enable HBase Thrift Http Server and Enable HBase Thrift Proxy Users properties checkboxes.
    8. Click Save Changes to commit the changes.
  3. Enable TLS/SSL for the HBase Thrift Server.
  4. Configure Hue to point to the Thrift Server and to a valid HBase configuration directory:
    1. Select the Hue service.
    2. Click the Configuration tab.
    3. Select Scope > All.
    4. Select Category > Main.
    5. For the HBase Service property, make sure it is set to the HBase service for which you enabled the Thrift Server role (if you have more than one HBase service instance).
    6. In the HBase Thrift Server property, click the edit field and select the Thrift Server role for Hue to use.
    7. Select Category > Advanced.
    8. Locate the Hue Service Advanced Configuration Snippet (Safety Valve) for hue_safety_valve.ini property and add the following property: 
      [hbase]
hbase_conf_dir=/etc/hbase/conf
    9. Click Save Changes to commit the changes.

Enabling the Solr Search Application

To use the Solr Search application with Hue, you must update the URL for the Solr Server in the Hue Server advanced configuration snippet. In addition, if you are using parcels with CDH 4.3, you must register the "hue-search" application manually, or access will fail. See Deploying Solr with Hue for detailed instructions.