E-MapReduce currently supports Hue, which you can access through Apache Knox. The following section provides an overview of how to use Hue.

Preparation

In the Security groups cluster, set the security group rules, and open port 8888.

Notice Set security group rules for limited IP ranges. IP 0.0.0.0/0 is not allowed to add into the security group.

Access Hue

To access Hue, complete the following steps:

  1. In the EMR console, click Manage to the right of the cluster ID.
  2. On the left side of the Configuration page, click Access Links and Ports.

View the password

If Hue does not have an administrator after the first running, the first user to log on is set automatically to administrator. For security, E-MapReduce generates an administrator account and password by default. The administrator account is admin. To view the password, complete the following steps:

  1. Click Manage to the right of the cluster ID.
  2. In the Clusters and Services panel, click Hue.
  3. Click the Configuration tab to go to the admin_pwd parameter. It is a random password.

Create a new account if you forget your password

If you forget your password for your Hue account, you can create a new account by completing the following steps:

  1. In the cluster list page, click Manage next to the target cluster.
  2. In the navigation panel on the left, click Cluster Overview.
  3. In the Core Instance Group, obtain the public network IPs of some master nodes.
  4. Log on to the master node through SSH.
  5. Execute the following command:
    /opt/apps/hue/build/env/bin/hue createsuperuser
  6. Enter a new user name, e-mail, and password, and press Enter.

    If Superuser created successfully is displayed, you have successfully created a new account. You can now log on to Hue with the new account.

Add or modify a configuration

  1. In the cluster list page, click Manage next to the target cluster.
  2. In the service list, click Hue, and then click the Configuration tab.
  3. In the upper-right corner of the page, click Custom Configuration, and configure the Key and Value fields. The key must adhere to the following specifications:
    $section_path.$real_key
    Note
    • $real_key is the actual key to be added, such as hive_server_host.
    • In the hue.ini file, you can view the $section_path before the $real_key.

      For example, if the hive_server_host belongs to the [beeswax] section, this means that the $section_path is beeswax. If this is the case, the key to be added is beeswax.hive_server_host.

    • If you need to modify the multilevel section [desktop] -> [[ldap]] -> [[[ldap_servers]]] -> [[[[users]]]] ->user_name_attr value in the hue.ini file, the key to be configured is desktop.ldap.ldap_servers.users.user_name_attr.