开发者社区> 数据库> 正文



Where is my hue.ini?

  • CDH package: /etc/hue/conf/hue.ini

  • A tarball release: /usr/share/desktop/conf/hue.ini

  • Development version: desktop/conf/pseudo-distributed.ini

  • Cloudera Manager: CM generates all the hue.ini for you, so no hassle \"\" /var/run/cloudera-scm-agent/process/`ls -alrt /var/run/cloudera-scm-agent/process | grep HUE | tail -1 | awk ‘{print $9}’`/hue.ini


  # Host where HiveServer2 is running.


To point to another server, just replaced the host value by ‘’:


  # Host where HiveServer2 is running.

Note: Any line starting with a # is considered as a comment so is not used.

Note: The list of mis-configured services are listed on the /about/admin_wizard page.

Note: After each change in the ini file, Hue should be restarted to pick it up.

Note: In some cases, as explained in how to configure Hadoop for Hue documentation, the API of these services needs to be turned on and Hue set as proxy user.

Here are the main sections that you will need to update in order to have each service accessible in Hue:


This is required for listing or creating files. Replace localhost by the real address of the NameNode (usually http://localhost:50070).

Enter this in hdfs-site.xml to enable WebHDFS in the NameNode and DataNodes:

<< code="">property>

  << code="">name>dfs.webhdfs.enabledname>

  << code="">value>truevalue>


Configure Hue as a proxy user for all other users and groups, meaning it may submit a request on behalf of any other user. Add to core-site.xml:

<< code="">property>

  << code="">name>hadoop.proxyuser.hue.hostsname>

  << code="">value>*value>


<< code="">property>

  << code="">name>hadoop.proxyuser.hue.groupsname>

  << code="">value>*value>


Then, if the Namenode is on another host than Hue, don’t forget to update in the hue.ini:







      # Enter the filesystem uri



      # Use WebHdfs/HttpFs as the communication mechanism.

      # Domain should be the NameNode or HttpFs host.



The Resource Manager is often on http://localhost:8088 by default. The ProxyServer and Job History servers also needs to be specified. Then Job Browser will let you list and kill running applications and get their logs.







      # Enter the host on which you are running the ResourceManager



      # Whether to submit jobs to this cluster



      # URL of the ResourceManager API



      # URL of the ProxyServer API



      # URL of the HistoryServer API



Here we need a running HiveServer2 in order to send SQL queries.



  # Host where HiveServer2 is running.


If HiveServer2 is on another machine and you are using security or customized HiveServer2 configuration, you will need to copy the hive-site.xml on the Hue machine too:



  # Host where HiveServer2 is running.



  # Hive configuration directory, where hive-site.xml is located


Solr Search

We just need to specify the address of a Solr Cloud (or non Cloud Solr), then interactive dashboards capabilities are unleashed!



  # URL of the Solr Server



An Oozie server should be up and running before submitting or monitoring workflows.



  # The URL where the Oozie service runs on.



The HBase app works with a HBase Thrift Server version 1. It lets you browse, query and edit HBase tables.


  # Comma-separated list of HBase Thrift server 1 for clusters in the format of '(name|host:port)'.


本文转自 yntmdr 51CTO博客,原文链接:,如需转载请自行联系原作者


+ 订阅