Provides a self-service analytical workbench to run alongside Hadoop.
- misc ›
HUE is an analytical workbench for lightweight Business Intelligence (BI).
It provides an overlay to Hadoop to make finding and querying data quick
and easy. HUE stands for Hadoop User Experience. Hadoop can be thought of as a
set of open source programs and procedures (essentially, they are free for
anyone to use or modify, with a few exceptions) which anyone can use as the
"backbone" of their big data operations.
Features of Hue
- Allows easy finding of data. Users can browse and search for datasets within an organisation from within the Hue workbench/dashboard.
- Querying the data. Advanced users can leverage the smart query editor while less technical users have sets of discoverable queries and presentations available which can be modified for their individual use.
- Getting results from the data. Results from the queries can very easily be charted and pasted into whatever application or report required.
To deploy this charm simply run:
juju deploy cs:~spiculecharms/bundle/anssr-hadoop juju deploy cs:~spicule/hue juju add-relation hue hadoop-plugin juju expose hue
To add MySQL connectivity simply run:
juju deploy cs:mysql juju add-relation hue mysql
If you are running a Hadoop setup, you can also test the HDFS connectivity.
juju add-relation hue namenode
This will add a datasource entry for your Hadoop namenode. You can then query CSV/JSON/Parquet files.
Scale out Usage
Known Limitations and Issues
Currently, if Hue is run without a database software relation such as MySQL of Postgres then a bunch of error messages appear upon opening Hue from the Juju GUI.
- Contact: email@example.com
If you require commercial support for this charm or Hue, please contact us and we'd be happy to help. Email us at firstname.lastname@example.org and we can arrange a call to discuss your requirements.
- (boolean) A short description of the configuration option
- (string) Space separated list of extra deb packages to install.
- (string) List of signing keys for install_sources package sources, per charmhelpers standard format (a yaml list of strings encoded as a string). The keys should be the full ASCII armoured GPG public keys. While GPG key ids are also supported and looked up on a keyserver, operators should be aware that this mechanism is insecure. null can be used if a standard package signing key is used that will already be installed on the machine, and for PPA sources where the package signing key is securely retrieved from Launchpad.
- (string) List of extra apt sources, per charm-helpers standard format (a yaml list of strings encoded as a string). Each source may be either a line that can be added directly to sources.list(5), or in the form ppa:<user>/<ppa-name> for adding Personal Package Archives, or a distribution component to enable.
- (int) A short description of the configuration option
- (string) The status of service-affecting packages will be set to this value in the dpkg database. Valid values are "install" and "hold".
- (string) A short description of the configuration option
- Default Value