manual.txt 24 KB

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