manual.txt 23 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667
  1. Hue Tarball Installation Guide
  2. ==============================
  3. == Introduction
  4. Hue is a graphical user interface to operate and develop applications for
  5. Apache Hadoop. Hue applications are collected into a desktop-style environment
  6. and delivered as a Web application, requiring no additional installation for
  7. individual users.
  8. This guide describes how to install and configure a Hue tarball. For
  9. information about installing Hue packages, see
  10. https://wiki.cloudera.com/display/DOC/Hue+Installation[Installing Hue].
  11. There is also a companion SDK guide that describes how to develop
  12. new Hue applications:
  13. http://archive.cloudera.com/cdh3/hue/sdk/sdk.html[Hue SDK Documentation]
  14. IMPORTANT: Hue requires the Hadoop contained in Cloudera's Distribution for
  15. Apache Hadoop (CDH), version 3 Beta 4.
  16. .Conventions Used in this Guide:
  17. * Commands that must be run with +root+ permission have a +#+ command prompt.
  18. * Commands that do not require +root+ permission have a +$+ command prompt.
  19. == Hue Installation Instructions
  20. The following instructions describe how to install the Hue tarball on a
  21. multi-node cluster. You must install CDH first and update some
  22. Hadoop configuration files before installing Hue.
  23. IMPORTANT: You'll need to install the Hue plugins
  24. on _every_ machine that's running Hadoop daemons.
  25. === Install Hadoop from CDH3
  26. To use Hue, you must install and run Hadoop from CDH3 Beta 4 or later. If you
  27. are not running this version of CDH or later, upgrade your cluster before
  28. proceeding.
  29. === Install Hue
  30. Hue consists of a web service that runs on a special node in your cluster.
  31. Choose one node where you want to run Hue. This guide refers to that node as
  32. the _Hue Server_. For optimal performance, this should be one of the nodes
  33. within your cluster, though it can be a remote node as long as there are no
  34. overly restrictive firewalls. For small clusters of less than 10 nodes,
  35. you can use your existing master node as the Hue Server.
  36. You can download the Hue tarball here:
  37. http://github.com/cloudera/hue/downloads/
  38. ==== Hue Dependencies
  39. Hue employs some Python modules which use native code and requires
  40. certain development libraries be installed on your system. To install from the
  41. tarball, you must have the following installed:
  42. .Required Dependencies
  43. [grid="rows"]
  44. ``~
  45. Redhat,Debian
  46. ~~~~~~~~~~
  47. gcc,gcc
  48. libxml2-devel,libxml2-dev
  49. libxslt-devel,libxslt-dev
  50. cyrus-sasl-devel,libsasl2-dev
  51. mysql-devel,libmysqlclient-dev
  52. python-devel,python-dev
  53. python-setuptools,python-setuptools
  54. python-simplejson,python-simplejson
  55. sqlite-devel,libsqlite3-dev
  56. ant,ant
  57. ~~~~~~~~~~
  58. ==== Build
  59. Configure `$HADOOP_HOME` and `$PREFIX` with the path of your Hadoop
  60. installation and the path where you want to install Hue by running:
  61. ----
  62. $ HADOOP_HOME=/path/to/hadoop-0.20 PREFIX=/path/to/install/into make install
  63. ----
  64. You can install Hue anywhere on your system - it does not need root permission
  65. although additional third-party SDK applications may.
  66. It is a good practice to create a new user for Hue and either install Hue in
  67. that user's home directory, or in a directory within `/usr/local`.
  68. ==== Install Hadoop Plugins
  69. In order to communicate with Hadoop, Hue requires a plugin jar that you must
  70. install and configure. This jar is:
  71. `desktop/libs/hadoop/java-lib/hue-plugins-*.jar`
  72. relative to the Hue installation directory.
  73. Run these commands to create a symlink your Hadoop lib directory
  74. (`/usr/lib/hadoop-0.20/lib` if you installed CDH via a Debian or RPM package)
  75. to this jar:
  76. ----
  77. $ cd /usr/lib/hadoop/lib
  78. $ ln -s /usr/local/hue/desktop/libs/hadoop/java-lib/hue*jar .
  79. # Restart Hadoop
  80. ----
  81. NOTE: On a multi-node cluster, you must install the plugin jar on every
  82. node. You do not need to install all of the Hue components on every node.
  83. ==== Restart Hadoop
  84. After making the changes in your Hadoop configuration, restart the
  85. Hadoop daemons:
  86. ----
  87. # /etc/init.d/hadoop-0.20-datanode restart
  88. # /etc/init.d/hadoop-0.20-namenode restart
  89. # /etc/init.d/hadoop-0.20-jobtracker restart
  90. # /etc/init.d/hadoop-0.20-secondarynamenode restart
  91. # /etc/init.d/hadoop-0.20-tasktracker restart
  92. ----
  93. ==== Starting Hue
  94. To start Hue, use `build/env/bin/supervisor`. This will start
  95. several subprocesses, corresponding to the different Hue components.
  96. ==== Troubleshooting the Hue Tarball Installation
  97. .Q: I moved my Hue installation from one directory to another and now Hue no
  98. longer functions correctly.
  99. A: Due to the use of absolute paths by some Python packages, you must run a
  100. series of commands if you move your Hue installation. In the new location, run:
  101. ----
  102. $ rm app.reg
  103. $ rm -r build
  104. $ make apps
  105. ----
  106. .Q: Why does "make install" compile other pieces of software?
  107. A: In order to ensure that Hue is stable on a variety of distributions and
  108. architectures, it installs a Python virtual environment which includes its
  109. dependencies. This ensures that the software can depend on specific versions
  110. of various Python libraries and you don't have to be concerned about missing
  111. software components.
  112. === Configuring Hadoop for Hue
  113. Hue requires that you install and configure some plugins in your
  114. Hadoop installation. In order to enable the plugins, you must make some
  115. small additions to your configuration files. Make these configuration changes
  116. on each node in your cluster by editing the following files
  117. in: `/etc/hadoop-0.20/conf/`
  118. ==== `hdfs-site.xml`
  119. Add the following configuration properties to `hdfs-site.xml`:
  120. ----
  121. <property>
  122. <name>dfs.namenode.plugins</name>
  123. <value>org.apache.hadoop.thriftfs.NamenodePlugin</value>
  124. <description>Comma-separated list of namenode plugins to be activated.
  125. </description>
  126. </property>
  127. <property>
  128. <name>dfs.datanode.plugins</name>
  129. <value>org.apache.hadoop.thriftfs.DatanodePlugin</value>
  130. <description>Comma-separated list of datanode plugins to be activated.
  131. </description>
  132. </property>
  133. <property>
  134. <name>dfs.thrift.address</name>
  135. <value>0.0.0.0:10090</value>
  136. </property>
  137. -----
  138. ==== `mapred-site.xml`
  139. Add the following configuration properties to mapred-site.xml:
  140. ----
  141. <property>
  142. <name>jobtracker.thrift.address</name>
  143. <value>0.0.0.0:9290</value>
  144. </property>
  145. <property>
  146. <name>mapred.jobtracker.plugins</name>
  147. <value>org.apache.hadoop.thriftfs.ThriftJobTrackerPlugin</value>
  148. <description>Comma-separated list of jobtracker plugins to be activated.
  149. </description>
  150. </property>
  151. ----
  152. ==== `hadoop-metrics.properties`
  153. To enable full monitoring in the Health application, the metrics
  154. contexts must not be NullContext. You can configure `hadoop-metrics.properties`
  155. as shown below:
  156. ----
  157. # Exposes /metrics URL endpoint for metrics information.
  158. dfs.class=org.apache.hadoop.metrics.spi.NoEmitMetricsContext
  159. mapred.class=org.apache.hadoop.metrics.spi.NoEmitMetricsContext
  160. jvm.class=org.apache.hadoop.metrics.spi.NoEmitMetricsContext
  161. rpc.class=org.apache.hadoop.metrics.spi.NoEmitMetricsContext
  162. ----
  163. === Further Hadoop Configuration and Caveats
  164. ==== `HADOOP_CLASSPATH` Caveat
  165. If you are setting `$HADOOP_CLASSPATH` in your `hadoop-env.sh`, be sure
  166. to set it in such a way that user-specified options are preserved. For example:
  167. Correct:
  168. ----
  169. # HADOOP_CLASSPATH=<your_additions>:$HADOOP_CLASSPATH
  170. ----
  171. Incorrect:
  172. ----
  173. # HADOOP_CLASSPATH=<your_additions>
  174. ----
  175. This enables certain components of Hue to add to
  176. Hadoop's classpath using the environment variable.
  177. ==== `hadoop.tmp.dir`
  178. If your users are likely to be submitting jobs both using Hue and from the
  179. same machine via the command line interface, they will be doing so as the `hue`
  180. user if they're using Hue and via their own user account on the command line.
  181. This leads to some contention on the directory specified by `hadoop.tmp.dir`,
  182. which defaults to `/tmp/hadoop-${user.name}`. Specifically, `hadoop.tmp.dir`
  183. is used to unpack jars in `bin/hadoop jar`. One work around to this is
  184. to set `hadoop.tmp.dir` to `/tmp/hadoop-${user.name}-${hue.suffix}` in the
  185. core-site.xml file:
  186. ----
  187. <property>
  188. <name>hadoop.tmp.dir</name>
  189. <value>/tmp/hadoop-${user.name}${hue.suffix}</value>
  190. </property>
  191. ----
  192. Unfortunately, when the variable is unset, you'll end up
  193. with directories named `/tmp/hadoop-user_name-${hue.suffix}` in
  194. `/tmp`. The job submission daemon, however, will still work.
  195. IMPORTANT: The Beeswax server writes into a local directory on the Hue machine
  196. that is specified by `hadoop.tmp.dir` to unpack its jars. That directory
  197. needs to be writable by the `hue` user, which is the default user who starts
  198. Beeswax Server, or else Beeswax server will not start. You may also make that
  199. directory world-writable.
  200. === Restart Your Hadoop Cluster
  201. Restart all of the daemons in your cluster so that the plugins can be loaded.
  202. You can confirm that the plugins are running correctly by tailing the daemon
  203. logs:
  204. ----
  205. $ tail --lines=500 /var/log/hadoop-0.20/hadoop*namenode*.log | grep ThriftPlugin
  206. 2009-09-28 16:30:44,337 INFO org.apache.hadoop.thriftfs.ThriftPluginServer: Starting Thrift server
  207. 2009-09-28 16:30:44,419 INFO org.apache.hadoop.thriftfs.ThriftPluginServer:
  208. Thrift server listening on 0.0.0.0:10090
  209. ----
  210. [TIP]
  211. .Configuring Your Firewall for Hue
  212. ============================================================
  213. Hue currently requires that the machines within your cluster can connect to
  214. each other freely over TCP. The machines outside your cluster must be able to
  215. open TCP port 8088 on the Hue Server to interact with the system.
  216. ============================================================
  217. == Configuring Hue
  218. Hue ships with a default configuration that will work for
  219. pseudo-distributed clusters. If you are running on a real cluster, you must
  220. make a few changes to the `/etc/hue/hue.ini` configuration file. The
  221. following sections describe the key configuration options you must make to
  222. configure Hue.
  223. [TIP]
  224. .Listing all Configuration Options
  225. ============================================================
  226. To list all available configuration options, run:
  227. ----
  228. /usr/share/hue/build/env/bin/hue config_help | less
  229. ----
  230. This commands outlines the various sections and options in the configuration,
  231. and provides help and information on the default values.
  232. ============================================================
  233. [TIP]
  234. .Viewing Current Configuration Options
  235. ============================================================
  236. To view the current configuration from within Hue, open:
  237. ----
  238. http://<hue>/dump_config
  239. ----
  240. ============================================================
  241. [TIP]
  242. .Using Multiple Files to Store Your Configuration
  243. ============================================================
  244. Hue loads and merges all of the files with extension `.ini`
  245. located in the `/etc/hue/conf/` directory. Files that are alphabetically later
  246. take precedence.
  247. ============================================================
  248. === Web Server Configuration
  249. Hue uses the CherryPy web server. You can use the following options to
  250. change the IP address and port that the web server listens on. The default
  251. setting is port 8088 on all configured IP addresses.
  252. ----
  253. # Webserver listens on this address and port
  254. http_host=0.0.0.0
  255. http_port=8088
  256. ----
  257. ==== Specifying the Secret Key
  258. For security, you should also specify the secret key that is used for secure
  259. hashing in the session store.
  260. Open the `/etc/hue/hue.ini` configuration file. In the `desktop` section, enter
  261. a long series of random characters (30 to 60 characters is recommended).
  262. ----
  263. [desktop]
  264. secret_key=jFE93j;2[290-eiw.KEiwN2s3['d;/.q[eIW^y#e=+Iei*@Mn<qW5o
  265. ----
  266. NOTE: If you don't specify a secret key, your session cookies will not be
  267. secure. Hue will run but it will also display error messages telling you to
  268. set the secret key.
  269. === Authentication
  270. By default, the first user who logs in to Hue can choose any
  271. username and password and becomes an administrator automatically. This
  272. user can create other user and administrator accounts. User information is
  273. stored in the Django database in the Django backend.
  274. The authentication system is pluggable. For more information, see the
  275. http://archive.cloudera.com/cdh3/hue/sdk/sdk.html[Hue SDK Documentation].
  276. === Configuring Hue for SSL
  277. You can configure Hue to serve over HTTPS. To do so, you must install
  278. "pyOpenSSL" within Hue's context and configure your keys.
  279. To install `pyOpenSSL`, from the root of your Hue installation path,
  280. do the following steps:
  281. 1. Run this command:
  282. ----
  283. $ ./build/env/bin/easy_install pyOpenSSL
  284. ----
  285. 2. Configure Hue to use your private key by adding the following
  286. options to the `/etc/hue/hue.ini` configuration file:
  287. ----
  288. ssl_certificate=/path/to/certificate
  289. ssl_private_key=/path/to/key
  290. ----
  291. 3. Ideally, you would have an appropriate key signed by a Certificate Authority.
  292. If you're just testing, you can create a self-signed key using the `openssl`
  293. command that may be installed on your system:
  294. ----
  295. # Create a key
  296. $ openssl genrsa 1024 > host.key
  297. # Create a self-signed certificate
  298. $ openssl req -new -x509 -nodes -sha1 -key host.key > host.cert
  299. ----
  300. [NOTE]
  301. .Self-signed Certificates and File Uploads
  302. ============================================================
  303. To upload files using the Hue File Browser over HTTPS requires
  304. using a proper SSL Certificate. Self-signed certificates don't
  305. work.
  306. ============================================================
  307. === Pointing Hue to Your Master Nodes
  308. If your Hadoop cluster contains multiple nodes, you should configure
  309. Hue to point to the external hostnames of your NameNode and
  310. JobTracker. To do so, change the `namenode_host` and `jobtracker_host`
  311. lines in the `/etc/hue/hue.ini` configuration file. Refer to the inline comments
  312. in the configuration file for more information.
  313. == Starting Hue from the Tarball
  314. After your cluster is running with the plugins enabled, you can start Hue on
  315. your Hue Server by running:
  316. ----
  317. # build/env/bin/supervisor
  318. ----
  319. Your Hue installation is now running.
  320. == Administering Hue
  321. Now that you've installed and started Hue, you can feel free to skip ahead
  322. to the <<usage,Using Hue>> section. Administrators may want to refer to this
  323. section for more details about managing and operating a Hue installation.
  324. === Hue Processes
  325. ==== Process Hierarchy
  326. A script called `supervisor` manages all Hue processes. The supervisor is a
  327. watchdog process -- its only purpose is to spawn and monitor other processes.
  328. A standard Hue installation starts and monitors the following processes:
  329. * `runcpserver` - a web server based on CherryPy that provides the core web
  330. functionality of Hue
  331. * `jobsubd` - a daemon which handles submission of jobs to Hadoop
  332. * `beeswax server` - a daemon that manages concurrent Hive queries
  333. If you have installed other applications into your Hue instance, you may see
  334. other daemons running under the supervisor as well.
  335. You can see the supervised processes running in the output of `ps -f -u hue`:
  336. ------------------
  337. UID PID PPID C STIME TTY TIME CMD
  338. hue 8685 8679 0 Aug05 ? 00:01:39 /usr/share/hue/build/env/bin/python /usr/share/hue/build/env/bin/desktop runcpserver
  339. hue 8693 8679 0 Aug05 ? 00:00:01 /usr/share/hue/build/env/bin/python /usr/share/hue/build/env/bin/desktop jobsubd
  340. hue 8695 8679 0 Aug05 ? 00:00:06 /usr/java/jdk1.6.0_14/bin/java -Xmx1000m -Dhadoop.log.dir=/usr/lib/hadoop-0.20/logs -Dhadoop.log.file=hadoop.log ...
  341. ------------------
  342. Note that the supervisor automatically restarts these processes if they fail for
  343. any reason. If the processes fail repeatedly within a short time, the supervisor
  344. itself shuts down.
  345. === Hue Logging
  346. The Hue logs are found in `/var/log/hue`. Inside the log directory you can find:
  347. * An `access.log` file, which contains a log for all requests against the Hue
  348. web server.
  349. * A `supervisor.log` file, which contains log information for the supervisor
  350. process.
  351. * A `supervisor.out` file, which contains the stdout and stderr for the
  352. supervisor process.
  353. * A `.log` file for each supervised process described above, which contains
  354. the logs for that process.
  355. * A `.out` file for each supervised process described above, which contains
  356. the stdout and stderr for that process.
  357. If users on your cluster have problems running Hue, you can often find error
  358. messages in these log files. If you are unable to start Hue from the init
  359. script, the `supervisor.log` log file can often contain clues.
  360. ==== Viewing Recent Log Messages through your Web Browser
  361. In addition to logging `INFO` level messages to the `logs` directory, the Hue
  362. web server keeps a small buffer of log messages at all levels in memory. You can
  363. view these logs by visiting `http://myserver:8088/logs`. The `DEBUG` level
  364. messages shown can sometimes be helpful in troubleshooting issues.
  365. === The Hue Database
  366. Hue requires a SQL database to store small amounts of data, including user
  367. account information as well as history of job submissions and Hive queries.
  368. By default, Hue is configured to use the embedded database SQLite for this
  369. purpose, and should require no configuration or management by the administrator.
  370. However, MySQL is the recommended database to use; this section contains
  371. instructions for configuring Hue to access MySQL and other databases.
  372. ==== Inspecting the Hue Database
  373. The default SQLite database used by Hue is located in:
  374. `/usr/share/hue/desktop/desktop.db`.
  375. You can inspect this database from the command line using the `sqlite3`
  376. program. For example:
  377. ---------
  378. # sqlite3 /usr/share/hue/desktop/desktop.db
  379. SQLite version 3.6.22
  380. Enter ".help" for instructions
  381. Enter SQL statements terminated with a ";"
  382. sqlite> select username from auth_user;
  383. admin
  384. test
  385. sample
  386. sqlite>
  387. ----------
  388. It is strongly recommended that you avoid making any modifications to the
  389. database directly using SQLite, though this trick can be useful for management
  390. or troubleshooting.
  391. ==== Backing up the Hue Database
  392. If you use the default SQLite database, then copy the `desktop.db` file to
  393. another node for backup. It is recommended that you back it up on a regular
  394. schedule, and also that you back it up before any upgrade to a new version of
  395. Hue.
  396. ==== Configuring Hue to Access Another Database
  397. Although SQLite is the default database type, some advanced users may prefer
  398. to have Hue access an alternate database type. Note that if you elect to
  399. configure Hue to use an external database, upgrades may require more manual
  400. steps in the future.
  401. The following instructions are for MySQL, though you can also configure Hue to
  402. work with other common databases such as PostgreSQL and Oracle.
  403. [NOTE]
  404. .Tested Database Backends
  405. ============================================================
  406. Note that Hue has only been tested with SQLite and MySQL database backends.
  407. ============================================================
  408. ===== Configuring Hue to Store Data in MySQL
  409. To configure Hue to store data in MySQL:
  410. 1. Create a new database in MySQL and grant privileges to a Hue user to manage
  411. this database.
  412. ----
  413. mysql> create database hue;
  414. Query OK, 1 row affected (0.01 sec)
  415. mysql> grant all on hue.* to 'hue'@'localhost' identified by 'secretpassword';
  416. Query OK, 0 rows affected (0.00 sec)
  417. ----
  418. 2. Shut down Hue if it is running.
  419. 3. To migrate your existing data to MySQL, use the following command to dump the
  420. existing database data to a text file. Note that using the ".json" extension
  421. is required.
  422. ----
  423. $ /usr/share/hue/build/env/bin/hue dumpdata > <some-temporary-file>.json
  424. ----
  425. 4. Open the `/etc/hue/hue.ini` file in a text editor. Directly below the
  426. `[[database]]` line, add the following options (and modify accordingly for
  427. your MySQL setup):
  428. ----
  429. host=localhost
  430. port=3306
  431. engine=mysql
  432. user=hue
  433. password=secretpassword
  434. name=hue
  435. ----
  436. 5. Install the Python drivers for MySQL into Hue's environment:
  437. ----
  438. # su - hue -s /bin/bash
  439. $ /usr/share/hue/build/env/bin/easy_install MySQL-python
  440. ----
  441. `easy_install` will access the Internet to find MySQL-python.
  442. If you don't have network access, you may specify a path
  443. to a tarball (such as `/tmp/MySQL-python-1.2.2.tar.gz`) instead.
  444. 6. As the Hue user, configure Hue to load the existing data and create the
  445. necessary database tables:
  446. ----
  447. $ /usr/share/hue/build/env/bin/hue syncdb --noinput
  448. $ mysql -uhue -psecretpassword -e "DELETE FROM hue.django_content_type;"
  449. $ /usr/share/hue/build/env/bin/hue loaddata <temporary-file-containing-dumped-data>.json
  450. ----
  451. Your system is now configured and you can start the Hue server as normal.
  452. == Hue Applications
  453. This section includes documentation specific to built-in Hue applications.
  454. === Beeswax, the Hive UI
  455. ==== Introduction
  456. Beeswax is an application that is a component within Hue that helps you use
  457. Hive to query your data.
  458. ==== Installation
  459. Beeswax is installed as part of Hue.
  460. ==== Hive Configuration
  461. Beeswax, the Hive interface in Hue, includes Hive 0.7. You do
  462. not need an existing Hive installation.
  463. Your Hive data is stored in HDFS, normally under `/user/hive/warehouse`
  464. (or any path you specify as `hive.metastore.warehouse.dir` in your
  465. `hive-site.xml`). Make sure this location exists and is writable by
  466. the users whom you expect to be creating tables. `/tmp` (on the local file
  467. system) must be world-writable, as Hive makes extensive use of it.
  468. [NOTE]
  469. If you used the embedded Hive MetaStore functionality of Beeswax in Hue from
  470. versions prior to Hue 1.2, read this section. Hue 1.2 includes changes in the
  471. Hive MetaStore schema that are part of the Hive 0.7 release. If you want to use
  472. Beeswax in Hue 1.2, it is imperative that you upgrade the Hive MetaStore schema
  473. by running the appropriate schema upgrade script located in the
  474. apps/beeswax/hive/scripts/metastore/upgrade directory in the Hue installation.
  475. Scripts for Derby and MySQL databases are available. If you are using a
  476. different database for your MetaStore, you will need to provide your own
  477. upgrade script.
  478. ==== Configuration
  479. ===== No Existing Hive Installation
  480. Familiarize yourself with the configuration options in
  481. `hive-site.xml` (see
  482. http://wiki.apache.org/hadoop/Hive/AdminManual/Configuration).
  483. Having a `hive-site.xml` is optional but often useful, particularly on setting
  484. up a http://wiki.apache.org/hadoop/Hive/AdminManual/MetastoreAdmin[metastore].
  485. You may store the `hive-site.xml` in `/etc/hue/conf`, or instruct
  486. Beeswax to locate it using the `hive_conf_dir` configuration variable. See
  487. `/etc/hue/conf/hue-beeswax.ini`.
  488. ===== Existing Hive Installation
  489. In `/etc/hue/conf/hue-beeswax.ini`, modify `hive_conf_dir` to point to the
  490. directory containing `hive-site.xml`.
  491. [[usage]]
  492. == Using Hue
  493. After installation, you can use Hue by navigating to `http://myserver:8088/`.
  494. The following login screen appears:
  495. image:images/login.png[]
  496. Launch applications on the bottom-right.
  497. image:images/open-apps.png[,width=50%]
  498. The Help application guides users through the various installed applications.
  499. === Supported Browsers
  500. Hue is primarily tested on Firefox 3.5 and Firefox 3.6, on Windows, Mac, and
  501. Linux. Google Chrome and Safari work as well.
  502. === Feedback
  503. Your feedback is welcome. The best way to send feedback is to join the
  504. https://groups.google.com/a/cloudera.org/group/hue-user[mailing list], and
  505. send e-mail, to mailto:hue-user@cloudera.org[hue-user@cloudera.org].
  506. === Reporting Bugs
  507. If you find that something doesn't work, it'll often be helpful to include logs
  508. from your server. These are available at the +/logs+ URL on Hue's web server
  509. (not part of the graphical Hue UI). Please download the logs as a zip (or cut
  510. and paste the ones that look relevant) and send those with your bug reports.
  511. image:images/logs.png[]