Browse Source

[doc] Removed old links, bad tables, updated graphics, new search doc.

Stephanie Bodoff 12 năm trước cách đây
mục cha
commit
2883d30

+ 1 - 2
docs/user-guide/about.md

@@ -47,8 +47,7 @@ settings are in the hue.ini configuration file.
 
 Click the tabs under **Configuration Sections and Variables** to see the
 settings configured for each application. For information on configuring
-these settings, see Hue Configuration in [CDH4
-Installation](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
+these settings, see Hue Configuration in the Hue installation manual.
 
 Server Logs
 -----------

+ 41 - 81
docs/user-guide/admin.md

@@ -42,61 +42,46 @@ superusers and users.
 2.  In the **Credentials** screen, add required information about the
     user. Once you provide the required information you can click the
     wizard step tabs to set other information.
-
-    **Username**
-
-    A user name that contains only letters, numbers, and underscores;
+    
+ <table>
+<tr><td>Username</td><td>  A user name that contains only letters, numbers, and underscores;
     blank spaces are not allowed and the name cannot begin with a
     number. The user name is used to log into Hue and in file
     permissions and job submissions. This is a required field.
-
-    **Password** and **Password confirmation**
-
-    A password for the user. This is a required field.
-
-    **Create home directory**
-
-    Indicate whether to create a directory named /user/username in HDFS.
+</td></tr>
+<tr><td>Password and Password confirmation</td><td>    A password for the user. This is a required field.</td></tr>
+<tr><td>Create home directory</td><td>   Indicate whether to create a directory named /user/username in HDFS.
     For non-superusers, the user and group of the directory are
     username. For superusers, the user and group are username and
-    supergroup.
+    supergroup.</td></tr></table>
+
+ 
 
 3.  Click **Add User** to save the information you specified and close
     the **Add User** wizard or click **Next**.
 4.  In the **Names and Groups** screen, add optional information.
 
-    **First name** and **Last name**
-
-    The user's first and last name.
-
-    **E-mail address**
-
-    The user's e-mail address. The e-mail address is used by the Job
+<table>
+<tr><td>First name and Last name</td><td> The user's first and last name.
+</td></tr>
+<tr><td>E-mail address</td><td>The user's e-mail address. The e-mail address is used by the Job
     Designer and Beeswax applications to send users an e-mail message
     after certain actions have occurred. The Job Designer sends an
     e-mail message after a job has completed. Beeswax sends a message
     after a query has completed. If an e-mail address is not specified,
-    the application will not attempt to email the user.
-
-    **Groups**
-
-    The groups to which the user belongs. By default, a user is assigned
+    the application will not attempt to email the user.</td></tr>
+<tr><td>Groups</td><td> The groups to which the user belongs. By default, a user is assigned
     to the **default** group, which allows access to all applications.
-    See [Managing Application Permissions](#topic_11_4).
+    See [Managing Application Permissions](#topic_11_4).</td></tr></table>
+    
 
 5.  Click **Add User** to save the information you specified and close
     the **Add User** wizard or click **Next**.
 6.  In the **Advanced** screen, add status information.
 
-    **Active**
-
-    Indicate that the user is enabled and allowed to log in.
-
-    Default: checked.
-
-    **Superuser status**
-
-    Assign superuser privileges to the user.
+<table>
+<tr><td>Active</td><td> Indicate that the user is enabled and allowed to log in. Default: checked.</td></tr>
+<tr><td>Superuser status</td><td> Assign superuser privileges to the user.</td></tr></table>
 
 7.  Click **Add User** to save the information you specified and close
     the **Add User** wizard.
@@ -128,20 +113,14 @@ To add a user from an external LDAP directory:
 1.  Click **Add/sync LDAP user**.
 2.  Specify the user properties:
 
-    **Username**
-
-    The user name.
-
-    **Distinguished name**
-
-    Indicate that Hue should use a full distinguished name for the user.
+<table>
+<tr><td>Username</td><td>The user name.</td></tr>
+<tr><td>Distinguished name</td><td>Indicate that Hue should use a full distinguished name for the user.
     This imports the user's first and last name, username, and email,
-    but does not store the user password.
-
-    **Create home directory**
+    but does not store the user password.</td></tr>
+    <tr><td>Create home directory</td><td> Indicate that Hue should create a home directory for the user in
+    HDFS.</td></tr></table>
 
-    Indicate that Hue should create a home directory for the user in
-    HDFS.
 
 3.  Click **Add/sync user**.
 
@@ -177,19 +156,12 @@ import groups from an LDAP directory.
     Group**.
 2.  Specify the group properties:
 
-    **Name**
-
-    The name of the group. Group names can only be letters, numbers, and
-    underscores; blank spaces are not allowed.
-
-    **Members**
-
-    The users in the group. Check user names or check **Select all**.
-
-    **Permissions**
-
-    The applications the users in the group can access. Check
-    application names or check **Select all**.
+<table>
+<tr><td>Name</td><td> The name of the group. Group names can only be letters, numbers, and
+    underscores; blank spaces are not allowed.</td></tr>
+<tr><td>Members</td><td>The users in the group. Check user names or check Select all.</td></tr>
+    <tr><td>Permissions</td><td>The applications the users in the group can access. Check
+    application names or check Select all.</td></tr></table>
 
 3.  Click **Add group**.
 
@@ -212,27 +184,15 @@ import groups from an LDAP directory.
 1.  From the **Groups** tab, click **Add/sync LDAP group**.
 2.  Specify the group properties:
 
-    **Name**
-
-    The group name.
-
-    **Distinguished name**
-
-    Indicate that Hue should use a full distinguished name for the
-    group.
-
-    **Import new members**
-
-    Indicate that Hue should import the members of the group.
-
-    **Import new members from all subgroups**
-
-    Indicate that Hue should import the members of the subgroups.
-
-    **Create home directories**
-
-    Indicate that Hue should create home directories in HDFS for the
-    imported members.
+<table>
+<tr><td>Name</td><td> The name of the group.</td></tr>
+<tr><td>Distinguished name</td><td> Indicate that Hue should use a full distinguished name for the
+    group.</td></tr>
+    <tr><td>Import new members</td><td>  Indicate that Hue should import the members of the group.</td></tr>
+        <tr><td>Import new members from all subgroups</td><td>
+    Indicate that Hue should import the members of the subgroups.</td></tr>
+            <tr><td>Create home directories</td><td> Indicate that Hue should create home directories in HDFS for the
+    imported members.</td></tr></table>
 
 3.  Click **Add/sync group**.
 

+ 39 - 55
docs/user-guide/beeswax.md

@@ -16,15 +16,15 @@ Beeswax and Hive Installation and Configuration
 -----------------------------------------------
 
 Beeswax is installed and configured as part of Hue. For information
-about installing and configuring Hue, see Hue Installation in
-[http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
+about installing and configuring Hue, see the Hue Installation
+manual..
 
 Beeswax assumes an existing Hive installation. The Hue installation
 instructions include the configuration necessary for Beeswax to access
 Hive. You can view the current Hive configuration from the **Settings**
 tab in the Beeswax application.
 
-By default, a Beeswax user can see the saved queries for all users 
+By default, a Beeswax user can see the saved queries for all users -
 both his/her own queries and those of other Beeswax users. To restrict
 viewing saved queries to the query owner and Hue administrators, set the
 share\_saved\_queries property under the [beeswax] section in the Hue
@@ -155,80 +155,67 @@ MapReduce jobs that the query generated.
 The pane to the left of the Query Editor lets you specify the following
 options:
 
-**Option**
 
-**Description**
-
-**DATABASE**
-
-The database containing the table definitions.
-
-**SETTINGS**
-
-Override the Hive and Hadoop default settings. To configure a new
+<table>
+<tr><td>DATABASE</td><td>The database containing the table definitions.</td></tr>
+<tr><td>SETTINGS</td><td>Override the Hive and Hadoop default settings. To configure a new
 setting:
 
-1.  Click **Add**.
-2.  For **Key**, enter a Hive or Hadoop configuration variable name.
-3.  For **Value**, enter the value you want to use for the variable.
+<ol>
+<li> Click Add.
+<li> For Key, enter a Hive or Hadoop configuration variable name.
+<li> For Value, enter the value you want to use for the variable.
 
 For example, to override the directory where structured Hive query logs
-are created, you would enter hive.querylog.location for **Key**, and a
-path for **Value.**
+are created, you would enter hive.querylog.location for Key, and a
+path for Value.
+</ol>
 
-To view the default settings, click the **Settings** tab at the top of
+To view the default settings, click the Settings tab at the top of
 the page. For information about Hive configuration variables, see:
 [http://wiki.apache.org/hadoop/Hive/AdminManual/Configuration](http://wiki.apache.org/hadoop/Hive/AdminManual/Configuration).
 For information about Hadoop configuration variables, see:
-[http://hadoop.apache.org/docs/current/hadoop-mapreduce-client/hadoop-mapreduce-client-core/mapred-default.xml](http://hadoop.apache.org/docs/current/hadoop-mapreduce-client/hadoop-mapreduce-client-core/mapred-default.xml).
-
-**FILE RESOURCES**
-
-Make files locally accessible at query execution time available on the
+[http://hadoop.apache.org/docs/current/hadoop-mapreduce-client/hadoop-mapreduce-client-core/mapred-default.xml](http://hadoop.apache.org/docs/current/hadoop-mapreduce-client/hadoop-mapreduce-client-core/mapred-default.xml).</td></tr>
+<tr><td>FILE RESOURCES</td><td>Make files locally accessible at query execution time available on the
 Hadoop cluster. Hive uses the Hadoop Distributed Cache to distribute the
 added files to all machines in the cluster at query execution time.
 
-1.  Click **Add** to configure a new setting.
-2.  From the **Type** drop-down menu, choose one of the following:
-    -   **jar** — Adds the specified resources to the Java classpath.
-    -   **archive** — Unarchives the specified resources when
+<ol>
+<li>  Click Add to configure a new setting.
+<li>   From the Type drop-down menu, choose one of the following:
+<ul>
+   <li>jar - Adds the specified resources to the Java classpath.
+   <li>archive - Unarchives the specified resources when
         distributing them.
-    -   **file** — Adds the specified resources to the distributed
+    <li>file - Adds the specified resources to the distributed
         cache. Typically, this might be a transform script (or similar)
         to be executed.
 
-3.  For **Path**, enter the path to the file or click
+<li>   For Path, enter the path to the file or click
     ![image](images/browse.png) to browse and select the file.
+</ol>
 
-![image](images/note.jpg) **Note**: It is not necessary to specify files
+![image](images/note.jpg) Note: It is not necessary to specify files
 used in a transform script if the files are available in the same path
-on all machines in the Hadoop cluster.
-
-**USER-DEFINED FUNCTIONS**
+on all machines in the Hadoop cluster.</td></tr>
+<tr><td>USER-DEFINED FUNCTIONS</td><td>Specify user-defined functions. Click Add to configure a new
+setting. Specify the function name in the Name field, and specify
+the class name for Classname.
 
-Specify user-defined functions. Click **Add** to configure a new
-setting. Specify the function name in the **Name** field, and specify
-the class name for **Class** **name**.
-
-You *must* specify a JAR file for the user-defined functions in ****FILE
-RESOURCES****.
+You *must* specify a JAR file for the user-defined functions in FILE RESOURCES.
 
 To include a user-defined function in a query, add a $ (dollar sign)
 before the function name in the query. For example, if MyTable is a
-user-defined function name in the query, you would type: SELECT \*
-$MyTable
-
-**PARAMETERIZATION**
-
-Indicate that a dialog box should display to enter parameter values when
+user-defined function name in the query, you would type: SELECT $MyTable
+</td></tr>
+<tr><td>PARAMETERIZATION</td><td>Indicate that a dialog box should display to enter parameter values when
 a query containing the string $parametername is executed. Enabled by
-default.
-
-**EMAIL NOTIFICATION**
-
-Indicate that an email message should be sent after a query completes.
+default.</td></tr>
+<tr><td>EMAIL NOTIFICATION</td><td>Indicate that an email message should be sent after a query completes.
 The email is sent to the email address specified in the logged-in user's
-profile.
+profile.</td></tr>
+</table>
+
 
 ### Viewing Query History
 
@@ -252,9 +239,6 @@ Queries tab to display the respective queries or clicking **Saved
 Queries**. You can copy any query, but you can edit, delete, and view
 the history of only your own queries.
 
-Saved Query
-
-Procedure
 
 **Edit**
 

+ 2 - 16
docs/user-guide/filebrowser.md

@@ -21,9 +21,8 @@ File Browser Installation and Configuration
 -------------------------------------------
 
 File Browser is one of the applications installed as part of Hue. For
-information about installing and configuring Hue, see Hue Installation
-in
-[http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
+information about installing and configuring Hue, see the Hue Installation
+manual.
 
 Starting File Browser
 ---------------------
@@ -113,9 +112,6 @@ information on how to configure the HDFS trash folder, see Enabling
 Trash. in
 [http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
 
-Action
-
-Procedure
 
 **Open**
 
@@ -134,9 +130,6 @@ Procedure
 
 ### Renaming, Moving, Deleting, and Restoring Files and Directories
 
-Action
-
-Procedure
 
 **Rename**
 
@@ -184,10 +177,6 @@ Hue superuser account. If you create a Hue user (in User Admin) with the
 same user name and password as the Hadoop superuser, then that Hue user
 can change a file's or directory's owner, group, or permissions.
 
-Change
-
-Procedure
-
 **Owner or Group**
 
 1.  In the **File Browser** window, check the checkbox next to the
@@ -221,9 +210,6 @@ Viewing and Editing Files
 
 You can view and edit files as text or binary.
 
-Action
-
-Procedure
 
 **View**
 

BIN
docs/user-guide/images/applications.png


BIN
docs/user-guide/images/huearch.jpg


BIN
docs/user-guide/images/icon_search_24.png


BIN
docs/user-guide/images/import.png


+ 24 - 32
docs/user-guide/impala.md

@@ -16,8 +16,8 @@ Cloudera Impala Query UI Installation and Configuration
 
 The Cloudera Impala Query UI application is one of the applications
 installed as part of Hue. For information about installing and
-configuring Hue, see Hue Installation in
-[http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
+configuring Hue, see the Hue Installation
+manual..
 
 The Cloudera Impala Query UI assumes an existing Cloudera Impala
 installation. The Hue installation instructions include the
@@ -126,35 +126,30 @@ server.
 The pane to the left of the Query Editor lets you specify the following
 options:
 
-**Option**
-
-**Description**
-
-**DATABASE**
-
-The database containing the table definitions.
-
-**SETTINGS**
-
-Override Cloudera Impala default settings. To configure a new setting:
-
-1.  Click **Add**.
-2.  For **Key**, enter a Cloudera Impala configuration variable name.
-3.  For **Value**, enter the value you want to use for the variable.
-
-To view the default settings, click the **Settings** tab at the top of
-the page.
-
-**PARAMETERIZATION**
-
-Indicate that a dialog box should display to enter parameter values when
+<table>
+<tr><td>DATABASE</td><td>The database containing the table definitions.</td></tr>
+<tr><td>SETTINGS</td><td>Override the Cloudera Impala  default settings. To configure a new
+setting:
+
+<ol>
+<li> Click Add.
+<li> For Key, enter a Hive or Hadoop configuration variable name.
+<li> For Value, enter the value you want to use for the variable.
+
+For example, to override the directory where structured Hive query logs
+are created, you would enter hive.querylog.location for Key, and a
+path for Value.
+</ol>
+To view the default settings, click the Settings tab at the top of
+the page. 
+</td></tr>  
+<tr><td>PARAMETERIZATION</td><td>Indicate that a dialog box should display to enter parameter values when
 a query containing the string $parametername is executed. Enabled by
-default.
+default.</td></tr>
+<tr><td>METASTORE CATALOG</td><td>Refresh metadata. It is best to refresh metadata after making changes to
+databases such as adding or dropping a table.</td></tr>
+</table>
 
-**METASTORE CATALOG**
-
-Refresh metadata. It is best to refresh metadata after making changes to
-databases such as adding or dropping a table.
 
 ### Viewing Query History
 
@@ -178,9 +173,6 @@ Queries tab to display the respective queries or clicking **Saved
 Queries**. You can copy any query, but you can edit, delete, and view
 the history of only your own queries.
 
-Saved Query
-
-Procedure
 
 **Edit**
 

+ 3 - 6
docs/user-guide/jobbrowser.md

@@ -16,14 +16,11 @@ Job Browser Installation and Configuration
 ------------------------------------------
 
 Job Browser is one of the applications installed as part of Hue. For
-information about installing and configuring Hue, see Hue Installation
-in
-[http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
+information about installing and configuring Hue, see the Hue Installation
+manual.
 
 Job Browser can display both MRv1 and MRv2 jobs, but must be configured
-to display one type at a time. See MapReduce (MRv1) and YARN (MRv2)
-Cluster Configuration in [CDH4
-Installation](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
+to display one type at a time. 
 
 Starting Job Browser
 --------------------

+ 70 - 137
docs/user-guide/jobdesigner.md

@@ -16,13 +16,11 @@ Job Designer Installation and Configuration
 -------------------------------------------
 
 Job Designer is one of the applications installed as part of Hue. For
-information about installing and configuring Hue, see Hue Installation
-in
-[http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
+information about installing and configuring Hue, see the Hue Installation
+manual..
 
 In order to run DistCp, Streaming, Pig, Sqoop, and Hive jobs, Oozie must
-be configured to use the Oozie ShareLib. See Oozie Installation in
-[http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
+be configured to use the Oozie ShareLib. See the Oozie Installation manual.
 
 Starting Job Designer
 ---------------------
@@ -112,48 +110,21 @@ All job design settings except Name and Description support the use of
 variables of the form $variable\_name. When you run the job, a dialog
 box will appear to enable you to specify the values of the variables.
 
-**Name**
-
-Identifies the job and its collection of properties and parameters.
-
-**Description**
-
-A description of the job. The description is displayed in the dialog box
-that appears if you specify variables for the job.
-
-**Advanced**
-
--   **Is shared** - Indicate whether to share the action with all users.
--   **Oozie parameters** -
-
-**Prepare**
-
-Specifies paths to create or delete before starting the workflow job.
-
-**Params**
-
-Parameters to pass to a script or command. The parameters are expressed
+<table>
+<tr><td>Name</td><td>Identifies the job and its collection of properties and parameters.</td></tr>
+<tr><td>Description</td><td>A description of the job. The description is displayed in the dialog box
+that appears if you specify variables for the job.</td></tr>
+<tr><td>Advanced</td><td>Advanced settings:<ul><li>Is shared- Indicate whether to share the action with all users.<li>Oozie parameters - parameters to pass to Oozie</td></tr>
+<tr><td>Prepare</td><td>Specifies paths to create or delete before starting the workflow job.</td></tr>
+<tr><td>Params</td>Parameters to pass to a script or command. The parameters are expressed
 using the [JSP 2.0 Specification (JSP.2.3) Expression
 Language](http://jcp.org/aboutJava/communityprocess/final/jsr152/),
-allowing variables, functions, and complex expressions as parameters.
-
-**Job Properties**
-
-Job properties. To set a property value, click **Add Property**.
-
--   **Property name -** a configuration property name. This field
-    provides autocompletion, so you can type the first few characters of
-    a property name and then select the one you want from the drop-down
-    list.
--   **Value -** the property value.
-
-**Files**
+allowing variables, functions, and complex expressions as parameters.<td></td></tr>
+<tr><td>Job Properties</td><td>Job properties. To set a property value, click <b>Add Property</b>.<ol><li>Property name -  a configuration property name. This field provides autocompletion, so you can type the first few characters of a property name and then select the one you want from the drop-down
+    list.<li>Valuethe property value.</td></tr>
+<tr><td>Files</td><td>Files to pass to the job. Equivalent to the Hadoop -files option.</td></tr>
+<tr><td>Archives</td><td>Files to pass to the job. Archives to pass to the job. Equivalent to the Hadoop -archives option.</td></tr></table>
 
-Files to pass to the job. Equivalent to the Hadoop -files option.
-
-**Archives**
-
-Archives to pass to the job. Equivalent to the Hadoop -archives option.
 
 #### MapReduce Job Design
 
@@ -163,10 +134,10 @@ classes without having to write a main Java class. You must specify the
 mapper and reducer classes as well as other MapReduce properties in the
 Job Properties setting.
 
-**Jar path**
-
-The fully-qualified path to a JAR file containing the classes that
-implement the Mapper and Reducer functions.
+<table>
+<tr><td>Jar path</td><td>The fully-qualified path to a JAR file containing the classes that
+implement the Mapper and Reducer functions.</td></tr>
+</table>
 
 #### Streaming Job Design
 
@@ -176,139 +147,104 @@ Unix output. For more information about Hadoop streaming jobs, see
 [Hadoop
 Streaming](http://archive.cloudera.com/cdh/3/hadoop-0.20.2+320/streaming.html).
 
-**Mapper**
-
-The path to the mapper script or class. If the mapper file is not on the
-machines on the cluster, use the **Files** option to pass it as a part
-of job submission. Equivalent to the Hadoop -mapper option.
-
-**Reducer**
-
-The path to the reducer script or class. If the reducer file is not on
-the machines on the cluster, use the **Files** option to pass it as a
-part of job submission. Equivalent to the Hadoop -reducer option.
+<table>
+<tr><td>Mapper</td><td>The path to the mapper script or class. If the mapper file is not on the
+machines on the cluster, use the Files option to pass it as a part
+of job submission. Equivalent to the Hadoop -mapper option.</td></tr>
+<tr><td>Reducer</td><td>The path to the reducer script or class. If the reducer file is not on
+the machines on the cluster, use the Files option to pass it as a
+part of job submission. Equivalent to the Hadoop -reducer option.</td></tr>
+</table>
 
 #### Java Job Design
 
 A Java job design consists of a main class written in Java.
 
-**Jar path**
-
-The fully-qualified path to a JAR file containing the main class.
+<table>
+<tr><td>Jar path</td><td>The fully-qualified path to a JAR file containing the main class.</td></tr>
+<tr><td>Main class</td><td>The main class to invoke the program.</td></tr>
+<tr><td>Args</td><td>The arguments to pass to the main class.</td></tr>
+<tr><td>Java opts</td><td>The options to pass to the JVM.</td></tr>
+</table>
 
-**Main class**
-
-The main class to invoke the program.
-
-**Args**
-
-The arguments to pass to the main class.
-
-**Java opts**
-
-The options to pass to the JVM.
 
 #### Pig Job Design
 
-A Pig job design consists of a Pig script.
 
-**Script name**
+A Pig job design consists of a Pig script.
 
-Script name or path to the Pig script.
+<table>
+<tr><td>Script name</td><td>Script name or path to the Pig script.</td></tr>
+<tr><td></td><td></td></tr>
+<tr><td></td><td></td></tr>
+</table>
 
 #### Hive Job Design
 
 A Hive job design consists of a Hive script.
 
-**Script name**
+<table>
+<tr><td>Script name</td><td>Script name or path to the Hive script.</td></tr>
+</table>
+
 
-Script name or path to the Hive script.
 
 #### Sqoop Job Design
 
 A Sqoop job design consists of a Sqoop command.
 
-**Command**
-
-The Sqoop command.
+<table>
+<tr><td>Command</td><td>The Sqoop command.</td></tr>
+</table>
 
 #### Shell Job Design
 
 A Shell job design consists of a shell command.
 
-**Command**
-
-The shell command.
+<table>
+<tr><td>Command</td><td>The shell command.</td></tr>
+<tr><td></td>Capture output<td>Indicate whether to capture the output of the command.</td></tr>
+</table>
 
-**Capture output**
-
-Indicate whether to capture the output of the command.
 
 #### Ssh Job Design
 
 A Ssh job design consists of an ssh command.
 
-**User**
-
-The name of the user to run the command as.
-
-**Host**
-
-The name of the host to run the command on.
-
-**Command**
-
-The ssh command.
-
-**Capture output**
-
-Indicate whether to capture the output of the command.
+<table>
+<tr><td>User</td><td>The name of the user to run the command as.</td></tr>
+<tr><td>Host</td><td>The name of the host to run the command on.</td></tr>
+<tr><td>Command</td><td>The ssh command.</td></tr>
+<tr><td></td>Capture output<td>Indicate whether to capture the output of the command.</td></tr>
+</table>
 
 #### DistCp Job Design
 
-A DistCp job design consists of a .
+A DistCp job design consists of a DistCp command.
 
 #### Fs Job Design
 
 A Fs job design consists of a command that operates on HDFS.
 
-**Delete path**
-
-The path to delete. If it is a directory, it deletes recursively all its
-content and then deletes the directory.
-
-**Create directory**
-
-The path of a directory to create.
-
-**Move file**
-
-The source and destination paths to the file to be moved.
-
-**Change permissions**
-
-The path whose permissions are to be changed, the permissions, and an
-indicator of whether to change permission recursively.
+<table>
+<tr><td>Delete path</td><td>The path to delete. If it is a directory, it deletes recursively all its
+content and then deletes the directory.</td></tr>
+<tr><td></td>Create directory<td>The path of a directory to create.</td></tr>
+<tr><td>Move file</td><td>The source and destination paths to the file to be moved.</td></tr>
+<tr><td>Change permissions</td><td>The path whose permissions are to be changed, the permissions, and an
+indicator of whether to change permission recursively.</td></tr></table>
 
 #### Email Job Design
 
 A Email job design consists of an email message.
 
-**To addresses**
-
-The recipient of the email message.
+<table>
+<tr><td>To addresses</td><td>The recipient of the email message.</td></tr>
+<tr><td>CC addresses (optional)</td><td>The cc recipients of the email message.</td></tr>
+<tr><td>Subject</td><td>The subject of the email message.</td></tr>
+<tr><td>Body</td><td>The body of the email message.</td></tr>
+</table>
 
-**CC addresses (optional)**
-
-The cc recipients of the email message.
-
-**Subject**
-
-The subject of the email message.
-
-**Body**
-
-The body of the email message.
 
 ### Submitting a Job Design
 
@@ -339,9 +275,6 @@ Results of Submitting a Job](#topic_8_5).
 If you want to edit and use a job but you don't own it, you can make a
 copy of it and then edit and use the copied job.
 
-Action
-
-Procedure
 
 **Copy**
 

+ 2 - 7
docs/user-guide/metastore_manager.md

@@ -27,9 +27,8 @@ Metastore Manager Installation and Configuration
 ------------------------------------------------
 
 Metastore Manager is one of the applications installed as part of Hue.
-For information about installing and configuring Hue, see Hue
-Installation in
-[http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
+For information about installing and configuring Hue, see the Hue Installation
+manual.
 
 Starting Metastore Manager
 --------------------------
@@ -101,10 +100,6 @@ specify all the properties of the table, and then execute the resulting
 query to actually create the table. You then import data into the table
 as an additional step.
 
-Create a Table
-
-Procedure
-
 **From a File**
 
 1.  In the ACTIONS pane in the Metastore Manager window, click **Create

+ 11 - 30
docs/user-guide/oozie.md

@@ -29,9 +29,8 @@ acyclic graph (DAG). It includes two types of nodes:
     [Email](hue2.0ug_topic_8.html#concept_gt5_bh3_zj__section_qjt_lh3_zj))
 
     In order to run DistCp, Streaming, Pig, Sqoop, and Hive jobs, Oozie
-    must be configured to use the Oozie ShareLib. See Oozie Installation
-    in
-    [http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
+    must be configured to use the Oozie ShareLib. See the Oozie Installation
+   manual.
 
 A coordinator application allows you to define and execute recurrent and
 interdependent workflow jobs. The coordinator application defines the
@@ -44,9 +43,8 @@ Oozie Editor/Dashboard Installation and Configuration
 -----------------------------------------------------
 
 Oozie Editor/Dashboard is one of the applications installed as part of
-Hue. For information about installing and configuring Hue, see Hue
-Installation in
-[http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html](http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH4/latest/CDH4-Installation-Guide/CDH4-Installation-Guide.html).
+Hue. For information about installing and configuring Hue, see the Hue Installation
+manual.
 
 Starting Oozie Editor/Dashboard
 -------------------------------
@@ -94,29 +92,13 @@ viewed, submitted, and modified by their owner or a superuser.
 Editor permissions for performing actions on workflows, coordinators,
 and bundles are summarized in the following table:
 
-**Action**
+<table>
+<th><td>Action</td><td>Superuser or Owner</td><td>All</td></th>
+<tr><td>View</td><td>Y.</td><td>Only if "Is shared" is set</td></tr>
+<tr><td>Submit</td><td>Y.</td><td>Only if "Is shared" is set</td></tr>
+<tr><td>Modify</td><td>Y.</td><td>N</td></tr>
+</table>
 
-**Superuser or Owner**
-
-**All**
-
-View
-
-Y
-
-Only if "Is shared" is set
-
-Submit
-
-Y
-
-Only if "Is shared" is set
-
-Modify
-
-Y
-
-N
 
 Deleting and Restoring Workflows, Coordinators, and Bundles
 -----------------------------------------------------------
@@ -160,8 +142,7 @@ Click a workflow row in the Running or Completed table to view detailed
 information about that workflow job.
 
 In the left pane contains a link to the workflow and the variable values
-specified.\
-![image](images/workflow.jpg)\
+specified.![image](images/workflow.jpg)
 
 For the selected job, the following information is available in the
 right area.

+ 74 - 0
docs/user-guide/search.md

@@ -0,0 +1,74 @@
+
+<link rel="stylesheet" href="docbook.css" type="text/css" media="screen" title="no title" charset="utf-8"></link>
+
+Solr Search
+==========================
+
+The Solr Search application allows you to 
+
+ Solr Search Installation and Configuration
+-----------------------------------------------------
+
+Search is one of the applications installed as part of
+Hue. For information about installing and configuring Hue, see the Hue Installation
+manual.
+
+Starting  Solr Search
+-------------------------------
+
+Click the ** Solr Search** icon
+(![image](images/icon_search_24.png)) in the navigation bar at the top of
+the Hue browser page. **Solr Search** opens with the
+following screens:
+
+-   [Collection Manager](#topic_9_7) - shows available collections 
+
+Installing Solr Search Examples
+------------------------------------------
+
+![image](images/note.jpg) **Note**: You must be a superuser to perform
+this task.
+
+1.  Click ![image](images/quick_start.png). The Quick Start Wizard
+    opens.
+2.  Click **Step 2: Examples**.
+3.  Click **Solr Search**.
+
+
+Filtering Collections in Solr Search
+-----------------------------------------
+
+Many screens contain lists. When you type in the Filter field on
+screens, the lists are dynamically filtered to display only those rows
+containing text that matches the specified substring.
+
+
+Collection Manager
+----------------
+
+In Collection Manager you .
+
+
+### Creating a Collection
+
+1.  Click the **Create** button at the top right.
+2.  In the Name field, type a name.
+3.  Check the Is shared checkbox to allow all users to access the
+    workflow.
+4.  Click **advanced** to specify the deployment directory or a job.xml
+    file.
+5.  Click **Save**. The Workflow Editor opens. Proceed with [Editing a
+    Workflow](#topic_9_7_7).
+
+### Importing a Collection
+
+1. Click the ![image](images/import.png) **Import** button at the top right.
+1. Check the checkboxes next to the collections or cores to import.
+1. Click **Import Selected**.
+
+
+#### A Heading
+
+
+
+