hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Update of "Hive/HiveWebInterface" by EdwardCapriolo
Date Wed, 04 Mar 2009 04:45:42 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The following page has been changed by EdwardCapriolo:
http://wiki.apache.org/hadoop/Hive/HiveWebInterface

------------------------------------------------------------------------------
  == Features ==
  
  === Schema Browsing ===
- An alternative to running 'show tables' or 'show extended tables' from the CLI is to use
the web based schema browser. The Hive MetaData is presented in a hierarchical manner allowing
you to start at the database level and click to get information about tables including the
SerDe, column names, and column types.
+ An alternative to running 'show tables' or 'show extended tables' from the CLI is to use
the web based schema browser. The Hive Meta Data is presented in a hierarchical manner allowing
you to start at the database level and click to get information about tables including the
SerDe, column names, and column types.
  
  === Detached query execution ===
  A power user issuing multiple hive queries simultaneously would have multiple CLI windows
open. The hive web interface manages the session on the web server, not from inside the CLI
window. This allows a user to start multiple queries and return to the web interface later
to check the status.
@@ -16, +16 @@

  === No local installation ===
  Any user with a web browser can work with Hive. This has the usual web interface benefits,
in particular remote users have less firewall/connectivity issues.
  
- == Administration == 
+ == Configuration ==
+ Hive Web Interface made its first appeareance in the 0.2 branch. If you have 2.0 or the
SVN trunk you already have it
+ 
+ 
+ You should not need to edit the defults for the Hive web interface. HWI uses:
  {{{
+ <property>
+   <name>hive.hwi.listen.host</name>
+   <value>0.0.0.0</value>
+   <description>This is the host address the Hive Web Interface will listen on</description>
+ </property>
+ 
+ <property>
+   <name>hive.hwi.listen.port</name>
+   <value>9999</value>
+   <description>This is the port the Hive Web Interface will listen on</description>
+ </property>
+ 
+ <property>
+   <name>hive.hwi.war.file</name>
+   <value>${HIVE_HOME}/lib/hive.war</value>
+   <description>This is the WAR file with the jsp content for Hive Web Interface</description>
+ <property>
+ }}}
+ === Startup ===
+ 
+ When initializing Hive with no arguments that CLI is invoked. Hive has an extension architecture
used to start other hive demons.
+ {{{
- /bin/hive --service hwi
+ bin/hive --service hwi
+ }}}
+ Java has no direct way of deamonizing. In a production environment you should create a wrapper
script.
+ {{{
+ nohup bin/hive --service hwi > /dev/null 2> /dev/null &
+ }}}
+ If you want help on the service invocation or list of parameters you can add
+ {{{
+ bin/hive --service hwi --help
  }}}
  
+ === Authentication ===
+ Hadoop currently uses environmental properties to determine user name and group vector.
Thus Hive and Hive Web Interface can not enforce more stringent security then Hadoop can.
When you first connect to the Hive Web Interface the user is prompted for a user name and
groups.  This feature was added to support instalations using different schedulers.
+ 
+ If you want to tighten up security you are going to need to patch the source Hive Session
Manager or you may be able to tweak the JSP to accomplish this.
+ 
+ == Tips and tricks ==
+ 
+ === Result file ===
+ The result file is local to the web server. As a query that produces massive output should
set the result file to /dev/null.
+ 
+ === Debug Mode ===
+ The debug mode is used when the user is interested in having the result file not only contain
the result of the hive query but the other messages.
+ 
+ === Set Processor ===
+ In the CLI a command like 'SET x=5' is not processed by the the Query Processor it is processed
by
+ the Set Processor. Use the form 'x=5' not 'set x=5' 
+ 
+ == Walk through ==
+ === Authorize ===
+ attachment:1_hwi_authorize.png
+ attachment:2_hwi_authorize.png
+ === Schema Browser ===
+ attachment:3_schema_table.png
+ attachment:4_schema_browser.png
+ === Diagnostics ===
+ attachment:5_diagnostic.png
+ === Running a query ===
+ attachment:6_newsession.png
+ attachment:7_session_runquery.png
+ attachment:8_session_query_1.png
+ attachment:9_file_view.png
+ 

Mime
View raw message