You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hive.apache.org by gi...@apache.org on 2025/02/10 09:00:39 UTC

(hive-site) branch asf-site updated: deploy: 23b13c4cb5ef328862564d91e094728affc85c42

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hive-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 93cb7cb  deploy: 23b13c4cb5ef328862564d91e094728affc85c42
93cb7cb is described below

commit 93cb7cba7fbc51d7c658dff1cdc9fe24634f5ed4
Author: zabetak <za...@users.noreply.github.com>
AuthorDate: Mon Feb 10 09:00:33 2025 +0000

    deploy: 23b13c4cb5ef328862564d91e094728affc85c42
---
 docs/latest/158869886/index.html                   |   2 +-
 docs/latest/170266662/index.html                   |   2 +-
 docs/latest/283118453/index.html                   |  18 +-
 docs/latest/284790216/index.html                   |  10 +-
 docs/latest/30151323/index.html                    |   6 +-
 docs/latest/44302539/index.html                    |   4 +-
 docs/latest/45876173/index.html                    |  58 +--
 .../latest/accumulointegration_46633569/index.html |  40 +-
 .../adminmanual-installation_27362077/index.html   |   4 +-
 .../index.html                                     |   2 +-
 .../index.html                                     |   4 +-
 docs/latest/authdev_27362078/index.html            | 262 +++++-----
 docs/latest/avroserde_27850707/index.html          |  30 +-
 .../binary-datatype-proposal_27826614/index.html   |   2 +-
 .../column-statistics-in-hive_29131019/index.html  |   2 +-
 .../common-table-expression_38572242/index.html    |   2 +-
 .../latest/compaction-pooling_240884493/index.html |   6 +-
 docs/latest/compressedstorage_27362073/index.html  |   4 +-
 .../configuration-properties_27842758/index.html   |   4 +-
 .../correlation-optimizer_34019487/index.html      |  48 +-
 docs/latest/csv-serde_48202659/index.html          |   8 +-
 .../index.html                                     |  32 +-
 .../data-connectors-in-hive_177049669/index.html   |  14 +-
 .../datasketches-integration_177050456/index.html  |  64 +--
 docs/latest/developerguide_27362074/index.html     |  18 +-
 docs/latest/druid-integration_65866491/index.html  | 164 +++----
 docs/latest/dynamicpartitions_27823715/index.html  |   8 +-
 docs/latest/exchange-partition_30755801/index.html |   2 +-
 .../genericudafcasestudy_27362093/index.html       |   4 +-
 docs/latest/gettingstarted_27362090/index.html     |  72 +--
 docs/latest/hbasebulkload_27362088/index.html      |  52 +-
 docs/latest/hbaseintegration_27362089/index.html   | 106 ++--
 .../hcatalog-dynamicpartitions_34014006/index.html |   8 +-
 .../hcatalog-inputoutput_34013776/index.html       |  56 +--
 docs/latest/hcatalog-loadstore_34013511/index.html |  58 +--
 .../hcatalog-notification_34014558/index.html      |  16 +-
 docs/latest/hcatalog-usinghcat_34013260/index.html |  12 +-
 .../hive-iceberg-integration_282102247/index.html  |  60 ++-
 docs/latest/hive-metatool_55156221/index.html      |  20 +-
 docs/latest/hive-on-tez_33296197/index.html        |  52 +-
 docs/latest/hive-schema-tool_34835119/index.html   |   8 +-
 docs/latest/hive-transactions_40509723/index.html  |  18 +-
 docs/latest/hive-udfs_282102277/index.html         | 164 +++----
 .../hiveaws-hivings3nremotely_27362102/index.html  |  20 +-
 docs/latest/hiveclient_27362101/index.html         |  30 +-
 .../latest/hivederbyservermode_27362068/index.html |  14 +-
 docs/latest/hivedeveloperfaq_27823747/index.html   |  34 +-
 docs/latest/hivejdbcinterface_27362100/index.html  |  10 +-
 docs/latest/hiveodbc_27362099/index.html           |  24 +-
 docs/latest/hiveplugins_27362098/index.html        |  18 +-
 .../index.html                                     |   4 +-
 .../latest/hiveserver2-clients_30758725/index.html |  40 +-
 .../hiveserver2-thrift-api_27843687/index.html     | 300 ++++++------
 docs/latest/hiveserver_27362111/index.html         |   4 +-
 docs/latest/hivewebinterface_27362110/index.html   |   4 +-
 .../how-to-edit-the-website_33294834/index.html    |   2 +-
 docs/latest/howtocontribute_27362107/index.html    |   8 +-
 docs/latest/howtorelease_27362106/index.html       |  22 +-
 docs/latest/index.xml                              |  20 +-
 docs/latest/indexdev_27362104/index.html           |  72 +--
 .../jdbc-storage-handler_95651916/index.html       |  24 +-
 docs/latest/jenkins-script_33295285/index.html     |  54 +-
 docs/latest/kudu-integration_133631955/index.html  |  10 +-
 .../languagemanual-archiving_27362031/index.html   |   4 +-
 docs/latest/languagemanual-cli_27362033/index.html |  16 +-
 .../index.html                                     |  10 +-
 docs/latest/languagemanual-ddl_27362034/index.html | 542 ++++++++++-----------
 docs/latest/languagemanual-dml_27362036/index.html |  46 +-
 .../languagemanual-explain_27362037/index.html     | 206 ++++----
 .../languagemanual-groupby_27362038/index.html     |  38 +-
 .../index.html                                     |  36 +-
 .../languagemanual-indexing_31822176/index.html    |  30 +-
 .../index.html                                     |  42 +-
 .../languagemanual-joins_27362039/index.html       |  32 +-
 .../languagemanual-lateralview_27362040/index.html |   4 +-
 docs/latest/languagemanual-lzo_33298193/index.html |   4 +-
 docs/latest/languagemanual-orc_31818911/index.html |   8 +-
 .../languagemanual-sampling_27362042/index.html    |   8 +-
 .../languagemanual-select_27362043/index.html      |  38 +-
 .../languagemanual-sortby_27362045/index.html      |  14 +-
 .../languagemanual-transform_27362047/index.html   |  62 +--
 .../languagemanual-types_27838462/index.html       |  26 +-
 docs/latest/languagemanual-udf_27362046/index.html |  30 +-
 .../languagemanual-union_27362049/index.html       |  26 +-
 .../index.html                                     |   2 +-
 .../index.html                                     |   4 +-
 .../languagemanual-xpathudf_27362051/index.html    |  40 +-
 docs/latest/llap_62689557/index.html               |   2 +-
 .../managed-vs-external-tables_95654003/index.html |   4 +-
 .../manual-installation_283118363/index.html       |  62 +--
 docs/latest/materialized-views_80447331/index.html | 220 ++++-----
 docs/latest/outerjoinbehavior_35749927/index.html  |  52 +-
 docs/latest/parquet_38570914/index.html            |   4 +-
 docs/latest/partitionedviews_27362053/index.html   |  16 +-
 docs/latest/plugindeveloperkit_27820324/index.html |  16 +-
 docs/latest/query-reexecution_87298873/index.html  |   2 +-
 docs/latest/rcfilecat_30748712/index.html          |   4 +-
 .../rebalance-compaction_240884502/index.html      |   6 +-
 .../index.html                                     |  18 +-
 docs/latest/running-yetus_71012969/index.html      |   2 +-
 docs/latest/scheduled-queries_145724128/index.html |  54 +-
 .../index.html                                     |  12 +-
 .../setting-up-hiveserver2_30758712/index.html     |   6 +-
 .../index.html                                     |  56 +--
 .../statisticsanddatamining_27362058/index.html    |  12 +-
 docs/latest/statsdev_27362062/index.html           |  22 +-
 docs/latest/storagehandlers_27362063/index.html    |  20 +-
 .../streaming-data-ingest-v2_85477610/index.html   |   4 +-
 .../subqueries-in-select_68717850/index.html       |  64 +--
 .../latest/teradatabinaryserde_89068127/index.html | 166 +++----
 docs/latest/top-k-stats_30150275/index.html        |  10 +-
 .../index.html                                     |  36 +-
 docs/latest/tutorial_27362061/index.html           | 248 +++++-----
 .../index.html                                     |  26 +-
 docs/latest/userguide_27362066/index.html          |  18 +-
 .../index.html                                     |  18 +-
 .../vectorized-query-execution_34838326/index.html |   8 +-
 docs/latest/viewdev_27362067/index.html            |  34 +-
 docs/latest/webhcat-configure_34015738/index.html  |   2 +-
 .../webhcat-reference-ddl_34015990/index.html      |  12 +-
 .../webhcat-reference-deletedb_34016281/index.html |   2 +-
 .../index.html                                     |  14 +-
 .../index.html                                     |  14 +-
 .../index.html                                     |   4 +-
 .../index.html                                     |   4 +-
 .../index.html                                     |   4 +-
 .../index.html                                     |   8 +-
 .../index.html                                     |   4 +-
 .../index.html                                     |  10 +-
 .../index.html                                     |   8 +-
 .../webhcat-reference-gettable_34016519/index.html |  18 +-
 .../index.html                                     |   6 +-
 .../webhcat-reference-hive_34017180/index.html     |   4 +-
 .../webhcat-reference-job_34835065/index.html      |  14 +-
 .../webhcat-reference-jobids_34017187/index.html   |   4 +-
 .../webhcat-reference-jobinfo_34017194/index.html  |  26 +-
 .../webhcat-reference-jobs_34835057/index.html     |  24 +-
 .../index.html                                     |   4 +-
 .../index.html                                     |   8 +-
 .../webhcat-reference-pig_34017169/index.html      |   4 +-
 .../index.html                                     |  10 +-
 .../index.html                                     |   4 +-
 .../webhcat-reference-putdb_34016273/index.html    |   2 +-
 .../index.html                                     |   6 +-
 .../index.html                                     |   4 +-
 .../webhcat-reference-puttable_34016540/index.html |  14 +-
 .../index.html                                     |   4 +-
 .../webhcat-usingwebhcat_34015492/index.html       |   6 +-
 index.xml                                          |  20 +-
 149 files changed, 2508 insertions(+), 2490 deletions(-)

diff --git a/docs/latest/158869886/index.html b/docs/latest/158869886/index.html
index ca7baf9..af9016e 100644
--- a/docs/latest/158869886/index.html
+++ b/docs/latest/158869886/index.html
@@ -186,7 +186,7 @@ public GetTableResponse getTable(GetTableRequest grpcTableRequest) {
   // convertToThriftRequest is implemented by a different library, not in Hive code
   Table thriftGetTableRequest = convertToThriftRequest(grpcTableRequest);
   // Result is a Thrift API object    
-  GetTableResult result = HiveMetaStoreThriftServer.get\_table(thriftTable);
+  GetTableResult result = HiveMetaStoreThriftServer.get_table(thriftTable);
   return convertToThriftResponse(result);
 }
 
diff --git a/docs/latest/170266662/index.html b/docs/latest/170266662/index.html
index eb00ccf..b07c358 100644
--- a/docs/latest/170266662/index.html
+++ b/docs/latest/170266662/index.html
@@ -162,7 +162,7 @@ ASF
 <p>For example, in case of browser the URL will look like</p>
 <pre tabindex=0><code>jdbc:hive2://HiveServer2-host:10001/default;transportMode=http;httpPath=cliservice;auth=browser
 </code></pre><p>A token based URL will look like:</p>
-<pre tabindex=0><code>jdbc:hive2://HiveServer2-host:10001/default;transportMode=http;httpPath=cliservice;auth=token;token=&lt;token\_string&gt;
+<pre tabindex=0><code>jdbc:hive2://HiveServer2-host:10001/default;transportMode=http;httpPath=cliservice;auth=token;token=&lt;token_string&gt;
 </code></pre><p>The Jdbc connection parameters will be passed in over the connection URL. </p>
 <h5 id=sso-mode-url-validations>SSO mode URL validations</h5>
 <p>Driver makes sure that the SSO integration is only allowed when TLS enabled between driver and the server. If the SSL is not enabled, the driver should error out (or optionally warn the users based on a configuration override). Currently, both these modes will only be supported in http mode.</p>
diff --git a/docs/latest/283118453/index.html b/docs/latest/283118453/index.html
index d2bbb5e..155b8da 100644
--- a/docs/latest/283118453/index.html
+++ b/docs/latest/283118453/index.html
@@ -195,12 +195,12 @@ ASF
 <p>Previously all files for a partition (or a table if the table is not partitioned) lived in a single directory.  With these changes, any partitions (or tables) written with an ACID aware writer will have a directory for the base files and a directory for each set of delta files.  Here is what this may look like for an unpartitioned table &ldquo;t&rdquo;:</p>
 <p><strong>Filesystem Layout for Table &ldquo;t&rdquo;</strong></p>
 <pre tabindex=0><code>hive&gt; dfs -ls -R /user/hive/warehouse/t;
-drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:03 /user/hive/warehouse/t/base\_0000022
--rw-r--r--   1 ekoifman staff        602 2016-06-09 17:03 /user/hive/warehouse/t/base\_0000022/bucket\_00000
-drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:06 /user/hive/warehouse/t/delta\_0000023\_0000023\_0000
--rw-r--r--   1 ekoifman staff        611 2016-06-09 17:06 /user/hive/warehouse/t/delta\_0000023\_0000023\_0000/bucket\_00000
-drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:07 /user/hive/warehouse/t/delta\_0000024\_0000024\_0000
--rw-r--r--   1 ekoifman staff        610 2016-06-09 17:07 /user/hive/warehouse/t/delta\_0000024\_0000024\_0000/bucket\_00000
+drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:03 /user/hive/warehouse/t/base_0000022
+-rw-r--r--   1 ekoifman staff        602 2016-06-09 17:03 /user/hive/warehouse/t/base_0000022/bucket_00000
+drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:06 /user/hive/warehouse/t/delta_0000023_0000023_0000
+-rw-r--r--   1 ekoifman staff        611 2016-06-09 17:06 /user/hive/warehouse/t/delta_0000023_0000023_0000/bucket_00000
+drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:07 /user/hive/warehouse/t/delta_0000024_0000024_0000
+-rw-r--r--   1 ekoifman staff        610 2016-06-09 17:07 /user/hive/warehouse/t/delta_0000024_0000024_0000/bucket_00000
 </code></pre><h3 id=compactor>Compactor</h3>
 <p>Compactor is a set of background processes running inside the Metastore to support ACID system.  It consists of Initiator, Worker, Cleaner, AcidHouseKeeperService and a few others.</p>
 <h4 id=delta-file-compaction>Delta File Compaction</h4>
@@ -613,7 +613,7 @@ drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:07 /user/hive/warehouse/t
 <p>Table properties are set with the TBLPROPERTIES clause when a table is created or altered, as described in the <a href=#create-table>Create Table</a> and <a href=#alter-table-properties>Alter Table Properties</a> sections of Hive Data Definition Language. The &ldquo;<code>transactional</code>&rdquo; and &ldquo;<code>NO_AUTO_COMPACTION</code>&rdquo; table properties are case-insensitive.</p>
 <p>More compaction related options can be set via TBLPROPERTIES. They can be set at both table-level via <a href=https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-Create/Drop/TruncateTable>CREATE TABLE</a>, and on request-level via <a href=https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-AlterTable/PartitionCompact>ALTER TABLE/PARTITION COMPACT</a>.  These are used to override the Warehouse/table wide settings.  For [...]
 <p><strong>Example: Set compaction options in TBLPROPERTIES at table level</strong></p>
-<pre tabindex=0><code>CREATE TABLE table\_name (
+<pre tabindex=0><code>CREATE TABLE table_name (
   id                int,
   name              string
 )
@@ -625,9 +625,9 @@ TBLPROPERTIES (&quot;transactional&quot;=&quot;true&quot;,
                                                                    -- size of base files is greater than 50%
 );
 </code></pre><p><strong>Example: Set compaction options in TBLPROPERTIES at request level</strong></p>
-<pre tabindex=0><code>ALTER TABLE table\_name COMPACT 'minor' 
+<pre tabindex=0><code>ALTER TABLE table_name COMPACT 'minor' 
    WITH OVERWRITE TBLPROPERTIES (&quot;compactor.mapreduce.map.memory.mb&quot;=&quot;3072&quot;);  -- specify compaction map job properties
-ALTER TABLE table\_name COMPACT 'major'
+ALTER TABLE table_name COMPACT 'major'
    WITH OVERWRITE TBLPROPERTIES (&quot;tblprops.orc.compress.size&quot;=&quot;8192&quot;);         -- change any other Hive table properties
 </code></pre><h1 id=talks-and-presentations>Talks and Presentations</h1>
 <p><a href="https://youtu.be/h62Bhe78jW0?t=1953">The Art of Compaction</a> by Kokila N at a Cloudera meetup.</p>
diff --git a/docs/latest/284790216/index.html b/docs/latest/284790216/index.html
index 5a12184..a51cb1d 100644
--- a/docs/latest/284790216/index.html
+++ b/docs/latest/284790216/index.html
@@ -229,7 +229,7 @@ Caused by: MetaException(message:Version information not found in metastore. )
 <li>Initialize to current schema for a new Hive setup:</li>
 </ul>
 <pre tabindex=0><code>$ schematool -dbType derby -initSchema Initializing the schema to: 4.0.0-beta-2
-Metastore connection URL:	 jdbc:derby:;databaseName=metastore\_db;create=true
+Metastore connection URL:	 jdbc:derby:;databaseName=metastore_db;create=true
 Metastore connection Driver :	 org.apache.derby.jdbc.EmbeddedDriver
 Metastore connection User:	 APP
 Starting metastore schema initialization to 4.0.0-beta-2
@@ -239,7 +239,7 @@ Initialization script completed
 <li>Get schema information:</li>
 </ul>
 <pre tabindex=0><code>$ schematool -dbType derby -info 
-Metastore connection URL:	 jdbc:derby:;databaseName=metastore\_db;create=true
+Metastore connection URL:	 jdbc:derby:;databaseName=metastore_db;create=true
 Metastore connection Driver :	 org.apache.derby.jdbc.EmbeddedDriver
 Metastore connection User:	 APP
 Hive distribution version:	 4.0.0-beta-2
@@ -248,7 +248,7 @@ Metastore schema version:	 4.0.0-beta-2
 <li>Init schema to for a given version: </li>
 </ul>
 <pre tabindex=0><code>$ schematool -dbType derby -initSchemaTo 3.1.0 
-Metastore connection URL:	 jdbc:derby:;databaseName=metastore\_db;create=true
+Metastore connection URL:	 jdbc:derby:;databaseName=metastore_db;create=true
 Metastore connection Driver :	 org.apache.derby.jdbc.EmbeddedDriver
 Metastore connection User:	 APP
 Starting metastore schema initialization to 3.1.0
@@ -257,7 +257,7 @@ Initialization script hive-schema-3.1.0.derby.sql
 <li>Upgrade schema from an 3.1.0 release by specifying the &lsquo;from&rsquo; version:</li>
 </ul>
 <pre tabindex=0><code>$ schematool -dbType derby -upgradeSchemaFrom 3.1.0 Upgrading from the user input version 3.1.0
-Metastore connection URL:	 jdbc:derby:;databaseName=metastore\_db;create=true
+Metastore connection URL:	 jdbc:derby:;databaseName=metastore_db;create=true
 Metastore connection Driver :	 org.apache.derby.jdbc.EmbeddedDriver
 Metastore connection User:	 APP
 Starting upgrade metastore schema from version 3.1.0 to 4.0.0-beta-2
@@ -269,7 +269,7 @@ Completed upgrade-4.0.0-beta-1-to-4.0.0-beta-2.derby.sql
 <li>Upgrade dry run can be used to list the required scripts for the given upgrade.</li>
 </ul>
 <pre tabindex=0><code>$ schematool -dbType derby -upgradeSchemaFrom 3.1.0 -dryRun Upgrading from the user input version 3.1.0
-Metastore connection URL:	 jdbc:derby:;databaseName=metastore\_db;create=true
+Metastore connection URL:	 jdbc:derby:;databaseName=metastore_db;create=true
 Metastore connection Driver :	 org.apache.derby.jdbc.EmbeddedDriver
 Metastore connection User:	 APP
 Starting upgrade metastore schema from version 3.1.0 to 4.0.0-beta-2
diff --git a/docs/latest/30151323/index.html b/docs/latest/30151323/index.html
index 2ef23d1..126654c 100644
--- a/docs/latest/30151323/index.html
+++ b/docs/latest/30151323/index.html
@@ -200,7 +200,7 @@ Support for SQL <em>grouping</em> function was added in Hive 2.3.0 too (see <a h
 </tbody>
 </table>
 <p>The following query:</p>
-<pre tabindex=0><code>SELECT key, value, GROUPING\_\_ID, count(*)
+<pre tabindex=0><code>SELECT key, value, GROUPING__ID, count(*)
 FROM T1
 GROUP BY key, value WITH ROLLUP;
 </code></pre><p>will have the following results:</p>
@@ -289,7 +289,7 @@ For the third row, both the columns are being selected (and the second column h
 <h3 id=grouping-function>Grouping function</h3>
 <p>The grouping function indicates whether an expression in a GROUP BY clause is aggregated or not for a given row. The value 0 represents a column that is part of the grouping set, while the value 1 represents a column that is not part of the grouping set. </p>
 <p>Going back to our example above, consider the following query:</p>
-<pre tabindex=0><code>SELECT key, value, GROUPING\_\_ID,
+<pre tabindex=0><code>SELECT key, value, GROUPING__ID,
   grouping(key, value), grouping(value, key), grouping(key), grouping(value),
   count(*)
 FROM T1
@@ -441,7 +441,7 @@ assumption that the orginal group by will reduce the data size.</p>
 <h3 id=grouping__id-function-before-hive-230>Grouping__ID function (before Hive 2.3.0)</h3>
 <p>Grouping__ID function was fixed in Hive 2.3.0, thus behavior before that release is different (this is expected). For each column, the function would return a value of &ldquo;0&rdquo; iif that column has been aggregated in that row, otherwise the value is &ldquo;1&rdquo;.</p>
 <p>Hence the following query:</p>
-<pre tabindex=0><code>SELECT key, value, GROUPING\_\_ID, count(*)
+<pre tabindex=0><code>SELECT key, value, GROUPING__ID, count(*)
 FROM T1
 GROUP BY key, value WITH ROLLUP;
 </code></pre><p>will have the following results.</p>
diff --git a/docs/latest/44302539/index.html b/docs/latest/44302539/index.html
index 47d056e..d647740 100644
--- a/docs/latest/44302539/index.html
+++ b/docs/latest/44302539/index.html
@@ -358,7 +358,7 @@ set spark.serializer=org.apache.spark.serializer.KryoSerializer;
 <td>Run this command before starting Hive or HiveServer2:export HADOOP_OPTS="-Dorg.xerial.snappy.tempdir=/tmp -Dorg.xerial.snappy.lib.name=libsnappyjava.jnilib $HADOOP_OPTS"</td>
 </tr>
 <tr>
-<td>Stack trace: ExitCodeException exitCode=1: &mldr;/launch_container.sh: line 27: $PWD:$PWD/__spark__.jar:$HADOOP_CONF_DIR&mldr;/usr/hdp/${hdp.version}/hadoop/lib/hadoop-lzo-0.6.0.${hdp.version}.jar:/etc/hadoop/conf/secure:$PWD/__app__.jar:$PWD/*: bad substitution </td>
+<td>Stack trace: ExitCodeException exitCode=1: &mldr;/launch_container.sh: line 27: $PWD:$PWD/<strong>spark</strong>.jar:$HADOOP_CONF_DIR&mldr;/usr/hdp/${hdp.version}/hadoop/lib/hadoop-lzo-0.6.0.${hdp.version}.jar:/etc/hadoop/conf/secure:$PWD/<strong>app</strong>.jar:$PWD/*: bad substitution </td>
 <td>The key mapreduce.application.classpath in /etc/hadoop/conf/mapred-site.xml contains a variable which is invalid in bash.</td>
 <td>From <strong>mapreduce.application.classpath</strong> remove <code>:/usr/hdp/${hdp.version}/hadoop/lib/hadoop-lzo-0.6.0.${hdp.version}.jar</code> from <strong>/etc/hadoop/conf/mapred-site.xml</strong></td>
 </tr>
@@ -370,7 +370,7 @@ set spark.serializer=org.apache.spark.serializer.KryoSerializer;
 <tr>
 <td>java.lang.OutOfMemoryError: PermGen space with spark.master=local</td>
 <td>By default (<a href=https://issues.apache.org/jira/browse/SPARK-1879>SPARK-1879</a>), Spark&rsquo;s own launch scripts increase PermGen to 128 MB, so we need to increase PermGen in hive launch script.</td>
-<td>If use JDK7, append following in conf/hive-env.sh: <code>export HADOOP\_OPTS="$HADOOP\_OPTS -XX:MaxPermSize=128m"</code> If use JDK8, append following in Conf/hive-env.sh: <code>export HADOOP\_OPTS="$HADOOP\_OPTS -XX:MaxMetaspaceSize=512m"</code></td>
+<td>If use JDK7, append following in conf/hive-env.sh: <code>export HADOOP_OPTS="$HADOOP_OPTS -XX:MaxPermSize=128m"</code> If use JDK8, append following in Conf/hive-env.sh: <code>export HADOOP_OPTS="$HADOOP_OPTS -XX:MaxMetaspaceSize=512m"</code></td>
 </tr>
 </tbody>
 </table>
diff --git a/docs/latest/45876173/index.html b/docs/latest/45876173/index.html
index 68b38ea..12e8e63 100644
--- a/docs/latest/45876173/index.html
+++ b/docs/latest/45876173/index.html
@@ -184,19 +184,19 @@ ASF
 <p>As of <a href=https://issues.apache.org/jira/browse/HIVE-8083>Hive 0.14</a>, user may be optionally surrounded by backtick characters (<code>) irrespective of the </code><a href=https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.support.quoted.identifiers>hive.support.quoted.identifiers</a>` setting.</p>
 <h3 id=creatingdroppingusing-roles>Creating/Dropping/Using Roles</h3>
 <h4 id=createdrop-role>Create/Drop Role</h4>
-<pre tabindex=0><code>CREATE ROLE role\_name
+<pre tabindex=0><code>CREATE ROLE role_name
 
-DROP ROLE role\_name
+DROP ROLE role_name
 
 </code></pre><h4 id=grantrevoke-roles>Grant/Revoke Roles</h4>
-<pre tabindex=0><code>GRANT ROLE role\_name [, role\_name] ...
-TO principal\_specification [, principal\_specification] ...
+<pre tabindex=0><code>GRANT ROLE role_name [, role_name] ...
+TO principal_specification [, principal_specification] ...
 [WITH ADMIN OPTION]
 
-REVOKE [ADMIN OPTION FOR] ROLE role\_name [, role\_name] ...
-FROM principal\_specification [, principal\_specification] ...
+REVOKE [ADMIN OPTION FOR] ROLE role_name [, role_name] ...
+FROM principal_specification [, principal_specification] ...
 
-principal\_specification:
+principal_specification:
     USER user
   | GROUP group
   | ROLE role
@@ -206,9 +206,9 @@ principal\_specification:
 <p>REVOKE ROLE will add the optional ADMIN OPTION FOR clause in Hive 0.14.0 (<a href=https://issues.apache.org/jira/browse/HIVE-6252>HIVE-6252</a>).</p>
 <p> </p>
 <h4 id=viewing-granted-roles>Viewing Granted Roles</h4>
-<pre tabindex=0><code>SHOW ROLE GRANT principal\_specification
+<pre tabindex=0><code>SHOW ROLE GRANT principal_specification
  
-principal\_specification:
+principal_specification:
     USER user
   | GROUP group
   | ROLE role
@@ -229,30 +229,30 @@ principal\_specification:
 </ul>
 <h4 id=grantrevoke-privileges>Grant/Revoke Privileges</h4>
 <pre tabindex=0><code>GRANT
-    priv\_type [(column\_list)]
-      [, priv\_type [(column\_list)]] ...
-    [ON object\_specification]
-    TO principal\_specification [, principal\_specification] ...
+    priv_type [(column_list)]
+      [, priv_type [(column_list)]] ...
+    [ON object_specification]
+    TO principal_specification [, principal_specification] ...
     [WITH GRANT OPTION]
 
 REVOKE [GRANT OPTION FOR]
-    priv\_type [(column\_list)]
-      [, priv\_type [(column\_list)]] ...
-    [ON object\_specification]
-    FROM principal\_specification [, principal\_specification] ...
+    priv_type [(column_list)]
+      [, priv_type [(column_list)]] ...
+    [ON object_specification]
+    FROM principal_specification [, principal_specification] ...
 
 REVOKE ALL PRIVILEGES, GRANT OPTION
     FROM user [, user] ...
 
-priv\_type:
+priv_type:
     ALL | ALTER | UPDATE | CREATE | DROP
-  | INDEX | LOCK | SELECT | SHOW\_DATABASE 
+  | INDEX | LOCK | SELECT | SHOW_DATABASE 
  
-object\_specification:
-    TABLE tbl\_name
-  | DATABASE db\_name
+object_specification:
+    TABLE tbl_name
+  | DATABASE db_name
  
-principal\_specification:
+principal_specification:
     USER user
   | GROUP group
   | ROLE role
@@ -260,17 +260,17 @@ principal\_specification:
 <p>REVOKE <em>priv_type</em> will add the optional GRANT OPTION FOR clause in Hive 0.14.0 (<a href=https://issues.apache.org/jira/browse/HIVE-7404>HIVE-7404</a>).</p>
 <p> </p>
 <h4 id=viewing-granted-privileges>Viewing Granted Privileges</h4>
-<pre tabindex=0><code>SHOW GRANT principal\_specification
-[ON object\_specification [(column\_list)]]
+<pre tabindex=0><code>SHOW GRANT principal_specification
+[ON object_specification [(column_list)]]
  
-principal\_specification:
+principal_specification:
     USER user
   | GROUP group
   | ROLE role
  
-object\_specification:
-    TABLE tbl\_name
-  | DATABASE db\_name
+object_specification:
+    TABLE tbl_name
+  | DATABASE db_name
 </code></pre><p>Version</p>
 <p>The output of SHOW GRANT is in tabular format starting with Hive 0.13.0 (<a href=https://issues.apache.org/jira/browse/HIVE-6204>HIVE-6204</a>).</p>
 <p> </p>
diff --git a/docs/latest/accumulointegration_46633569/index.html b/docs/latest/accumulointegration_46633569/index.html
index fa6d793..73de8e9 100644
--- a/docs/latest/accumulointegration_46633569/index.html
+++ b/docs/latest/accumulointegration_46633569/index.html
@@ -173,15 +173,15 @@ ASF
 <pre tabindex=0><code>hive -hiveconf accumulo.instance.name=accumulo -hiveconf accumulo.zookeepers=localhost -hiveconf accumulo.user.name=hive -hiveconf accumulo.user.pass=hive
 </code></pre><p>To access Accumulo tables, a Hive table must be created using the <code>CREATE</code> command with the <code>STORED BY</code> clause. If the <code>EXTERNAL</code> keyword is omitted from the <code>CREATE</code> call, the lifecycle of the Accumulo table is tied to the lifetime of the Hive table: if the Hive table is deleted, so is the Accumulo table. This is the default case. Providing the <code>EXTERNAL</code> keyword will create a Hive table that references an Accumulo t [...]
 <p>Each Hive row maps to a set of Accumulo keys with the same row ID. One column in the Hive row is designated as a &ldquo;special&rdquo; column which is used as the Accumulo row ID. All other Hive columns in the row have some mapping to Accumulo column (column family and qualifier) where the Hive column value is placed in the Accumulo value.</p>
-<pre tabindex=0><code>CREATE TABLE accumulo\_table(rowid STRING, name STRING, age INT, weight DOUBLE, height INT)
+<pre tabindex=0><code>CREATE TABLE accumulo_table(rowid STRING, name STRING, age INT, weight DOUBLE, height INT)
 STORED BY 'org.apache.hadoop.hive.accumulo.AccumuloStorageHandler'
 WITH SERDEPROPERTIES('accumulo.columns.mapping' = ':rowid,person:name,person:age,person:weight,person:height');
 </code></pre><p>In the above statement, normal Hive column name and type pairs are provided as is the case with normal create table statements. The full AccumuloStorageHandler class name is provided to inform Hive that Accumulo will back this Hive table. A number of properties can be provided to configure the AccumuloStorageHandler via SERDEPROPERTIES or TBLPROPERTIES. The most important property is &ldquo;accumulo.columns.mapping&rdquo; which controls how the Hive columns map to Accumul [...]
 <p>For the above schema in the &ldquo;accumulo_table&rdquo;, we could envision a single row in the table:</p>
-<pre tabindex=0><code>hive&gt; select * from accumulo\_table;
+<pre tabindex=0><code>hive&gt; select * from accumulo_table;
 row1	Steve	32	200	72
 </code></pre><p>The above record would be serialized into Accumulo Key-Value pairs in the following manner given the declared accumulo.columns.mapping:</p>
-<pre tabindex=0><code>user@accumulo accumulo\_table&gt; scan
+<pre tabindex=0><code>user@accumulo accumulo_table&gt; scan
 row1	person:age []	32
 row1	person:height []	72
 row1	person:name []	Steve
@@ -306,10 +306,10 @@ row1	person:weight []	200
 <pre tabindex=0><code>CREATE TABLE users(key int, userid int, username string) 
 STORED BY 'org.apache.hadoop.hive.accumulo.AccumuloStorageHandler'
 WITH SERDEPROPERTIES (&quot;accumulo.columns.mapping&quot; = &quot;:rowID,f:userid,f:nickname&quot;)
-WITH TBLPROPERTIES (&quot;accumulo.table.name&quot; = &quot;hive\_users&quot;);
+WITH TBLPROPERTIES (&quot;accumulo.table.name&quot; = &quot;hive_users&quot;);
 </code></pre><h3 id=store-a-hive-map-with-binary-serialization>Store a Hive map with binary serialization</h3>
 <p>Using an asterisk in the column mapping string, a Hive map can be expanded from a single Accumulo Key-Value pair to multiple Key-Value pairs. The Hive Map is a parameterized type: in the below case, the key is a string, and the value integer. The default serialization is overriden from &lsquo;string&rsquo; to &lsquo;binary&rsquo; which means that the integers in the value of the Hive map will be stored as a series of bytes instead of the UTF-8 string representation.</p>
-<pre tabindex=0><code>CREATE TABLE hive\_map(key int, value map&lt;string,int&gt;) 
+<pre tabindex=0><code>CREATE TABLE hive_map(key int, value map&lt;string,int&gt;) 
 STORED BY 'org.apache.hadoop.hive.accumulo.AccumuloStorageHandler'
 WITH SERDEPROPERTIES (
   &quot;accumulo.columns.mapping&quot; = &quot;:rowID,cf:*&quot;,
@@ -317,31 +317,31 @@ WITH SERDEPROPERTIES (
 );
 </code></pre><h3 id=register-an-external-table>Register an external table</h3>
 <p>Creating the Hive table with the external keyword decouples the lifecycle of the Accumulo table from that of the Hive table. Creating this table assumes that the Accumulo table &ldquo;countries&rdquo; already exists. This is a very useful way to use Hive to manage tables that are created and populated by some external tool (e.g. A MapReduce job). When the Hive table countries is deleted, the Accumulo table will not be deleted. Additionally, the external keyword can also be useful when [...]
-<pre tabindex=0><code>CREATE EXTERNAL TABLE countries(key string, name string, country string, country\_id int)
+<pre tabindex=0><code>CREATE EXTERNAL TABLE countries(key string, name string, country string, country_id int)
 STORED BY 'org.apache.hadoop.hive.accumulo.AccumuloStorageHandler'
-WITH SERDEPROPERTIES (&quot;accumulo.columns.mapping&quot; = &quot;:rowID,info:name,info:country,info:country\_id&quot;);
+WITH SERDEPROPERTIES (&quot;accumulo.columns.mapping&quot; = &quot;:rowID,info:name,info:country,info:country_id&quot;);
 </code></pre><h3 id=create-an-indexed-table>Create an indexed table</h3>
 <p>To take advantage of indexing, Hive uses another Accumulo table is used to create a lexicographically-sorted search term index for each field allowing for very efficient exact match and bounded range searches.</p>
-<pre tabindex=0><code>CREATE TABLE company\_stats (
+<pre tabindex=0><code>CREATE TABLE company_stats (
    rowid string,
-   active\_entry boolean,
-   num\_offices tinyint,
-   num\_personel smallint,
-   total\_manhours int,
-   num\_shareholders bigint,
-   eff\_rating float,
-   err\_rating double,
-   yearly\_production decimal,
-   start\_date date,
+   active_entry boolean,
+   num_offices tinyint,
+   num_personel smallint,
+   total_manhours int,
+   num_shareholders bigint,
+   eff_rating float,
+   err_rating double,
+   yearly_production decimal,
+   start_date date,
    address varchar(100),
    phone char(13),
-   last\_update timestamp )
+   last_update timestamp )
 ROW FORMAT SERDE 'org.apache.hadoop.hive.accumulo.serde.AccumuloSerDe'
 STORED BY 'org.apache.hadoop.hive.accumulo.AccumuloStorageHandler'
 WITH SERDEPROPERTIES (
    &quot;accumulo.columns.mapping&quot; = &quot;:rowID,a:act,a:off,a:per,a:mhs,a:shs,a:eff,a:err,a:yp,a:sd,a:addr,a:ph,a:lu”,
-   &quot;accumulo.table.name&quot;=&quot;company\_stats&quot;,
-   &quot;accumulo.indextable.name&quot;=&quot;company\_stats\_idx&quot;
+   &quot;accumulo.table.name&quot;=&quot;company_stats&quot;,
+   &quot;accumulo.indextable.name&quot;=&quot;company_stats_idx&quot;
  );
 </code></pre><h2 id=acknowledgements>Acknowledgements</h2>
 <p>I would be remiss to not mention the efforts made by Brian Femiano that were the basis for this storage handler. His initial prototype for Accumulo-Hive integration was the base for this work.</p>
diff --git a/docs/latest/adminmanual-installation_27362077/index.html b/docs/latest/adminmanual-installation_27362077/index.html
index 6a9498b..4ac1a20 100644
--- a/docs/latest/adminmanual-installation_27362077/index.html
+++ b/docs/latest/adminmanual-installation_27362077/index.html
@@ -154,10 +154,10 @@ Hive versions up to 0.13 also supported Hadoop 0.20.x, 0.23.x.</li>
 
 </code></pre><p>Set the environment variable <code>HIVE_HOME</code> to point to the installation directory:</p>
 <pre tabindex=0><code>  $ cd hive-x.y.z
-  $ export HIVE\_HOME={{pwd}}
+  $ export HIVE_HOME={{pwd}}
 
 </code></pre><p>Finally, add <code>$HIVE_HOME/bin</code> to your <code>PATH</code>:</p>
-<pre tabindex=0><code>  $ export PATH=$HIVE\_HOME/bin:$PATH
+<pre tabindex=0><code>  $ export PATH=$HIVE_HOME/bin:$PATH
 </code></pre><h2 id=installing-from-source-code-hive-120-and-later>Installing from Source Code (Hive 1.2.0 and Later)</h2>
 <p>Version information</p>
 <p>To build Hive 1.2.0 and later releases with <a href=http://maven.apache.org/>Apache Maven</a>, see <a href=#getting-started:-building-hive-from-source>Getting Started: Building Hive from Source</a>. You will need Java 1.7 or newer.</p>
diff --git a/docs/latest/adminmanual-metastore-3-0-administration_75978150/index.html b/docs/latest/adminmanual-metastore-3-0-administration_75978150/index.html
index 1c061b0..752fda4 100644
--- a/docs/latest/adminmanual-metastore-3-0-administration_75978150/index.html
+++ b/docs/latest/adminmanual-metastore-3-0-administration_75978150/index.html
@@ -384,7 +384,7 @@ ASF
 <p>Details about all properties for the CachedStore can be found on <a href=https://hive.apache.org/docs/latest/configuration-properties_27842758/>Configuration Properties</a> (Prefix: <code>metastore.cached</code>). </p>
 <h2 id=less-commonly-changed-configuration-parameters>Less Commonly Changed Configuration Parameters</h2>
 <p>BATCHED_RETRIEVE_<em>, CLIENT_CONNECT_RETRY_DELAY, FILTER_HOOK, SERDES_USING_METASTORE_FOR_SCHEMA, SERVER_</em>_THREADS, </p>
-<pre tabindex=0><code>THREAD\_POOL\_SIZE
+<pre tabindex=0><code>THREAD_POOL_SIZE
 </code></pre><p>Security: EXECUTE_SET_UGI, metastore.authorization.storage.checks</p>
 <p>Setting up Caching: CACHED*, CATALOGS_TO_CACHE & AGGREGATE_STATS_CACHE*</p>
 <p>Transactions: MAX_OPEN_TXNS, TXNS_*</p>
diff --git a/docs/latest/adminmanual-metastore-administration_27362076/index.html b/docs/latest/adminmanual-metastore-administration_27362076/index.html
index b8004db..656c0bc 100644
--- a/docs/latest/adminmanual-metastore-administration_27362076/index.html
+++ b/docs/latest/adminmanual-metastore-administration_27362076/index.html
@@ -367,7 +367,7 @@ ASF
 <p>In remote metastore setup, all Hive Clients will make a connection to a metastore server which in turn queries the datastore (MySQL in this example) for metadata. Metastore server and client communicate using <a href=http://incubator.apache.org/thrift>Thrift</a> Protocol. Starting with Hive 0.5.0, you can start a Thrift server by executing the following command:</p>
 <pre tabindex=0><code>hive --service metastore
 </code></pre><p>In versions of Hive earlier than 0.5.0, it&rsquo;s instead necessary to run the Thrift server via direct execution of Java:</p>
-<pre tabindex=0><code>$JAVA\_HOME/bin/java  -Xmx1024m -Dlog4j.configuration=file://$HIVE\_HOME/conf/hms-log4j.properties -Djava.library.path=$HADOOP\_HOME/lib/native/Linux-amd64-64/ -cp $CLASSPATH org.apache.hadoop.hive.metastore.HiveMetaStore
+<pre tabindex=0><code>$JAVA_HOME/bin/java  -Xmx1024m -Dlog4j.configuration=file://$HIVE_HOME/conf/hms-log4j.properties -Djava.library.path=$HADOOP_HOME/lib/native/Linux-amd64-64/ -cp $CLASSPATH org.apache.hadoop.hive.metastore.HiveMetaStore
 </code></pre><p>If you execute Java directly, then JAVA_HOME, HIVE_HOME, HADOOP_HOME must be correctly set; CLASSPATH should contain Hadoop, Hive (lib and auxlib), and Java jars.</p>
 <p><strong>Server Configuration Parameters</strong></p>
 <p>The following example uses a<a href=#remote-metastore-database>Remote Metastore Database</a>.</p>
@@ -495,7 +495,7 @@ ASF
 </table>
 <p>If you are using MySQL as the datastore for metadata, put MySQL jdbc libraries in HIVE_HOME/lib before starting Hive Client or HiveMetastore Server.</p>
 <p>To change the metastore port, use this <code>hive</code> command:</p>
-<pre tabindex=0><code>hive --service metastore -p &lt;port\_num&gt;
+<pre tabindex=0><code>hive --service metastore -p &lt;port_num&gt;
 </code></pre><h3 id=supported-backend-databases-for-metastore>Supported Backend Databases for Metastore</h3>
 <table>
 <thead>
diff --git a/docs/latest/authdev_27362078/index.html b/docs/latest/authdev_27362078/index.html
index d65e487..5affd5f 100644
--- a/docs/latest/authdev_27362078/index.html
+++ b/docs/latest/authdev_27362078/index.html
@@ -299,35 +299,35 @@ The db table determine database level access privileges, which apply to all obje
 <h2 id=42-show-grant>4.2 show grant</h2>
 <h2 id=43-grantrevoke-statement>4.3 grant/revoke statement</h2>
 <pre tabindex=0><code>GRANT
-    priv\_type [(column\_list)]
-      [, priv\_type [(column\_list)]] ...
-    ON [object\_type] priv\_level
+    priv_type [(column_list)]
+      [, priv_type [(column_list)]] ...
+    ON [object_type] priv_level
     TO user [, user] ...
 WITH ADMIN OPTION
 
-object\_type:
+object_type:
     TABLE
 
-priv\_level:
+priv_level:
     *
   | *.*
-  | db\_name.*
-  | db\_name.tbl\_name
-  | tbl\_name
+  | db_name.*
+  | db_name.tbl_name
+  | tbl_name
 
 REVOKE
-    priv\_type [(column\_list)]
-      [, priv\_type [(column\_list)]] ...
-    ON [object\_type] priv\_level
+    priv_type [(column_list)]
+      [, priv_type [(column_list)]] ...
+    ON [object_type] priv_level
     FROM user [, user] ...
 
 REVOKE ALL PRIVILEGES, GRANT OPTION
     FROM user [, user] ...
 
 DENY  
-	priv\_type [(column\_list)]
-      [, priv\_type [(column\_list)]] ...
-    ON [object\_type] priv\_level
+	priv_type [(column_list)]
+      [, priv_type [(column_list)]] ...
+    ON [object_type] priv_level
     FROM user [, user] ...
 
 </code></pre><h1 id=5-authorization-verification>5. Authorization verification</h1>
@@ -417,155 +417,155 @@ This still does not solve the problem if someone accesses the metastore directly
 
 DROP TABLE IF EXISTS {{ROLES}};
 CREATE TABLE {{ROLES}} (
-  {{ROLE\_ID}} bigint(20) NOT NULL,
-  {{CREATE\_TIME}} int(11) NOT NULL,
-  {{OWNER\_NAME}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{ROLE\_NAME}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  PRIMARY KEY  ({{ROLE\_ID}}),
-  UNIQUE KEY {{ROLEENTITYINDEX}} ({{ROLE\_NAME}})
+  {{ROLE_ID}} bigint(20) NOT NULL,
+  {{CREATE_TIME}} int(11) NOT NULL,
+  {{OWNER_NAME}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{ROLE_NAME}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  PRIMARY KEY  ({{ROLE_ID}}),
+  UNIQUE KEY {{ROLEENTITYINDEX}} ({{ROLE_NAME}})
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
 
 --
--- Table structure for table {{ROLE\_MAP}}
+-- Table structure for table {{ROLE_MAP}}
 --
 
-DROP TABLE IF EXISTS {{ROLE\_MAP}};
-CREATE TABLE {{ROLE\_MAP}} (
-  {{ROLE\_GRANT\_ID}} bigint(20) NOT NULL,
-  {{ADD\_TIME}} int(11) NOT NULL,
-  {{GRANT\_OPTION}} smallint(6) NOT NULL,
-  {{GRANTOR}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{GRANTOR\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_NAME}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{ROLE\_ID}} bigint(20) default NULL,
-  PRIMARY KEY  ({{ROLE\_GRANT\_ID}}),
-  UNIQUE KEY {{USERROLEMAPINDEX}} ({{PRINCIPAL\_NAME}},{{ROLE\_ID}},{{GRANTOR}},{{GRANTOR\_TYPE}}),
-  KEY {{ROLE\_MAP\_N49}} ({{ROLE\_ID}}),
-  CONSTRAINT {{ROLE\_MAP\_FK1}} FOREIGN KEY ({{ROLE\_ID}}) REFERENCES {{ROLES}} ({{ROLE\_ID}})
+DROP TABLE IF EXISTS {{ROLE_MAP}};
+CREATE TABLE {{ROLE_MAP}} (
+  {{ROLE_GRANT_ID}} bigint(20) NOT NULL,
+  {{ADD_TIME}} int(11) NOT NULL,
+  {{GRANT_OPTION}} smallint(6) NOT NULL,
+  {{GRANTOR}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{GRANTOR_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_NAME}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{ROLE_ID}} bigint(20) default NULL,
+  PRIMARY KEY  ({{ROLE_GRANT_ID}}),
+  UNIQUE KEY {{USERROLEMAPINDEX}} ({{PRINCIPAL_NAME}},{{ROLE_ID}},{{GRANTOR}},{{GRANTOR_TYPE}}),
+  KEY {{ROLE_MAP_N49}} ({{ROLE_ID}}),
+  CONSTRAINT {{ROLE_MAP_FK1}} FOREIGN KEY ({{ROLE_ID}}) REFERENCES {{ROLES}} ({{ROLE_ID}})
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
 
 --
--- Table structure for table {{GLOBAL\_PRIVS}}
+-- Table structure for table {{GLOBAL_PRIVS}}
 --
 
-DROP TABLE IF EXISTS {{GLOBAL\_PRIVS}};
-CREATE TABLE {{GLOBAL\_PRIVS}} (
-  {{USER\_GRANT\_ID}} bigint(20) NOT NULL,
-  {{CREATE\_TIME}} int(11) NOT NULL,
-  {{GRANT\_OPTION}} smallint(6) NOT NULL,
-  {{GRANTOR}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{GRANTOR\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_NAME}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{USER\_PRIV}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  PRIMARY KEY  ({{USER\_GRANT\_ID}}),
-  UNIQUE KEY {{GLOBALPRIVILEGEINDEX}} ({{PRINCIPAL\_NAME}},{{PRINCIPAL\_TYPE}},{{USER\_PRIV}},{{GRANTOR}},{{GRANTOR\_TYPE}})
+DROP TABLE IF EXISTS {{GLOBAL_PRIVS}};
+CREATE TABLE {{GLOBAL_PRIVS}} (
+  {{USER_GRANT_ID}} bigint(20) NOT NULL,
+  {{CREATE_TIME}} int(11) NOT NULL,
+  {{GRANT_OPTION}} smallint(6) NOT NULL,
+  {{GRANTOR}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{GRANTOR_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_NAME}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{USER_PRIV}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  PRIMARY KEY  ({{USER_GRANT_ID}}),
+  UNIQUE KEY {{GLOBALPRIVILEGEINDEX}} ({{PRINCIPAL_NAME}},{{PRINCIPAL_TYPE}},{{USER_PRIV}},{{GRANTOR}},{{GRANTOR_TYPE}})
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
 
 --
--- Table structure for table {{DB\_PRIVS}}
+-- Table structure for table {{DB_PRIVS}}
 --
 
-DROP TABLE IF EXISTS {{DB\_PRIVS}};
-CREATE TABLE {{DB\_PRIVS}} (
-  {{DB\_GRANT\_ID}} bigint(20) NOT NULL,
-  {{CREATE\_TIME}} int(11) NOT NULL,
-  {{DB\_ID}} bigint(20) default NULL,
-  {{GRANT\_OPTION}} smallint(6) NOT NULL,
-  {{GRANTOR}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{GRANTOR\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_NAME}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{DB\_PRIV}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  PRIMARY KEY  ({{DB\_GRANT\_ID}}),
-  UNIQUE KEY {{DBPRIVILEGEINDEX}} ({{DB\_ID}},{{PRINCIPAL\_NAME}},{{PRINCIPAL\_TYPE}},{{DB\_PRIV}},{{GRANTOR}},{{GRANTOR\_TYPE}}),
-  KEY {{DB\_PRIVS\_N49}} ({{DB\_ID}}),
-  CONSTRAINT {{DB\_PRIVS\_FK1}} FOREIGN KEY ({{DB\_ID}}) REFERENCES {{DBS}} ({{DB\_ID}})
+DROP TABLE IF EXISTS {{DB_PRIVS}};
+CREATE TABLE {{DB_PRIVS}} (
+  {{DB_GRANT_ID}} bigint(20) NOT NULL,
+  {{CREATE_TIME}} int(11) NOT NULL,
+  {{DB_ID}} bigint(20) default NULL,
+  {{GRANT_OPTION}} smallint(6) NOT NULL,
+  {{GRANTOR}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{GRANTOR_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_NAME}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{DB_PRIV}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  PRIMARY KEY  ({{DB_GRANT_ID}}),
+  UNIQUE KEY {{DBPRIVILEGEINDEX}} ({{DB_ID}},{{PRINCIPAL_NAME}},{{PRINCIPAL_TYPE}},{{DB_PRIV}},{{GRANTOR}},{{GRANTOR_TYPE}}),
+  KEY {{DB_PRIVS_N49}} ({{DB_ID}}),
+  CONSTRAINT {{DB_PRIVS_FK1}} FOREIGN KEY ({{DB_ID}}) REFERENCES {{DBS}} ({{DB_ID}})
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
 
 --
--- Table structure for table {{TBL\_PRIVS}}
+-- Table structure for table {{TBL_PRIVS}}
 --
 
-DROP TABLE IF EXISTS {{TBL\_PRIVS}};
-
-CREATE TABLE {{TBL\_PRIVS}} (
-  {{TBL\_GRANT\_ID}} bigint(20) NOT NULL,
-  {{CREATE\_TIME}} int(11) NOT NULL,
-  {{GRANT\_OPTION}} smallint(6) NOT NULL,
-  {{GRANTOR}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{GRANTOR\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_NAME}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{TBL\_PRIV}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{TBL\_ID}} bigint(20) default NULL,
-  PRIMARY KEY  ({{TBL\_GRANT\_ID}}),
-  KEY {{TBL\_PRIVS\_N49}} ({{TBL\_ID}}),
-  KEY {{TABLEPRIVILEGEINDEX}} ({{TBL\_ID}},{{PRINCIPAL\_NAME}},{{PRINCIPAL\_TYPE}},{{TBL\_PRIV}},{{GRANTOR}},{{GRANTOR\_TYPE}}),
-  CONSTRAINT {{TBL\_PRIVS\_FK1}} FOREIGN KEY ({{TBL\_ID}}) REFERENCES {{TBLS}} ({{TBL\_ID}})
+DROP TABLE IF EXISTS {{TBL_PRIVS}};
+
+CREATE TABLE {{TBL_PRIVS}} (
+  {{TBL_GRANT_ID}} bigint(20) NOT NULL,
+  {{CREATE_TIME}} int(11) NOT NULL,
+  {{GRANT_OPTION}} smallint(6) NOT NULL,
+  {{GRANTOR}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{GRANTOR_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_NAME}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{TBL_PRIV}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{TBL_ID}} bigint(20) default NULL,
+  PRIMARY KEY  ({{TBL_GRANT_ID}}),
+  KEY {{TBL_PRIVS_N49}} ({{TBL_ID}}),
+  KEY {{TABLEPRIVILEGEINDEX}} ({{TBL_ID}},{{PRINCIPAL_NAME}},{{PRINCIPAL_TYPE}},{{TBL_PRIV}},{{GRANTOR}},{{GRANTOR_TYPE}}),
+  CONSTRAINT {{TBL_PRIVS_FK1}} FOREIGN KEY ({{TBL_ID}}) REFERENCES {{TBLS}} ({{TBL_ID}})
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
 
 --
--- Table structure for table {{PART\_PRIVS}}
+-- Table structure for table {{PART_PRIVS}}
 --
 
-DROP TABLE IF EXISTS {{PART\_PRIVS}};
-
-CREATE TABLE {{PART\_PRIVS}} (
-  {{PART\_GRANT\_ID}} bigint(20) NOT NULL,
-  {{CREATE\_TIME}} int(11) NOT NULL,
-  {{GRANT\_OPTION}} smallint(6) NOT NULL,
-  {{GRANTOR}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{GRANTOR\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PART\_ID}} bigint(20) default NULL,
-  {{PRINCIPAL\_NAME}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PART\_PRIV}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  PRIMARY KEY  ({{PART\_GRANT\_ID}}),
-  KEY {{PARTPRIVILEGEINDEX}} ({{PART\_ID}},{{PRINCIPAL\_NAME}},{{PRINCIPAL\_TYPE}},{{PART\_PRIV}},{{GRANTOR}},{{GRANTOR\_TYPE}}),
-  KEY {{PART\_PRIVS\_N49}} ({{PART\_ID}}),
-  CONSTRAINT {{PART\_PRIVS\_FK1}} FOREIGN KEY ({{PART\_ID}}) REFERENCES {{PARTITIONS}} ({{PART\_ID}})
+DROP TABLE IF EXISTS {{PART_PRIVS}};
+
+CREATE TABLE {{PART_PRIVS}} (
+  {{PART_GRANT_ID}} bigint(20) NOT NULL,
+  {{CREATE_TIME}} int(11) NOT NULL,
+  {{GRANT_OPTION}} smallint(6) NOT NULL,
+  {{GRANTOR}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{GRANTOR_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PART_ID}} bigint(20) default NULL,
+  {{PRINCIPAL_NAME}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PART_PRIV}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  PRIMARY KEY  ({{PART_GRANT_ID}}),
+  KEY {{PARTPRIVILEGEINDEX}} ({{PART_ID}},{{PRINCIPAL_NAME}},{{PRINCIPAL_TYPE}},{{PART_PRIV}},{{GRANTOR}},{{GRANTOR_TYPE}}),
+  KEY {{PART_PRIVS_N49}} ({{PART_ID}}),
+  CONSTRAINT {{PART_PRIVS_FK1}} FOREIGN KEY ({{PART_ID}}) REFERENCES {{PARTITIONS}} ({{PART_ID}})
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
 
 --
--- Table structure for table {{TBL\_COL\_PRIVS}}
+-- Table structure for table {{TBL_COL_PRIVS}}
 --
 
-DROP TABLE IF EXISTS {{TBL\_COL\_PRIVS}};
-CREATE TABLE {{TBL\_COL\_PRIVS}} (
-  {{TBL\_COLUMN\_GRANT\_ID}} bigint(20) NOT NULL,
-  {{COLUMN\_NAME}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{CREATE\_TIME}} int(11) NOT NULL,
-  {{GRANT\_OPTION}} smallint(6) NOT NULL,
-  {{GRANTOR}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{GRANTOR\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_NAME}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{TBL\_COL\_PRIV}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{TBL\_ID}} bigint(20) default NULL,
-  PRIMARY KEY  ({{TBL\_COLUMN\_GRANT\_ID}}),
-  KEY {{TABLECOLUMNPRIVILEGEINDEX}} ({{TBL\_ID}},{{COLUMN\_NAME}},{{PRINCIPAL\_NAME}},{{PRINCIPAL\_TYPE}},{{TBL\_COL\_PRIV}},{{GRANTOR}},{{GRANTOR\_TYPE}}),
-  KEY {{TBL\_COL\_PRIVS\_N49}} ({{TBL\_ID}}),
-  CONSTRAINT {{TBL\_COL\_PRIVS\_FK1}} FOREIGN KEY ({{TBL\_ID}}) REFERENCES {{TBLS}} ({{TBL\_ID}})
+DROP TABLE IF EXISTS {{TBL_COL_PRIVS}};
+CREATE TABLE {{TBL_COL_PRIVS}} (
+  {{TBL_COLUMN_GRANT_ID}} bigint(20) NOT NULL,
+  {{COLUMN_NAME}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{CREATE_TIME}} int(11) NOT NULL,
+  {{GRANT_OPTION}} smallint(6) NOT NULL,
+  {{GRANTOR}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{GRANTOR_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_NAME}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{TBL_COL_PRIV}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{TBL_ID}} bigint(20) default NULL,
+  PRIMARY KEY  ({{TBL_COLUMN_GRANT_ID}}),
+  KEY {{TABLECOLUMNPRIVILEGEINDEX}} ({{TBL_ID}},{{COLUMN_NAME}},{{PRINCIPAL_NAME}},{{PRINCIPAL_TYPE}},{{TBL_COL_PRIV}},{{GRANTOR}},{{GRANTOR_TYPE}}),
+  KEY {{TBL_COL_PRIVS_N49}} ({{TBL_ID}}),
+  CONSTRAINT {{TBL_COL_PRIVS_FK1}} FOREIGN KEY ({{TBL_ID}}) REFERENCES {{TBLS}} ({{TBL_ID}})
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
 
-DROP TABLE IF EXISTS {{PART\_COL\_PRIVS}};
-CREATE TABLE {{PART\_COL\_PRIVS}} (
-  {{PART\_COLUMN\_GRANT\_ID}} bigint(20) NOT NULL,
-  {{COLUMN\_NAME}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{CREATE\_TIME}} int(11) NOT NULL,
-  {{GRANT\_OPTION}} smallint(6) NOT NULL,
-  {{GRANTOR}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{GRANTOR\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PART\_ID}} bigint(20) default NULL,
-  {{PRINCIPAL\_NAME}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PRINCIPAL\_TYPE}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  {{PART\_COL\_PRIV}} varchar(128) character set latin1 collate latin1\_bin default NULL,
-  PRIMARY KEY  ({{PART\_COLUMN\_GRANT\_ID}}),
-  KEY {{PART\_COL\_PRIVS\_N49}} ({{PART\_ID}}),
-  KEY {{PARTITIONCOLUMNPRIVILEGEINDEX}} ({{PART\_ID}},{{COLUMN\_NAME}},{{PRINCIPAL\_NAME}},{{PRINCIPAL\_TYPE}},{{PART\_COL\_PRIV}},{{GRANTOR}},{{GRANTOR\_TYPE}}),
-  CONSTRAINT {{PART\_COL\_PRIVS\_FK1}} FOREIGN KEY ({{PART\_ID}}) REFERENCES {{PARTITIONS}} ({{PART\_ID}})
+DROP TABLE IF EXISTS {{PART_COL_PRIVS}};
+CREATE TABLE {{PART_COL_PRIVS}} (
+  {{PART_COLUMN_GRANT_ID}} bigint(20) NOT NULL,
+  {{COLUMN_NAME}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{CREATE_TIME}} int(11) NOT NULL,
+  {{GRANT_OPTION}} smallint(6) NOT NULL,
+  {{GRANTOR}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{GRANTOR_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PART_ID}} bigint(20) default NULL,
+  {{PRINCIPAL_NAME}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PRINCIPAL_TYPE}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  {{PART_COL_PRIV}} varchar(128) character set latin1 collate latin1_bin default NULL,
+  PRIMARY KEY  ({{PART_COLUMN_GRANT_ID}}),
+  KEY {{PART_COL_PRIVS_N49}} ({{PART_ID}}),
+  KEY {{PARTITIONCOLUMNPRIVILEGEINDEX}} ({{PART_ID}},{{COLUMN_NAME}},{{PRINCIPAL_NAME}},{{PRINCIPAL_TYPE}},{{PART_COL_PRIV}},{{GRANTOR}},{{GRANTOR_TYPE}}),
+  CONSTRAINT {{PART_COL_PRIVS_FK1}} FOREIGN KEY ({{PART_ID}}) REFERENCES {{PARTITIONS}} ({{PART_ID}})
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
 
 </code></pre><hr>
diff --git a/docs/latest/avroserde_27850707/index.html b/docs/latest/avroserde_27850707/index.html
index 275f607..8556724 100644
--- a/docs/latest/avroserde_27850707/index.html
+++ b/docs/latest/avroserde_27850707/index.html
@@ -300,7 +300,7 @@ ASF
   OUTPUTFORMAT
   'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'
   TBLPROPERTIES (
-    'avro.schema.url'='http://schema\_provider/kst.avsc');
+    'avro.schema.url'='http://schema_provider/kst.avsc');
 </code></pre><p>In this example we&rsquo;re pulling the source-of-truth reader schema from a webserver. Other options for providing the schema are described below.</p>
 <p>Add the Avro files to the database (or create an external table) using standard Hive operations (<a href=https://hive.apache.org/docs/latest/languagemanual-dml_27362036/>http://wiki.apache.org/hadoop/Hive/LanguageManual/DML</a>).</p>
 <p>This table might result in a description as below:</p>
@@ -313,7 +313,7 @@ boolean1        boolean from deserializer
 long1   bigint  from deserializer
 float1  float   from deserializer
 double1 double  from deserializer
-inner\_record1   struct&lt;int\_in\_inner\_record1:int,string\_in\_inner\_record1:string&gt; from deserializer
+inner_record1   struct&lt;int_in_inner_record1:int,string_in_inner_record1:string&gt; from deserializer
 enum1   string  from deserializer
 array1  array&lt;string&gt;   from deserializer
 map1    map&lt;string,string&gt;      from deserializer
@@ -335,7 +335,7 @@ bytes1  binary  from deserializer
     long1 bigint,
     float1 float,
     double1 double,
-    inner\_record1 struct&lt;int\_in\_inner\_record1:int,string\_in\_inner\_record1:string&gt;,
+    inner_record1 struct&lt;int_in_inner_record1:int,string_in_inner_record1:string&gt;,
     enum1 string,
     array1 array&lt;string&gt;,
     map1 map&lt;string,string&gt;,
@@ -356,7 +356,7 @@ boolean1        boolean from deserializer
 long1   bigint  from deserializer
 float1  float   from deserializer
 double1 double  from deserializer
-inner\_record1   struct&lt;int\_in\_inner\_record1:int,string\_in\_inner\_record1:string&gt; from deserializer
+inner_record1   struct&lt;int_in_inner_record1:int,string_in_inner_record1:string&gt; from deserializer
 enum1   string  from deserializer
 array1  array&lt;string&gt;   from deserializer
 map1    map&lt;string,string&gt;      from deserializer
@@ -378,7 +378,7 @@ bytes1  binary  from deserializer
 <p>Hive is very forgiving about types: it will attempt to store whatever value matches the provided column in the equivalent column position in the new table. No matching is done on column names, for instance. Therefore, it is incumbent on the query writer to make sure the target column types are correct. If they are not, Avro may accept the type or it may throw an exception; this is dependent on the particular combination of types.</p>
 <h5 id=example>Example</h5>
 <p>Consider the following Hive table, which covers all types of Hive data types, making it a good example:</p>
-<pre tabindex=0><code>CREATE TABLE test\_serializer(string1 STRING,
+<pre tabindex=0><code>CREATE TABLE test_serializer(string1 STRING,
                              int1 INT,
                              tinyint1 TINYINT,
                              smallint1 SMALLINT,
@@ -406,7 +406,7 @@ bytes1  binary  from deserializer
 <p>To save this table as an Avro file, create an equivalent Avro schema (the namespace and actual name of the record are not important):</p>
 <pre tabindex=0><code>{
   &quot;namespace&quot;: &quot;com.linkedin.haivvreo&quot;,
-  &quot;name&quot;: &quot;test\_serializer&quot;,
+  &quot;name&quot;: &quot;test_serializer&quot;,
   &quot;type&quot;: &quot;record&quot;,
   &quot;fields&quot;: [
     { &quot;name&quot;:&quot;string1&quot;, &quot;type&quot;:&quot;string&quot; },
@@ -419,16 +419,16 @@ bytes1  binary  from deserializer
     { &quot;name&quot;:&quot;double1&quot;, &quot;type&quot;:&quot;double&quot; },
     { &quot;name&quot;:&quot;list1&quot;, &quot;type&quot;:{&quot;type&quot;:&quot;array&quot;, &quot;items&quot;:&quot;string&quot;} },
     { &quot;name&quot;:&quot;map1&quot;, &quot;type&quot;:{&quot;type&quot;:&quot;map&quot;, &quot;values&quot;:&quot;int&quot;} },
-    { &quot;name&quot;:&quot;struct1&quot;, &quot;type&quot;:{&quot;type&quot;:&quot;record&quot;, &quot;name&quot;:&quot;struct1\_name&quot;, &quot;fields&quot;: [
+    { &quot;name&quot;:&quot;struct1&quot;, &quot;type&quot;:{&quot;type&quot;:&quot;record&quot;, &quot;name&quot;:&quot;struct1_name&quot;, &quot;fields&quot;: [
           { &quot;name&quot;:&quot;sInt&quot;, &quot;type&quot;:&quot;int&quot; }, { &quot;name&quot;:&quot;sBoolean&quot;, &quot;type&quot;:&quot;boolean&quot; }, { &quot;name&quot;:&quot;sString&quot;, &quot;type&quot;:&quot;string&quot; } ] } },
     { &quot;name&quot;:&quot;union1&quot;, &quot;type&quot;:[&quot;float&quot;, &quot;boolean&quot;, &quot;string&quot;] },
-    { &quot;name&quot;:&quot;enum1&quot;, &quot;type&quot;:{&quot;type&quot;:&quot;enum&quot;, &quot;name&quot;:&quot;enum1\_values&quot;, &quot;symbols&quot;:[&quot;BLUE&quot;,&quot;RED&quot;, &quot;GREEN&quot;]} },
+    { &quot;name&quot;:&quot;enum1&quot;, &quot;type&quot;:{&quot;type&quot;:&quot;enum&quot;, &quot;name&quot;:&quot;enum1_values&quot;, &quot;symbols&quot;:[&quot;BLUE&quot;,&quot;RED&quot;, &quot;GREEN&quot;]} },
     { &quot;name&quot;:&quot;nullableint&quot;, &quot;type&quot;:[&quot;int&quot;, &quot;null&quot;] },
     { &quot;name&quot;:&quot;bytes1&quot;, &quot;type&quot;:&quot;bytes&quot; },
     { &quot;name&quot;:&quot;fixed1&quot;, &quot;type&quot;:{&quot;type&quot;:&quot;fixed&quot;, &quot;name&quot;:&quot;threebytes&quot;, &quot;size&quot;:3} }
   ] }
 </code></pre><p>Then you can write it out to Avro with:</p>
-<pre tabindex=0><code>CREATE TABLE as\_avro
+<pre tabindex=0><code>CREATE TABLE as_avro
   ROW FORMAT SERDE
   'org.apache.hadoop.hive.serde2.avro.AvroSerDe'
   STORED as INPUTFORMAT
@@ -436,13 +436,13 @@ bytes1  binary  from deserializer
   OUTPUTFORMAT
   'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'
   TBLPROPERTIES (
-    'avro.schema.url'='file:///path/to/the/schema/test\_serializer.avsc');
+    'avro.schema.url'='file:///path/to/the/schema/test_serializer.avsc');
  
-INSERT OVERWRITE TABLE as\_avro SELECT * FROM test\_serializer;
+INSERT OVERWRITE TABLE as_avro SELECT * FROM test_serializer;
 
 </code></pre><h4 id=hive-014-and-later>Hive 0.14 and later</h4>
 <p>In Hive versions 0.14 and later, you do not need to create the Avro schema manually. The procedure shown above to save a table as an Avro file reduces to just a DDL statement followed by an insert into the table.</p>
-<pre tabindex=0><code>CREATE TABLE as\_avro(string1 STRING,
+<pre tabindex=0><code>CREATE TABLE as_avro(string1 STRING,
                      int1 INT,
                      tinyint1 TINYINT,
                      smallint1 SMALLINT,
@@ -459,7 +459,7 @@ INSERT OVERWRITE TABLE as\_avro SELECT * FROM test\_serializer;
                      bytes1 BINARY,
                      fixed1 BINARY)
 STORED AS AVRO;
-INSERT OVERWRITE TABLE as\_avro SELECT * FROM test\_serializer;
+INSERT OVERWRITE TABLE as_avro SELECT * FROM test_serializer;
 
 </code></pre><h4 id=avro-file-extension>Avro file extension</h4>
 <p>The files that are written by the Hive job are valid Avro files, however, MapReduce doesn&rsquo;t add the standard .avro extension. If you copy these files out, you&rsquo;ll likely want to rename them with .avro.</p>
@@ -481,7 +481,7 @@ INSERT OVERWRITE TABLE as\_avro SELECT * FROM test\_serializer;
   TBLPROPERTIES (
     'avro.schema.literal'='{
       &quot;namespace&quot;: &quot;com.howdy&quot;,
-      &quot;name&quot;: &quot;some\_schema&quot;,
+      &quot;name&quot;: &quot;some_schema&quot;,
       &quot;type&quot;: &quot;record&quot;,
       &quot;fields&quot;: [ { &quot;name&quot;:&quot;string1&quot;,&quot;type&quot;:&quot;string&quot;}]
     }');
@@ -502,7 +502,7 @@ CREATE TABLE example
     'avro.schema.literal'='${hiveconf:schema}');
 
 </code></pre><p>To execute this script file, assuming $SCHEMA has been defined to be the escaped schema value:</p>
-<pre tabindex=0><code>hive --hiveconf schema=&quot;${SCHEMA}&quot; -f your\_script\_file.sql
+<pre tabindex=0><code>hive --hiveconf schema=&quot;${SCHEMA}&quot; -f your_script_file.sql
 </code></pre><p>Note that $SCHEMA is interpolated into the quotes to correctly handle spaces within the schema.</p>
 <h5 id=use-none-to-ignore-either-avroschemaliteral-or-avroschemaurl>Use none to ignore either avro.schema.literal or avro.schema.url</h5>
 <p>Hive does not provide an easy way to unset or remove a property. If you wish to switch from using URL or schema to the other, set the to-be-ignored value to <strong>none</strong> and the AvroSerde will treat it as if it were not set.</p>
diff --git a/docs/latest/binary-datatype-proposal_27826614/index.html b/docs/latest/binary-datatype-proposal_27826614/index.html
index 3e7bdfd..ab35bb0 100644
--- a/docs/latest/binary-datatype-proposal_27826614/index.html
+++ b/docs/latest/binary-datatype-proposal_27826614/index.html
@@ -120,7 +120,7 @@ ASF
 <p>Hive is designed to work with big data. Often in such cases, a row in a data might be very wide with hundreds of columns. Sometimes, user is just interested in few of those columns and doesn&rsquo;t want to bother about exact type information for rest of columns. In such cases, he may just declare the types of those columns as binary and Hive will not try to interpret those columns. One important thing to note is this binary type is not modeled after blob type as it exists in other sy [...]
 <h3 id=syntax>Syntax:</h3>
 <pre tabindex=0><code>
-create table binary\_table (a string, b binary);
+create table binary_table (a string, b binary);
 
 </code></pre><h3 id=how-is-binary-represented-internally-in-hive>How is &lsquo;binary&rsquo; represented internally in Hive</h3>
 <p>Binary type in Hive will map to &lsquo;binary&rsquo; data type in thrift. </p>
diff --git a/docs/latest/column-statistics-in-hive_29131019/index.html b/docs/latest/column-statistics-in-hive_29131019/index.html
index f92ddfa..50346a6 100644
--- a/docs/latest/column-statistics-in-hive_29131019/index.html
+++ b/docs/latest/column-statistics-in-hive_29131019/index.html
@@ -132,7 +132,7 @@ ASF
 <p><code>analyze table t [partition p] compute statistics for [columns c,...];</code></p>
 <p>Please note that table and column aliases are not supported in the analyze statement.</p>
 <p>To view column stats :</p>
-<pre tabindex=0><code>describe formatted [table\_name] [column\_name];
+<pre tabindex=0><code>describe formatted [table_name] [column_name];
 </code></pre><h3 id=metastore-schema><strong>Metastore Schema</strong></h3>
 <p>To persist column level statistics, we propose to add the following new tables,</p>
 <p>CREATE TABLE TAB_COL_STATS<br>
diff --git a/docs/latest/common-table-expression_38572242/index.html b/docs/latest/common-table-expression_38572242/index.html
index 73794ff..1bbb569 100644
--- a/docs/latest/common-table-expression_38572242/index.html
+++ b/docs/latest/common-table-expression_38572242/index.html
@@ -120,7 +120,7 @@ ASF
 <p>Common Table Expressions are added in Hive 0.13.0 with <a href=https://issues.apache.org/jira/browse/HIVE-1180>HIVE-1180</a>.</p>
 <h2 id=common-table-expression-syntax>Common Table Expression Syntax</h2>
 <pre tabindex=0><code>withClause: cteClause (, cteClause)*
-cteClause: cte\_name AS (select statment)
+cteClause: cte_name AS (select statment)
 </code></pre><h3 id=additional-grammar-rules>Additional Grammar Rules</h3>
 <ul>
 <li>The WITH clause is not supported within SubQuery Blocks</li>
diff --git a/docs/latest/compaction-pooling_240884493/index.html b/docs/latest/compaction-pooling_240884493/index.html
index 6d8e98a..21ddd19 100644
--- a/docs/latest/compaction-pooling_240884493/index.html
+++ b/docs/latest/compaction-pooling_240884493/index.html
@@ -121,12 +121,12 @@ ASF
 <p>Compaction requests can be assigned to pools in three different ways.</p>
 <h4 id=automatic-pool-assignment>Automatic pool assignment</h4>
 <p>Databases, tables and partitions can be assigned to compaction pools through the</p>
-<pre tabindex=0><code>hive.compactor.worker.pool={pool\_name}
+<pre tabindex=0><code>hive.compactor.worker.pool={pool_name}
 </code></pre><p><a href=https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions#HiveTransactions-TableProperties>Database/Table property</a>. If the property is set on Database level, it applies to all tables and partitions. The pool also can be assigned on a table/partition level, in this case it overrides the Database level value (if set). <br>
 If any of the above is set, it is used by the <em>Initiator</em> during the creation of the compaction requests.</p>
 <h4 id=manual-pool-assignment>Manual pool assignment</h4>
 <p>The compaction request also can be assigned to a pool by using the ALTER TABLE COMPACT command (E.g. manual compaction). If provided, this value overrides the <em>hive.compactor.worker.pool</em> value on any level.</p>
-<pre tabindex=0><code>ALTER TABLE COMPACT table\_name POOL 'pool\_name';
+<pre tabindex=0><code>ALTER TABLE COMPACT table_name POOL 'pool_name';
 </code></pre><h4 id=implicit-pool-assignment>Implicit pool assignment</h4>
 <p>Tables, partitions and manual compaction requests without specified pool name are implicitly assigned to the default pool.</p>
 <h3 id=pool-timeout>Pool timeout</h3>
@@ -141,7 +141,7 @@ If any of the above is set, it is used by the <em>Initiator</em> during the crea
 <p>The timeout can be disabled by setting the configuration property to 0.</p>
 <h3 id=labeled-worker-pools>Labeled worker pools</h3>
 <p>The labeled worker pools can be defined through the </p>
-<pre tabindex=0><code>hive.compactor.worker.{poolname}.threads={thread\_count} 
+<pre tabindex=0><code>hive.compactor.worker.{poolname}.threads={thread_count} 
 </code></pre><p>configuration setting. Please note that in this case the configuration key is also dynamic.</p>
 <h3 id=default-pool>Default pool</h3>
 <p>The default pool is responsible for processing the non-labeled and timed-out compaction requests. On a cluster-wide level, at least 1 worker thread on at least one node should be assigned to the default pool, otherwise compaction requests may never be processed.</p>
diff --git a/docs/latest/compressedstorage_27362073/index.html b/docs/latest/compressedstorage_27362073/index.html
index 72a67d5..95fabc4 100644
--- a/docs/latest/compressedstorage_27362073/index.html
+++ b/docs/latest/compressedstorage_27362073/index.html
@@ -128,14 +128,14 @@ LOAD DATA LOCAL INPATH '/tmp/weblogs/20090603-access.log.gz' INTO TABLE raw;
 <pre tabindex=0><code>CREATE TABLE raw (line STRING)
    ROW FORMAT DELIMITED FIELDS TERMINATED BY '\t' LINES TERMINATED BY '\n';
 
-CREATE TABLE raw\_sequence (line STRING)
+CREATE TABLE raw_sequence (line STRING)
    STORED AS SEQUENCEFILE;
 
 LOAD DATA LOCAL INPATH '/tmp/weblogs/20090603-access.log.gz' INTO TABLE raw;
 
 SET hive.exec.compress.output=true;
 SET io.seqfile.compression.type=BLOCK; -- NONE/RECORD/BLOCK (see below)
-INSERT OVERWRITE TABLE raw\_sequence SELECT * FROM raw;
+INSERT OVERWRITE TABLE raw_sequence SELECT * FROM raw;
 
 </code></pre><p>The value for io.seqfile.compression.type determines how the compression is performed. Record compresses each value individually while BLOCK buffers up 1MB (default) before doing compression.</p>
 <h3 id=lzo-compression>LZO Compression</h3>
diff --git a/docs/latest/configuration-properties_27842758/index.html b/docs/latest/configuration-properties_27842758/index.html
index 57ba1fe..b367a08 100644
--- a/docs/latest/configuration-properties_27842758/index.html
+++ b/docs/latest/configuration-properties_27842758/index.html
@@ -2884,7 +2884,7 @@ With negative value, it&rsquo;s checked for all of the operations regardless of
 <p>The path to the Kerberos Keytab file containing the HiveServer2 WebUI SPNEGO service principal.</p>
 <h5 id=hiveserver2webuispnegoprincipal>hive.server2.webui.spnego.principal</h5>
 <ul>
-<li>Default Value: <code>HTTP/\_HOST@EXAMPLE.COM</code></li>
+<li>Default Value: <code>HTTP/_HOST@EXAMPLE.COM</code></li>
 <li>Added In: Hive 2.0.0 with <a href=https://issues.apache.org/jira/browse/HIVE-12485>HIVE-12485</a></li>
 </ul>
 <p>The HiveServer2 WebUI SPNEGO service principal. The special string _HOST will be replaced automatically with the value of <strong><a href=#hiveserver2webuihost>hive.server2.webui.host</a></strong> or the correct host name.</p>
@@ -4316,7 +4316,7 @@ Caution: Rebuilding indexes can be a lengthy and computationally expensive opera
 <p>Clean extra nodes at the end of the session.</p>
 <h5 id=hivelockmgrzookeeperdefaultpartitionname>hive.lockmgr.zookeeper.default.partition.name</h5>
 <ul>
-<li>Default Value: <code>\_\_HIVE\_DEFAULT\_ZOOKEEPER\_PARTITION\_\_</code></li>
+<li>Default Value: <code>__HIVE_DEFAULT_ZOOKEEPER_PARTITION__</code></li>
 <li>Added In: Hive 0.7.0 with <a href=https://issues.apache.org/jira/browse/HIVE-1293>HIVE-1293</a></li>
 </ul>
 <p>The default partition name when ZooKeeperHiveLockManager is the  <a href=#**hive-lock-manager**><strong>hive lock manager</strong></a> .</p>
diff --git a/docs/latest/correlation-optimizer_34019487/index.html b/docs/latest/correlation-optimizer_34019487/index.html
index db818f6..b2e59b2 100644
--- a/docs/latest/correlation-optimizer_34019487/index.html
+++ b/docs/latest/correlation-optimizer_34019487/index.html
@@ -156,30 +156,30 @@ GROUP BY /*AGG2*/ t1.key;
 <p><img src=attachments/34019487/34177456.png alt></p>
 <p><strong>Figure 4: The optimized operator tree of Example 2</strong></p>
 <h3 id=23-example-3>2.3 Example 3</h3>
-<pre tabindex=0><code>SELECT count(distinct ws1.ws\_order\_number) as order\_count,
-       sum(ws1.ws\_ext\_ship\_cost) as total\_shipping\_cost,
-       sum(ws1.ws\_net\_profit) as total\_net\_profit
-FROM web\_sales ws1
-JOIN /*MJ1*/ customer\_address ca ON (ws1.ws\_ship\_addr\_sk = ca.ca\_address\_sk)
-JOIN /*MJ2*/ web\_site s ON (ws1.ws\_web\_site\_sk = s.web\_site\_sk)
-JOIN /*MJ3*/ date\_dim d ON (ws1.ws\_ship\_date\_sk = d.d\_date\_sk)
-LEFT SEMI JOIN /*JOIN4*/ (SELECT ws2.ws\_order\_number as ws\_order\_number
-               	          FROM web\_sales ws2 JOIN /*JOIN1*/ web\_sales ws3
-               	          ON (ws2.ws\_order\_number = ws3.ws\_order\_number)
-               	          WHERE ws2.ws\_warehouse\_sk &lt;&gt; ws3.ws\_warehouse\_sk) ws\_wh1
-ON (ws1.ws\_order\_number = ws\_wh1.ws\_order\_number)
-LEFT SEMI JOIN /*JOIN4*/ (SELECT wr\_order\_number
-               	          FROM web\_returns wr
-               	          JOIN /*JOIN3*/ (SELECT ws4.ws\_order\_number as ws\_order\_number
-                                          FROM web\_sales ws4 JOIN /*JOIN2*/ web\_sales ws5
-                                          ON (ws4.ws\_order\_number = ws5.ws\_order\_number)
-                                          WHERE ws4.ws\_warehouse\_sk &lt;&gt; ws5.ws\_warehouse\_sk) ws\_wh2
-                          ON (wr.wr\_order\_number = ws\_wh2.ws\_order\_number)) tmp1
-ON (ws1.ws\_order\_number = tmp1.wr\_order\_number)
-WHERE d.d\_date &gt;= '2001-05-01' and
-      d.d\_date &lt;= '2001-06-30' and
-      ca.ca\_state = 'NC' and
-      s.web\_company\_name = 'pri';
+<pre tabindex=0><code>SELECT count(distinct ws1.ws_order_number) as order_count,
+       sum(ws1.ws_ext_ship_cost) as total_shipping_cost,
+       sum(ws1.ws_net_profit) as total_net_profit
+FROM web_sales ws1
+JOIN /*MJ1*/ customer_address ca ON (ws1.ws_ship_addr_sk = ca.ca_address_sk)
+JOIN /*MJ2*/ web_site s ON (ws1.ws_web_site_sk = s.web_site_sk)
+JOIN /*MJ3*/ date_dim d ON (ws1.ws_ship_date_sk = d.d_date_sk)
+LEFT SEMI JOIN /*JOIN4*/ (SELECT ws2.ws_order_number as ws_order_number
+               	          FROM web_sales ws2 JOIN /*JOIN1*/ web_sales ws3
+               	          ON (ws2.ws_order_number = ws3.ws_order_number)
+               	          WHERE ws2.ws_warehouse_sk &lt;&gt; ws3.ws_warehouse_sk) ws_wh1
+ON (ws1.ws_order_number = ws_wh1.ws_order_number)
+LEFT SEMI JOIN /*JOIN4*/ (SELECT wr_order_number
+               	          FROM web_returns wr
+               	          JOIN /*JOIN3*/ (SELECT ws4.ws_order_number as ws_order_number
+                                          FROM web_sales ws4 JOIN /*JOIN2*/ web_sales ws5
+                                          ON (ws4.ws_order_number = ws5.ws_order_number)
+                                          WHERE ws4.ws_warehouse_sk &lt;&gt; ws5.ws_warehouse_sk) ws_wh2
+                          ON (wr.wr_order_number = ws_wh2.ws_order_number)) tmp1
+ON (ws1.ws_order_number = tmp1.wr_order_number)
+WHERE d.d_date &gt;= '2001-05-01' and
+      d.d_date &lt;= '2001-06-30' and
+      ca.ca_state = 'NC' and
+      s.web_company_name = 'pri';
 
 </code></pre><p>The original operator tree generated by Hive is shown below.</p>
 <p><img src=attachments/34019487/34177457.png alt></p>
diff --git a/docs/latest/csv-serde_48202659/index.html b/docs/latest/csv-serde_48202659/index.html
index 6a4346d..e90ad60 100644
--- a/docs/latest/csv-serde_48202659/index.html
+++ b/docs/latest/csv-serde_48202659/index.html
@@ -133,7 +133,7 @@ ASF
 <p>This SerDe works for most CSV data, but does not handle embedded newlines. To use the SerDe, specify the fully qualified class name org.apache.hadoop.hive.serde2.OpenCSVSerde.  </p>
 <p>Documentation is based on original documentation at <a href=https://github.com/ogrodnek/csv-serde>https://github.com/ogrodnek/csv-serde</a>.</p>
 <p><strong>Create table, specify CSV properties</strong></p>
-<pre tabindex=0><code>CREATE TABLE my\_table(a string, b string, ...)
+<pre tabindex=0><code>CREATE TABLE my_table(a string, b string, ...)
 ROW FORMAT SERDE 'org.apache.hadoop.hive.serde2.OpenCSVSerde'
 WITH SERDEPROPERTIES (
    &quot;separatorChar&quot; = &quot;\t&quot;,
@@ -142,9 +142,9 @@ WITH SERDEPROPERTIES (
 )   
 STORED AS TEXTFILE;
 </code></pre><p><strong>Default separator, quote, and escape characters if unspecified</strong></p>
-<pre tabindex=0><code>DEFAULT\_ESCAPE\_CHARACTER \
-DEFAULT\_QUOTE\_CHARACTER  &quot;
-DEFAULT\_SEPARATOR        ,
+<pre tabindex=0><code>DEFAULT_ESCAPE_CHARACTER \
+DEFAULT_QUOTE_CHARACTER  &quot;
+DEFAULT_SEPARATOR        ,
 </code></pre><p>For general information about SerDes, see <a href=#hive-serde>Hive SerDe</a> in the Developer Guide. Also see <a href=https://hive.apache.org/docs/latest/serde_27362059/>SerDe</a> for details about input and output processing.</p>
 <h3 id=versions>Versions</h3>
 <p>The CSVSerde has been built and tested against Hive 0.14 and later, and uses <a href=http://opencsv.sourceforge.net/>Open-CSV</a> 2.3 which is bundled with the Hive distribution.</p>
diff --git a/docs/latest/data-connector-for-hive-and-hive-like-engines_288885794/index.html b/docs/latest/data-connector-for-hive-and-hive-like-engines_288885794/index.html
index 48e15ab..6bec608 100644
--- a/docs/latest/data-connector-for-hive-and-hive-like-engines_288885794/index.html
+++ b/docs/latest/data-connector-for-hive-and-hive-like-engines_288885794/index.html
@@ -131,37 +131,37 @@ ASF
 <ol>
 <li>Create a connector first.</li>
 </ol>
-<pre tabindex=0><code>    CREATE CONNECTOR hiveserver\_connector TYPE 'hivejdbc' URL 'jdbc:hive2://&lt;maskedhost&gt;:10000'   
+<pre tabindex=0><code>    CREATE CONNECTOR hiveserver_connector TYPE 'hivejdbc' URL 'jdbc:hive2://&lt;maskedhost&gt;:10000'   
      WITH DCPROPERTIES (&quot;hive.sql.dbcp.username&quot;=&quot;hive&quot;, &quot;hive.sql.dbcp.password&quot;=&quot;hive&quot;);  
   
 
 </code></pre><ol start=2>
 <li>Create a database of type REMOTE in hive using the connector from Step 1. This maps a remote database named &ldquo;<code>*default*</code>&rdquo; to a hive database named &ldquo;<em><code>hiveserver_remote</code></em>&rdquo; in hive.</li>
 </ol>
-<pre tabindex=0><code>         CREATE REMOTE DATABASE hiveserver\_remote USING hiveserver\_connector   
+<pre tabindex=0><code>         CREATE REMOTE DATABASE hiveserver_remote USING hiveserver_connector   
          WITH DBPROPERTIES (&quot;connector.remoteDbName&quot;=&quot;default&quot;);  
      
    3. Use the tables in REMOTE database much like the JDBC-storagehandler based tables in hive. One big difference   
       is that the metadata for these tables are never persisted in hive. Currently, create/alter/drop table DDLs   
       are not supported in REMOTE databases.   
   
-     0: jdbc:hive2://localhost:10000&gt; USE hiveserver\_remote;
-</code></pre><p><code>0: jdbc:hive2://localhost:10000> **describe formatted test\_emr\_tbl;**</code></p>
+     0: jdbc:hive2://localhost:10000&gt; USE hiveserver_remote;
+</code></pre><p><code>0: jdbc:hive2://localhost:10000> **describe formatted test_emr_tbl;**</code></p>
 <pre tabindex=0><code>+-------------------------------+-------------------------------------------------+----------------------------------------------------+  
-|           col\_name            |                    data\_type                    |                      comment                       |  
+|           col_name            |                    data_type                    |                      comment                       |  
 +-------------------------------+-------------------------------------------------+----------------------------------------------------+  
 | tblkey                        | int                                             | from deserializer                                  |  
 | descr                         | string                                          | from deserializer                                  |  
 |                               | NULL                                            | NULL                                               |  
 | # Detailed Table Information  | NULL                                            | NULL                                               |  
-| Database:                     | emr\_db                                          | NULL                                               |  
+| Database:                     | emr_db                                          | NULL                                               |  
 | OwnerType:                    | USER                                            | NULL                                               |  
 | Owner:                        | null                                            | NULL                                               |  
 | CreateTime:                   | UNKNOWN                                         | NULL                                               |  
 | LastAccessTime:               | UNKNOWN                                         | NULL                                               |  
 | Retention:                    | 0                                               | NULL                                               |  
-| Location:                     | [file:/tmp/hive/warehouse/external/test\_emr\_tbl](http://file/tmp/hive/warehouse/external/test_emr_tbl)  | NULL                                               |  
-| Table Type:                   | EXTERNAL\_TABLE                                  | NULL                                               |  
+| Location:                     | [file:/tmp/hive/warehouse/external/test_emr_tbl](http://file/tmp/hive/warehouse/external/test_emr_tbl)  | NULL                                               |  
+| Table Type:                   | EXTERNAL_TABLE                                  | NULL                                               |  
 | Table Parameters:             | NULL                                            | NULL                                               |  
 |                               | EXTERNAL                                        | TRUE                                               |  
 |                               | hive.sql.database.type                          | HIVE                                               |  
@@ -170,8 +170,8 @@ ASF
 |                               | hive.sql.jdbc.driver                            | org.apache.hive.jdbc.HiveDriver                    |  
 |                               | hive.sql.jdbc.url                               | jdbc:hive2://&lt;maskedIP&gt;.compute-1.amazonaws.com:10000 |  
 |                               | hive.sql.schema                                 | default                                            |  
-|                               | hive.sql.table                                  | test\_emr\_tbl                                       |  
-|                               | storage\_handler                                 | org.apache.hive.storage.jdbc.JdbcStorageHandler    |  
+|                               | hive.sql.table                                  | test_emr_tbl                                       |  
+|                               | storage_handler                                 | org.apache.hive.storage.jdbc.JdbcStorageHandler    |  
 |                               | NULL                                            | NULL                                               |  
 | # Storage Information         | NULL                                            | NULL                                               |  
 | SerDe Library:                | org.apache.hive.storage.jdbc.JdbcSerDe          | NULL                                               |  
@@ -187,15 +187,15 @@ ASF
 </code></pre><p><code>33 rows selected (6.099 seconds)</code></p>
 <pre tabindex=0><code>    4. Offload the remote table to local cluster, run CTAS (example below pulls in all the data into the local table,   
        but you can pull in select columns and rows by applying predicates)
-</code></pre><p><code>0: jdbc:hive2://localhost:10000> **create table default.emr\_clone as select * from test\_emr\_tbl;**</code></p>
-<p><code>INFO  : Completed executing command(queryId=ngangam\_20240129182608\_db20e2bb-1db3-473f-9564-0d81b01228bc); Time taken: 6.492 seconds</code></p>
+</code></pre><p><code>0: jdbc:hive2://localhost:10000> **create table default.emr_clone as select * from test_emr_tbl;**</code></p>
+<p><code>INFO  : Completed executing command(queryId=ngangam_20240129182608_db20e2bb-1db3-473f-9564-0d81b01228bc); Time taken: 6.492 seconds</code></p>
 <p><code>INFO  : OK</code></p>
 <p><code>2 rows affected (14.802 seconds)</code></p>
-<p><strong><code>0: jdbc:hive2://localhost:10000> select count(*) from default.emr\_clone;</code></strong></p>
-<p><code>INFO  : Completed executing command(queryId=ngangam\_20240129182647\_7544c9d1-c68b-4a34-b6b0-910945a1dba5); Time taken: 2.344 seconds</code></p>
+<p><strong><code>0: jdbc:hive2://localhost:10000> select count(*) from default.emr_clone;</code></strong></p>
+<p><code>INFO  : Completed executing command(queryId=ngangam_20240129182647_7544c9d1-c68b-4a34-b6b0-910945a1dba5); Time taken: 2.344 seconds</code></p>
 <p><code>INFO  : OK</code></p>
 <pre tabindex=0><code>     +------+  
-     | \_c0  |  
+     | _c0  |  
      +------+  
      | 2    |  
      +------+
@@ -207,7 +207,7 @@ ASF
 <p>INFO  : Completed executing command(queryId=ngangam_20240129191217_79b9e874-197d-4c31-8164-1ec2397bbff7); Time taken: 0.001 seconds</p>
 <p>INFO  : OK</p>
 <pre tabindex=0><code>     +----------------------+---------------------+  
-     | test\_emr\_tbl.tblkey  | test\_emr\_tbl.descr  |  
+     | test_emr_tbl.tblkey  | test_emr_tbl.descr  |  
      +----------------------+---------------------+  
      | 2                    | test 2              |  
      +----------------------+---------------------+
diff --git a/docs/latest/data-connectors-in-hive_177049669/index.html b/docs/latest/data-connectors-in-hive_177049669/index.html
index 1453d10..4d1e221 100644
--- a/docs/latest/data-connectors-in-hive_177049669/index.html
+++ b/docs/latest/data-connectors-in-hive_177049669/index.html
@@ -124,7 +124,7 @@ ASF
 <li>The metadata for the mapped table is static. It does not track changes to the remote table. If remote table has changed (added columns or dropped columns), the mapped hive table has to be dropped and re-created. This management compounds when one has constantly changing tables.</li>
 </ul>
 <p>Data connectors allow users to map a database/schema in the remote datasource to a Hive database. Such databases are referred to as REMOTE databases in hive.</p>
-<pre tabindex=0><code>       CREATE REMOTE DATABASE postgres\_db1 USING &lt;connectorName&gt; WITH DBPROPERTIES ('connector.remoteDbName'='db1');
+<pre tabindex=0><code>       CREATE REMOTE DATABASE postgres_db1 USING &lt;connectorName&gt; WITH DBPROPERTIES ('connector.remoteDbName'='db1');
 </code></pre><ul>
 <li>All the tables within a mapped database (<em>db1</em>) are automatically visible from Hive. The metadata for these tables are not persisted in Hive metastore&rsquo;s backend. They are retrieved at runtime via a live connector.</li>
 <li>All future tables will automatically be visible in Hive.</li>
@@ -135,21 +135,21 @@ ASF
 <ol>
 <li>Create a connector first.</li>
 </ol>
-<pre tabindex=0><code>    CREATE CONNECTOR pg\_local TYPE 'postgres' URL 'jdbc:&lt;postgresql://localhost:5432&gt;' WITH DCPROPERTIES (&quot;hive.sql.dbcp.username&quot;=&quot;postgres&quot;, &quot;hive.sql.dbcp.password&quot;=&quot;postgres&quot;);  
+<pre tabindex=0><code>    CREATE CONNECTOR pg_local TYPE 'postgres' URL 'jdbc:&lt;postgresql://localhost:5432&gt;' WITH DCPROPERTIES (&quot;hive.sql.dbcp.username&quot;=&quot;postgres&quot;, &quot;hive.sql.dbcp.password&quot;=&quot;postgres&quot;);  
   
 
 </code></pre><ol start=2>
-<li>Create a database of type REMOTE in hive using the connector from Step1.   This maps a remote database named &ldquo;<code>*hive\_hms\_testing*</code>&rdquo; to a hive database named &ldquo;<em><code>pg_hive_testing</code></em>&rdquo; in hive.</li>
+<li>Create a database of type REMOTE in hive using the connector from Step1.   This maps a remote database named &ldquo;<code>*hive_hms_testing*</code>&rdquo; to a hive database named &ldquo;<em><code>pg_hive_testing</code></em>&rdquo; in hive.</li>
 </ol>
-<pre tabindex=0><code>         CREATE REMOTE DATABASE pg\_hive\_testing USING pg\_local WITH DBPROPERTIES (&quot;connector.remoteDbName&quot;=&quot;hive\_hms\_testing&quot;);  
+<pre tabindex=0><code>         CREATE REMOTE DATABASE pg_hive_testing USING pg_local WITH DBPROPERTIES (&quot;connector.remoteDbName&quot;=&quot;hive_hms_testing&quot;);  
   
          // USING keystore instead of cleartext passwords in DCPROPERTIES  
-         CREATE CONNECTOR pg\_local\_ks TYPE 'postgres' URL 'jdbc:&lt;postgresql://localhost:5432/hive_hms_testing&gt;' WITH DCPROPERTIES(&quot;hive.sql.dbcp.username&quot;=&quot;postgres&quot;,&quot;hive.sql.dbcp.password.keystore&quot;=&quot;jceks://app/local/hive/secrets.jceks&quot; &quot;hive.sql.dbcp.password.key&quot;=&quot;postgres.credential&quot;);  
-         CREATE REMOTE DATABASE pg\_ks\_local USING pg\_local\_ks(&quot;connector.remoteDbName&quot;=&quot;hive\_hms\_testing&quot;);  
+         CREATE CONNECTOR pg_local_ks TYPE 'postgres' URL 'jdbc:&lt;postgresql://localhost:5432/hive_hms_testing&gt;' WITH DCPROPERTIES(&quot;hive.sql.dbcp.username&quot;=&quot;postgres&quot;,&quot;hive.sql.dbcp.password.keystore&quot;=&quot;jceks://app/local/hive/secrets.jceks&quot; &quot;hive.sql.dbcp.password.key&quot;=&quot;postgres.credential&quot;);  
+         CREATE REMOTE DATABASE pg_ks_local USING pg_local_ks(&quot;connector.remoteDbName&quot;=&quot;hive_hms_testing&quot;);  
      
    3. Use the tables in REMOTE database much like the JDBC-storagehandler based tables in hive. One big difference is that the metadata for these tables are never persisted in hive. Currently, create/alter/drop table DDLs are not supported in REMOTE databases.   
   
-         USE pg\_hive\_testing;  
+         USE pg_hive_testing;  
          SHOW TABLES;  
          DESCRIBE [formatted] &lt;tablename&gt;;  
          SELECT &lt;col1&gt; from &lt;tablename&gt; where &lt;filter1&gt; and &lt;filter2&gt;;
diff --git a/docs/latest/datasketches-integration_177050456/index.html b/docs/latest/datasketches-integration_177050456/index.html
index 2015df4..4a78bc5 100644
--- a/docs/latest/datasketches-integration_177050456/index.html
+++ b/docs/latest/datasketches-integration_177050456/index.html
@@ -127,7 +127,7 @@ ASF
 <ul>
 <li><a href=#rewrite-countdistinctx>Rewrite COUNT(DISTINCT(X))</a></li>
 <li><a href=#rewrite-percentile_discp-withing-grouporder-by-x>Rewrite percentile_disc(p) withing group(order by x)</a></li>
-<li><a href=#rewrite-cume\_dist---over--order-by-id->Rewrite cume_dist() over (order by id)</a></li>
+<li><a href=#rewrite-cume_dist---over--order-by-id->Rewrite cume_dist() over (order by id)</a></li>
 <li><a href=#rewrite-ntile>Rewrite NTILE</a></li>
 <li><a href=#rewrite-rank>Rewrite RANK</a></li>
 </ul>
@@ -234,66 +234,66 @@ The BI mode is about making rewrites automatically to sketch functions if possib
 <p>This feature can be toggled using the <strong>hive.optimize.bi.rewrite.countdistinct.enabled</strong> conf key</p>
 <p>The used distinct sketch family can be configured using: <strong>hive.optimize.bi.rewrite.countdistinct.sketch</strong> (currently only hll is available).</p>
 <p>This feature could rewrite</p>
-<pre tabindex=0><code>select category, count(distinct id) from sketch\_input group by category
+<pre tabindex=0><code>select category, count(distinct id) from sketch_input group by category
 </code></pre><p>to use a distinct count sketch to answer the query by rewriting it to</p>
-<pre tabindex=0><code>select category, round(ds\_hll\_estimate(ds\_hll\_sketch(id))) from sketch\_input
+<pre tabindex=0><code>select category, round(ds_hll_estimate(ds_hll_sketch(id))) from sketch_input
 </code></pre><h2 id=rewrite-percentile_discp-withing-grouporder-by-x>Rewrite percentile_disc(p) withing group(order by x)</h2>
 <p>This feature can be toggled using the<strong>hive.optimize.bi.rewrite.percentile_disc.enabled</strong> conf key</p>
 <p>The used histogram sketch family can be configured using: <strong>hive.optimize.bi.rewrite.percentile_disc.sketch</strong> (currently only kll is available).</p>
 <p>This feature could rewrite</p>
-<pre tabindex=0><code>select percentile\_disc(0.3) within group(order by id) from sketch\_input
+<pre tabindex=0><code>select percentile_disc(0.3) within group(order by id) from sketch_input
 </code></pre><p>to use a histogram sketch to answer the query by rewriting to</p>
-<pre tabindex=0><code>select ds\_kll\_quantile(ds\_kll\_sketch(id), 0.3) from sketch\_input
+<pre tabindex=0><code>select ds_kll_quantile(ds_kll_sketch(id), 0.3) from sketch_input
 </code></pre><h2 id=rewritecume_dist-over-order-by-id>Rewrite cume_dist() over (order by id)</h2>
 <p>This feature can be toggled using the**<a href=http://hive.optimize.bi>hive.optimize.bi</a>.rewrite.cume_dist.enabled** conf key</p>
 <p>The used histogram sketch family can be configured using: <a href=http://hive.optimize.bi>hive.optimize.bi</a>.rewrite.cume_dist.sketch (currently only kll is available).</p>
-<pre tabindex=0><code>select id,cume\_dist() over (order by id) from sketch\_input
+<pre tabindex=0><code>select id,cume_dist() over (order by id) from sketch_input
 </code></pre><p>to use a histogram sketch to answer the query by rewriting to</p>
-<pre tabindex=0><code>SELECT id, CAST(DS\_KLL\_RANK(t2.sketch, idVal) AS DOUBLE) 
-FROM (SELECT id, CAST(COALESCE(CAST(id AS FLOAT), 340282346638528860000000000000000000000) AS FLOAT) AS idVal FROM sketch\_input) AS t,
-(SELECT DS\_KLL\_SKETCH(CAST(`id` AS FLOAT)) AS `sketch` FROM sketch\_input) AS t2
+<pre tabindex=0><code>SELECT id, CAST(DS_KLL_RANK(t2.sketch, idVal) AS DOUBLE) 
+FROM (SELECT id, CAST(COALESCE(CAST(id AS FLOAT), 340282346638528860000000000000000000000) AS FLOAT) AS idVal FROM sketch_input) AS t,
+(SELECT DS_KLL_SKETCH(CAST(`id` AS FLOAT)) AS `sketch` FROM sketch_input) AS t2
 </code></pre><h2 id=rewrite-ntile>Rewrite NTILE</h2>
 <p>This feature can be toggled using the <strong><a href=http://hive.optimize.bi>hive.optimize.bi</a>.rewrite.ntile.enabled</strong> conf key</p>
 <p>The used histogram sketch family can be configured using: <a href=http://hive.optimize.bi>hive.optimize.bi</a>.rewrite.ntile.sketch (currently only kll is available).</p>
 <p>This feature can rewrite</p>
 <pre tabindex=0><code>select id,
        ntile(4) over (order by id
-from sketch\_input
+from sketch_input
 order by id
 </code></pre><p>To use a histogram sketch to calculate the NTILE&rsquo;s value:</p>
 <pre tabindex=0><code>select id,
-        case when ceil(ds\_kll\_cdf(ds, CAST(id AS FLOAT) )[0]*4) &lt; 1 then 1 else ceil(ds\_kll\_cdf(ds, CAST(id AS FLOAT) )[0]*4) end
-from sketch\_input
-join ( select ds\_kll\_sketch(cast(id as float)) as ds from sketch\_input ) q
+        case when ceil(ds_kll_cdf(ds, CAST(id AS FLOAT) )[0]*4) &lt; 1 then 1 else ceil(ds_kll_cdf(ds, CAST(id AS FLOAT) )[0]*4) end
+from sketch_input
+join ( select ds_kll_sketch(cast(id as float)) as ds from sketch_input ) q
 order by id
 
 select id,
                 rank() over (order by id),
-                case when ds\_kll\_n(ds) &lt; (ceil(ds\_kll\_rank(ds, CAST(id AS FLOAT) )*ds\_kll\_n(ds))+1) then ds\_kll\_n(ds) else (ceil(ds\_kll\_rank(ds, CAST(id AS FLOAT) )*ds\_kll\_n(ds))+1) end
+                case when ds_kll_n(ds) &lt; (ceil(ds_kll_rank(ds, CAST(id AS FLOAT) )*ds_kll_n(ds))+1) then ds_kll_n(ds) else (ceil(ds_kll_rank(ds, CAST(id AS FLOAT) )*ds_kll_n(ds))+1) end
 
 </code></pre><h2 id=rewrite-rank>Rewrite RANK</h2>
 <p>This feature can be toggled using the <strong>hive.optimize.bi.rewrite.rank.enabled</strong> conf key</p>
 <p>The used histogram sketch family can be configured using: <strong>hive.optimize.bi.rewrite.rank.sketch</strong> (currently only kll is available).</p>
 <pre tabindex=0><code>select id,
        rank() over (order by id)
-from sketch\_input
+from sketch_input
 order by id
 </code></pre><p>is rewritten to</p>
 <pre tabindex=0><code>select id,
-       case when ds\_kll\_n(ds) &lt; (ceil(ds\_kll\_rank(ds, CAST(id AS FLOAT) )*ds\_kll\_n(ds))+1) then ds\_kll\_n(ds) else (ceil(ds\_kll\_rank(ds, CAST(id AS FLOAT) )*ds\_kll\_n(ds))+1) end
-from sketch\_input
-join ( select ds\_kll\_sketch(cast(id as float)) as ds from sketch\_input ) q
+       case when ds_kll_n(ds) &lt; (ceil(ds_kll_rank(ds, CAST(id AS FLOAT) )*ds_kll_n(ds))+1) then ds_kll_n(ds) else (ceil(ds_kll_rank(ds, CAST(id AS FLOAT) )*ds_kll_n(ds))+1) end
+from sketch_input
+join ( select ds_kll_sketch(cast(id as float)) as ds from sketch_input ) q
 order by id
 </code></pre><h1 id=examples>Examples</h1>
 <h2 id=simple-distinct-counting-examples-using-hll>Simple distinct counting examples using HLL</h2>
 <ul>
 <li>Prepare sample table</li>
 </ul>
-<pre tabindex=0><code>create table sketch\_input (id int, category char(1))
+<pre tabindex=0><code>create table sketch_input (id int, category char(1))
 STORED AS ORC
 TBLPROPERTIES ('transactional'='true');
 
-insert into table sketch\_input values
+insert into table sketch_input values
   (1,'a'),(1, 'a'), (2, 'a'), (3, 'a'), (4, 'a'), (5, 'a'), (6, 'a'), (7, 'a'), (8, 'a'), (9, 'a'), (10, 'a'),
   (6,'b'),(6, 'b'), (7, 'b'), (8, 'b'), (9, 'b'), (10, 'b'), (11, 'b'), (12, 'b'), (13, 'b'), (14, 'b'), (15, 'b')
 ; 
@@ -303,41 +303,41 @@ insert into table sketch\_input values
 </li>
 </ul>
 <pre tabindex=0><code>-- build sketches per category
-create temporary table sketch\_intermediate (category char(1), sketch binary);
-insert into sketch\_intermediate select category, ds\_hll\_sketch(id) from sketch\_input group by category;
+create temporary table sketch_intermediate (category char(1), sketch binary);
+insert into sketch_intermediate select category, ds_hll_sketch(id) from sketch_input group by category;
 
 -- get unique count estimates per category
-select category, ds\_hll\_estimate(sketch) from sketch\_intermediate;
+select category, ds_hll_estimate(sketch) from sketch_intermediate;
 
 -- union sketches across categories and get overall unique count estimate
-select ds\_hll\_estimate(ds\_hll\_union(sketch)) from sketch\_intermediate;
+select ds_hll_estimate(ds_hll_union(sketch)) from sketch_intermediate;
 </code></pre><ul>
 <li>
 <h3 id=use-hll-to-compute-distinct-values-without-intermediate-table>Use HLL to compute distinct values without intermediate table</h3>
 </li>
 </ul>
-<pre tabindex=0><code>select category, ds\_hll\_estimate(ds\_hll\_sketch(id)) from sketch\_input group by category;
-select ds\_hll\_estimate(ds\_hll\_sketch(id)) from sketch\_input;
+<pre tabindex=0><code>select category, ds_hll_estimate(ds_hll_sketch(id)) from sketch_input group by category;
+select ds_hll_estimate(ds_hll_sketch(id)) from sketch_input;
 </code></pre><ul>
 <li>
 <h3 id=use-hll-to-compute-distinct-values-transparently-thru-bi-mode>Use HLL to compute distinct values transparently thru BI mode</h3>
 </li>
 </ul>
 <pre tabindex=0><code>set hive.optimize.bi.enabled=true;
-select category,count(distinct id) from sketch\_input group by category;
-select count(distinct id) from sketch\_input;
+select category,count(distinct id) from sketch_input group by category;
+select count(distinct id) from sketch_input;
 </code></pre><ul>
 <li>
 <h3 id=use-hll-to-compute-distinct-values-transparently-thru-bi-mode---while-utilizing-a-materialized-view-to-store-the-intermediate-sketches>Use HLL to compute distinct values transparently thru BI mode - while utilizing a Materialized View to store the intermediate sketches.</h3>
 </li>
 </ul>
 <pre tabindex=0><code>-- create an MV to store precomputed HLL values
-create  materialized view mv\_1 as
-  select category, ds\_hll\_sketch(id) from sketch\_input group by category;
+create  materialized view mv_1 as
+  select category, ds_hll_sketch(id) from sketch_input group by category;
 
 set hive.optimize.bi.enabled=true;
-select category,count(distinct id) from sketch\_input group by category;
-select count(distinct id) from sketch\_input;
+select category,count(distinct id) from sketch_input group by category;
+select count(distinct id) from sketch_input;
 </code></pre>
 </div>
 </div>
diff --git a/docs/latest/developerguide_27362074/index.html b/docs/latest/developerguide_27362074/index.html
index e90f655..e0a0b33 100644
--- a/docs/latest/developerguide_27362074/index.html
+++ b/docs/latest/developerguide_27362074/index.html
@@ -225,7 +225,7 @@ ASF
 <li>LazySimpleSerDe: This SerDe can be used to read the same data format as MetadataTypedColumnsetSerDe and TCTLSeparatedProtocol, however, it creates Objects in a lazy way which provides better performance. Starting in <a href=https://issues.apache.org/jira/browse/HIVE-7142>Hive 0.14.0</a> it also supports read/write data with a specified encode charset, for example:</li>
 </ul>
 <pre tabindex=0><code>ALTER TABLE person SET SERDEPROPERTIES ('serialization.encoding'='GBK');
-</code></pre><p>LazySimpleSerDe can treat &lsquo;T&rsquo;, &rsquo;t', &lsquo;F&rsquo;, &lsquo;f&rsquo;, &lsquo;1&rsquo;, and &lsquo;0&rsquo; as extended, legal boolean literals if the configuration property <a href=#hive-lazysimple-extended\_boolean\_literal>hive.lazysimple.extended_boolean_literal</a> is set to <code>true</code> (<a href=https://issues.apache.org/jira/browse/HIVE-3635>Hive 0.14.0</a> and later). The default is <code>false</code>, which means only &lsquo;TRUE&rsquo; and  [...]
+</code></pre><p>LazySimpleSerDe can treat &lsquo;T&rsquo;, &rsquo;t', &lsquo;F&rsquo;, &lsquo;f&rsquo;, &lsquo;1&rsquo;, and &lsquo;0&rsquo; as extended, legal boolean literals if the configuration property <a href=#hive-lazysimple-extended_boolean_literal>hive.lazysimple.extended_boolean_literal</a> is set to <code>true</code> (<a href=https://issues.apache.org/jira/browse/HIVE-3635>Hive 0.14.0</a> and later). The default is <code>false</code>, which means only &lsquo;TRUE&rsquo; and &l [...]
 <ul>
 <li>ThriftSerDe: This SerDe is used to read/write Thrift serialized objects. The class file for the Thrift object must be loaded first.</li>
 <li>DynamicSerDe: This SerDe also read/write Thrift serialized objects, but it understands Thrift DDL so the schema of the object can be provided at runtime. Also it supports a lot of different protocols, including TBinaryProtocol, TJSONProtocol, TCTLSeparatedProtocol (which writes data in delimited records).</li>
@@ -378,9 +378,9 @@ ASF
 </code></pre><p>If Hive fails at runtime, try &lsquo;<code>ant very-clean package</code>&rsquo; to delete the Ivy cache before rebuilding.</p>
 <h3 id=running-hive-without-a-hadoop-cluster>Running Hive Without a Hadoop Cluster</h3>
 <p>From Thejas:</p>
-<pre tabindex=0><code>export HIVE\_OPTS='--hiveconf mapred.job.tracker=local --hiveconf fs.default.name=file:///tmp \
+<pre tabindex=0><code>export HIVE_OPTS='--hiveconf mapred.job.tracker=local --hiveconf fs.default.name=file:///tmp \
     --hiveconf hive.metastore.warehouse.dir=file:///tmp/warehouse \
-    --hiveconf javax.jdo.option.ConnectionURL=jdbc:derby:;databaseName=/tmp/metastore\_db;create=true'
+    --hiveconf javax.jdo.option.ConnectionURL=jdbc:derby:;databaseName=/tmp/metastore_db;create=true'
 
 </code></pre><p>Then you can run &lsquo;<code>build/dist/bin/hive</code>&rsquo; and it will work against your local file system.</p>
 <h2 id=unit-tests-and-debugging>Unit tests and debugging</h2>
@@ -432,7 +432,7 @@ ASF
 <li><code>build/ql/test/logs/groupby1.q.out</code> - Actual query result for the test. This result is compared to the expected result as part of the test.</li>
 </ul>
 <p>Run the set of unit tests matching a regex, e.g. partition_wise_fileformat tests 10-16:</p>
-<pre tabindex=0><code>ant test -Dtestcase=TestCliDriver -Dqfile\_regex=partition\_wise\_fileformat1[0-6]
+<pre tabindex=0><code>ant test -Dtestcase=TestCliDriver -Dqfile_regex=partition_wise_fileformat1[0-6]
 
 </code></pre><p>Note that this option matches against the basename of the test without the .q suffix.</p>
 <p>Apparently the Hive tests do not run successfully after a clean unless you run <code>ant package</code> first. Not sure why build.xml doesn&rsquo;t encode this dependency.</p>
@@ -484,15 +484,15 @@ svn diff &gt; patch.txt
 </code></pre><ul>
 <li>Run ant test with additional options to tell the Java VM that is running Hive server-side code to wait for the debugger to attach. First define some convenient macros for debugging. You can put it in your .bashrc or .cshrc.</li>
 </ul>
-<pre tabindex=0><code>    &gt; export HIVE\_DEBUG\_PORT=8000
-    &gt; export HIVE\_DEBUG=&quot;-Xdebug -Xrunjdwp:transport=dt\_socket,address=${HIVE\_DEBUG\_PORT},server=y,suspend=y&quot;
+<pre tabindex=0><code>    &gt; export HIVE_DEBUG_PORT=8000
+    &gt; export HIVE_DEBUG=&quot;-Xdebug -Xrunjdwp:transport=dt_socket,address=${HIVE_DEBUG_PORT},server=y,suspend=y&quot;
 
 </code></pre><p>In particular HIVE_DEBUG_PORT is the port number that the JVM is listening on and the debugger will attach to. Then run the unit test as follows:</p>
-<pre tabindex=0><code>    &gt; export HADOOP\_OPTS=$HIVE\_DEBUG
+<pre tabindex=0><code>    &gt; export HADOOP_OPTS=$HIVE_DEBUG
     &gt; ant test -Dtestcase=TestCliDriver -Dqfile=&lt;mytest&gt;.q
 
 </code></pre><p>The unit test will run until it shows:</p>
-<pre tabindex=0><code>     [junit] Listening for transport dt\_socket at address: 8000
+<pre tabindex=0><code>     [junit] Listening for transport dt_socket at address: 8000
 
 </code></pre><ul>
 <li>Now, you can use jdb to attach to port 8000 to debug</li>
@@ -511,7 +511,7 @@ svn diff &gt; patch.txt
 <h4 id=debugging-without-ant-client-and-server-side>Debugging without Ant (Client and Server Side)</h4>
 <p>There is another way of debugging Hive code without going through Ant.<br>
 You need to install Hadoop and set the environment variable HADOOP_HOME to that.</p>
-<pre tabindex=0><code>    &gt; export HADOOP\_HOME=&lt;your hadoop home&gt;
+<pre tabindex=0><code>    &gt; export HADOOP_HOME=&lt;your hadoop home&gt;
  
 </code></pre><p>Then, start Hive:</p>
 <pre tabindex=0><code>    &gt;  ./build/dist/bin/hive --debug
diff --git a/docs/latest/druid-integration_65866491/index.html b/docs/latest/druid-integration_65866491/index.html
index 12ced4f..61eb27c 100644
--- a/docs/latest/druid-integration_65866491/index.html
+++ b/docs/latest/druid-integration_65866491/index.html
@@ -183,15 +183,15 @@ ASF
 <p>First, you need to set the Hive property <code>hive.druid.broker.address.default</code> in your configuration to point to the broker address:</p>
 <pre tabindex=0><code>SET hive.druid.broker.address.default=10.5.0.10:8082;
 </code></pre><p>Then, to create a table that we can query from Hive, we execute the following statement in Hive:</p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE druid\_table\_1
+<pre tabindex=0><code>CREATE EXTERNAL TABLE druid_table_1
 STORED BY 'org.apache.hadoop.hive.druid.DruidStorageHandler'
 TBLPROPERTIES (&quot;druid.datasource&quot; = &quot;wikiticker&quot;);
 </code></pre><p>Observe that you need to specify the <em>datasource</em> as TBLPROPERTIES using the <code>druid.datasource</code> property. Further, observe that the table needs to be created as <em>EXTERNAL</em>, as data is stored in Druid. The table is just a logical entity that we will use to express our queries, but <em>there is no data movement when we create the table</em>. In fact, what happened under the hood when you execute that statement, is that Hive sends a <em><a href=http: [...]
 <p>If we execute a <em>DESCRIBE</em> statement, we can actually see the information about the table:</p>
-<pre tabindex=0><code>hive&gt; DESCRIBE FORMATTED druid\_table\_1;
+<pre tabindex=0><code>hive&gt; DESCRIBE FORMATTED druid_table_1;
 OK
-# col\_name            	data\_type           	comment
-\_\_time              	timestamp           	from deserializer
+# col_name            	data_type           	comment
+__time              	timestamp           	from deserializer
 added               	bigint              	from deserializer
 channel             	string              	from deserializer
 cityname            	string              	from deserializer
@@ -212,25 +212,25 @@ page                	string              	from deserializer
 regionisocode       	string              	from deserializer
 regionname          	string              	from deserializer
 user                	string              	from deserializer
-user\_unique         	string              	from deserializer
+user_unique         	string              	from deserializer
 # Detailed Table Information
 Database:           	druid
 Owner:              	user1
 CreateTime:         	Thu Aug 18 19:09:10 BST 2016
 LastAccessTime:     	UNKNOWN
 Retention:          	0
-Location:           	hdfs:/tmp/user1/hive/warehouse/druid.db/druid\_table\_1
-Table Type:         	EXTERNAL\_TABLE
+Location:           	hdfs:/tmp/user1/hive/warehouse/druid.db/druid_table_1
+Table Type:         	EXTERNAL_TABLE
 Table Parameters:
-	COLUMN\_STATS\_ACCURATE	{\&quot;BASIC\_STATS\&quot;:\&quot;true\&quot;}
+	COLUMN_STATS_ACCURATE	{\&quot;BASIC_STATS\&quot;:\&quot;true\&quot;}
 	EXTERNAL            	TRUE
 	druid.datasource    	wikiticker
 	numFiles            	0
 	numRows             	0
 	rawDataSize         	0
-	storage\_handler     	org.apache.hadoop.hive.druid.DruidStorageHandler
+	storage_handler     	org.apache.hadoop.hive.druid.DruidStorageHandler
 	totalSize           	0
-	transient\_lastDdlTime	1471543750
+	transient_lastDdlTime	1471543750
 # Storage Information
 SerDe Library:      	org.apache.hadoop.hive.druid.serde.DruidSerDe
 InputFormat:        	null
@@ -246,22 +246,22 @@ Time taken: 0.111 seconds, Fetched: 55 row(s)
 <h3 id=create-druid-datasources-from-hive>Create Druid datasources from Hive</h3>
 <p>If we want to manage the data in the Druid datasources from Hive, there are multiple possible scenarios.</p>
 <p>For instance, we might want to create an empty table backed by Druid using a <em>CREATE TABLE</em> statement and then append and overwrite data using <em>INSERT</em> and <em>INSERT OVERWRITE</em> Hive statements, respectively.</p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE druid\_table\_1
-(`\_\_time` TIMESTAMP, `dimension1` STRING, `dimension2` STRING, `metric1` INT, `metric2` FLOAT)
+<pre tabindex=0><code>CREATE EXTERNAL TABLE druid_table_1
+(`__time` TIMESTAMP, `dimension1` STRING, `dimension2` STRING, `metric1` INT, `metric2` FLOAT)
 STORED BY 'org.apache.hadoop.hive.druid.DruidStorageHandler';
 
 </code></pre><p>Another possible scenario is that our data is stored in Hive tables and we want to preprocess it and create Druid datasources from Hive to accelerate our SQL query workload. We can do that by executing a <em>Create Table As Select</em> (CTAS) statement. For example:</p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE druid\_table\_1
+<pre tabindex=0><code>CREATE EXTERNAL TABLE druid_table_1
 STORED BY 'org.apache.hadoop.hive.druid.DruidStorageHandler'
 AS
-&lt;select `timecolumn` as `\_\_time`, `dimension1`, `dimension2`, `metric1`, `metric2`....&gt;;
+&lt;select `timecolumn` as `__time`, `dimension1`, `dimension2`, `metric1`, `metric2`....&gt;;
 </code></pre><p>Observe that we still create three different groups of columns corresponding to the Druid categories: the <strong>timestamp</strong> column (<code>__time</code>) mandatory in Druid, the <strong>dimension</strong> columns (whose type is STRING), and the <strong>metrics</strong> columns (all the rest).</p>
 <p>In both statements, the column types (either specified statically for <em>CREATE TABLE</em> statements or inferred from the query result for <em>CTAS</em> statements) are used to infer the corresponding Druid column category.</p>
 <p>Further, note that if we do not specify the value for the <code>druid.datasource</code> property, Hive automatically uses the fully qualified name of the table to create the corresponding datasource with the same name.</p>
 <p>Version Info</p>
 <p><strong>Version 2.2.0: CREATE TABLE syntax when data is managed via hive.</strong></p>
-<pre tabindex=0><code>CREATE TABLE druid\_table\_1
-(`\_\_time` TIMESTAMP, `dimension1` STRING, `dimension2` STRING, `metric1` INT, `metric2` FLOAT)
+<pre tabindex=0><code>CREATE TABLE druid_table_1
+(`__time` TIMESTAMP, `dimension1` STRING, `dimension2` STRING, `metric1` INT, `metric2` FLOAT)
 STORED BY 'org.apache.hadoop.hive.druid.DruidStorageHandler';
 </code></pre><p> NOTE - Before Hive 3.0.0, we do not use <em>EXTERNAL</em> tables and do not specify the value for the <code>druid.datasource</code> property.</p>
 <p><strong>For versions 3.0.0+, All Druid tables are EXTERNAL (<a href=https://issues.apache.org/jira/browse/HIVE-20085>HIVE-20085</a>).</strong></p>
@@ -270,7 +270,7 @@ STORED BY 'org.apache.hadoop.hive.druid.DruidStorageHandler';
 <p>Integration with Druid Kafka Indexing Service is introduced in Hive 3.0.0 (<a href=https://jira.apache.org/jira/browse/HIVE-18976>HIVE-18976</a>).</p>
 <p><a href=http://druid.io/docs/latest/development/extensions-core/kafka-ingestion.html>Druid Kafka Indexing Service</a> supports exactly-once ingestion from Kafka topic by managing the creation and lifetime of Kafka indexing tasks. We can manage Druid Kafka Ingestion using Hive <em>CREATE TABLE</em> statement as shown below.</p>
 <p><strong>Druid Kafka Ingestion</strong></p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE druid\_kafka\_table\_1(`\_\_time` timestamp,`dimension1` string, `dimension1` string, `metric1` int, `metric2 double ....)
+<pre tabindex=0><code>CREATE EXTERNAL TABLE druid_kafka_table_1(`__time` timestamp,`dimension1` string, `dimension1` string, `metric1` int, `metric2 double ....)
         STORED BY 'org.apache.hadoop.hive.druid.DruidStorageHandler'
         TBLPROPERTIES (
         &quot;kafka.bootstrap.servers&quot; = &quot;localhost:9092&quot;,
@@ -286,9 +286,9 @@ STORED BY 'org.apache.hadoop.hive.druid.DruidStorageHandler';
 <p>Observe that we specified kafka topic name and kafka bootstrap servers as part of the table properties. Other tunings for <a href=http://druid.io/docs/latest/development/extensions-core/kafka-ingestion.html>Druid Kafka Indexing Service</a> can also be specified by prefixing them with <em>&lsquo;druid.kafka.ingestion.&rsquo;  e.g.</em> to configure duration of druid ingestion tasks we can add*&ldquo;druid.kafka.ingestion.taskDuration&rdquo; = &ldquo;PT60S&rdquo;* as a table property. </p>
 <h5 id=startstopreset-druid-kafka-ingestion>Start/Stop/Reset Druid Kafka ingestion</h5>
 <p>We can Start/Stop/Reset druid kafka ingestion using sql statement shown below. </p>
-<pre tabindex=0><code>ALTER TABLE druid\_kafka\_test SET TBLPROPERTIES('druid.kafka.ingestion' = 'START');
-ALTER TABLE druid\_kafka\_test SET TBLPROPERTIES('druid.kafka.ingestion' = 'STOP');
-ALTER TABLE druid\_kafka\_test SET TBLPROPERTIES('druid.kafka.ingestion' = 'RESET');
+<pre tabindex=0><code>ALTER TABLE druid_kafka_test SET TBLPROPERTIES('druid.kafka.ingestion' = 'START');
+ALTER TABLE druid_kafka_test SET TBLPROPERTIES('druid.kafka.ingestion' = 'STOP');
+ALTER TABLE druid_kafka_test SET TBLPROPERTIES('druid.kafka.ingestion' = 'RESET');
 </code></pre><p>Note: Reseting the ingestion will reset the kafka consumer offset maintained by druid to the next offset. The consumer offsets maintained by druid will be reset to either the earliest or latest offset depending on <em>druid.kafka.ingestion.useEarliestOffset</em></p>
 <p> table property. This can cause duplicate/missing events. We typically only need to reset kafka ingestion when messages in Kafka at the current consumer offsets are no longer available for consumption and therefore won&rsquo;t be ingested into Druid.</p>
 <h3 id=insert-insert-overwrite-and-drop-statements>INSERT, INSERT OVERWRITE and DROP statements</h3>
@@ -309,19 +309,19 @@ ALTER TABLE druid\_kafka\_test SET TBLPROPERTIES('druid.kafka.ingestion' = 'RESE
 <h4 id=select-queries>Select queries</h4>
 <p>We start with the simplest type of Druid query: <em><a href=http://druid.io/docs/0.9.1.1/querying/selectquery.html>select</a></em> queries. Basically, a <em>select</em> query will be equivalent to a scan operation on the data sources, although operations such as projection, filter, or limit can still be pushed into this type of query.</p>
 <p>Consider the following query, a simple select query for 10 rows consisting of all the columns of the table:</p>
-<pre tabindex=0><code>SELECT * FROM druid\_table\_1 LIMIT 10;
+<pre tabindex=0><code>SELECT * FROM druid_table_1 LIMIT 10;
 </code></pre><p>The Hive plan for the query will be the following:</p>
 <pre tabindex=0><code>hive&gt; EXPLAIN
-    &gt; SELECT * FROM druid\_table\_1 LIMIT 10;
+    &gt; SELECT * FROM druid_table_1 LIMIT 10;
 OK
 Plan optimized by CBO.
 Stage-0
   Fetch Operator
     limit:-1
-    Select Operator [SEL\_1]
-      Output:[&quot;\_col0&quot;,&quot;\_col1&quot;,&quot;\_col2&quot;,&quot;\_col3&quot;,&quot;\_col4&quot;,&quot;\_col5&quot;,&quot;\_col6&quot;,&quot;\_col7&quot;,&quot;\_col8&quot;,&quot;\_col9&quot;,&quot;\_col10&quot;,&quot;\_col11&quot;,&quot;\_col12&quot;,&quot;\_col13&quot;,&quot;\_col14&quot;,&quot;\_col15&quot;,&quot;\_col16&quot;,&quot;\_col17&quot;,&quot;\_col18&quot;,&quot;\_col19&quot;,&quot;\_col20&quot;,&quot;\_col21&quot;]
-      TableScan [TS\_0]
-        Output:[&quot;\_\_time&quot;,&quot;added&quot;,&quot;channel&quot;,&quot;cityname&quot;,&quot;comment&quot;,&quot;count&quot;,&quot;countryisocode&quot;,&quot;countryname&quot;,&quot;deleted&quot;,&quot;delta&quot;,&quot;isanonymous&quot;,&quot;isminor&quot;,&quot;isnew&quot;,&quot;isrobot&quot;,&quot;isunpatrolled&quot;,&quot;metrocode&quot;,&quot;namespace&quot;,&quot;page&quot;,&quot;regionisocode&quot;,&quot;regionname&quot;,&quot;user&quot;,&quot;user\_unique&quot;],properti [...]
+    Select Operator [SEL_1]
+      Output:[&quot;_col0&quot;,&quot;_col1&quot;,&quot;_col2&quot;,&quot;_col3&quot;,&quot;_col4&quot;,&quot;_col5&quot;,&quot;_col6&quot;,&quot;_col7&quot;,&quot;_col8&quot;,&quot;_col9&quot;,&quot;_col10&quot;,&quot;_col11&quot;,&quot;_col12&quot;,&quot;_col13&quot;,&quot;_col14&quot;,&quot;_col15&quot;,&quot;_col16&quot;,&quot;_col17&quot;,&quot;_col18&quot;,&quot;_col19&quot;,&quot;_col20&quot;,&quot;_col21&quot;]
+      TableScan [TS_0]
+        Output:[&quot;__time&quot;,&quot;added&quot;,&quot;channel&quot;,&quot;cityname&quot;,&quot;comment&quot;,&quot;count&quot;,&quot;countryisocode&quot;,&quot;countryname&quot;,&quot;deleted&quot;,&quot;delta&quot;,&quot;isanonymous&quot;,&quot;isminor&quot;,&quot;isnew&quot;,&quot;isrobot&quot;,&quot;isunpatrolled&quot;,&quot;metrocode&quot;,&quot;namespace&quot;,&quot;page&quot;,&quot;regionisocode&quot;,&quot;regionname&quot;,&quot;user&quot;,&quot;user_unique&quot;],properties: [...]
 Time taken: 0.141 seconds, Fetched: 10 row(s)
 </code></pre><p>Observe that the Druid query is in the properties attached to the TableScan. For readability, we format it properly:</p>
 <pre tabindex=0><code>{
@@ -333,7 +333,7 @@ Time taken: 0.141 seconds, Fetched: 10 row(s)
     [&quot;channel&quot;,&quot;cityname&quot;,&quot;comment&quot;,&quot;countryisocode&quot;,
      &quot;countryname&quot;,&quot;isanonymous&quot;,&quot;isminor&quot;,&quot;isnew&quot;,
      &quot;isrobot&quot;,&quot;isunpatrolled&quot;,&quot;metrocode&quot;,&quot;namespace&quot;,
-     &quot;page&quot;,&quot;regionisocode&quot;,&quot;regionname&quot;,&quot;user&quot;,&quot;user\_unique&quot;
+     &quot;page&quot;,&quot;regionisocode&quot;,&quot;regionname&quot;,&quot;user&quot;,&quot;user_unique&quot;
     ],
   &quot;metrics&quot;:[&quot;added&quot;,&quot;count&quot;,&quot;deleted&quot;,&quot;delta&quot;],
   &quot;pagingSpec&quot;:{&quot;threshold&quot;:10}
@@ -341,9 +341,9 @@ Time taken: 0.141 seconds, Fetched: 10 row(s)
 </code></pre><p>Observe that we get to push the limit into the Druid query (<code>threshold</code>). Observe as well that as we do not specify a filter on the timestamp dimension for the data source, we generate an interval that covers the range (−∞,+∞).</p>
 <p> </p>
 <p>In Druid, the timestamp column plays a central role. In fact, Druid allows to filter on the time dimension using the <code>intervals</code> property for all those queries. This is very important, as the time intervals determine the nodes that store the Druid data. Thus, specifying a precise range minimizes the number of nodes hit by the broken for a certain query. Inspired by Druid <a href=https://github.com/druid-io/druid/pull/2880>PR-2880</a>, we implemented the intervals extraction [...]
-<pre tabindex=0><code>SELECT `\_\_time`
-FROM druid\_table\_1
-WHERE `\_\_time` &gt;= '2010-01-01 00:00:00' AND `\_\_time` &lt;= '2011-01-01 00:00:00'
+<pre tabindex=0><code>SELECT `__time`
+FROM druid_table_1
+WHERE `__time` &gt;= '2010-01-01 00:00:00' AND `__time` &lt;= '2011-01-01 00:00:00'
 LIMIT 10;
 </code></pre><p>The Druid query generated for the SQL query above is the following (we omit the plan, as it is a simple TableScan operator).</p>
 <pre tabindex=0><code>{
@@ -356,33 +356,33 @@ LIMIT 10;
   &quot;pagingSpec&quot;:{&quot;threshold&quot;:10}
 }
 </code></pre><p>Observe that we infer correctly the interval for the specified dates, <code>2010-01-01T00:00:00.000Z/2011-01-01T00:00:00.001Z</code>, because in Druid the starting date of the interval is included, but the closing date is not. We also support recognition of multiple interval ranges, for instance in the following SQL query:</p>
-<pre tabindex=0><code>SELECT `\_\_time`
-FROM druid\_table\_1
-WHERE (`\_\_time` BETWEEN '2010-01-01 00:00:00' AND '2011-01-01 00:00:00')
-    OR (`\_\_time` BETWEEN '2012-01-01 00:00:00' AND '2013-01-01 00:00:00')
+<pre tabindex=0><code>SELECT `__time`
+FROM druid_table_1
+WHERE (`__time` BETWEEN '2010-01-01 00:00:00' AND '2011-01-01 00:00:00')
+    OR (`__time` BETWEEN '2012-01-01 00:00:00' AND '2013-01-01 00:00:00')
 LIMIT 10;
 </code></pre><p>Furthermore we can infer overlapping intervals too. Finally, the filters that are not specified on the time dimension will be translated into valid Druid filters and included within the query using the <code>filter</code> property.</p>
 <h4 id=timeseries-queries>Timeseries queries</h4>
 <p><em><a href=http://druid.io/docs/0.9.1.1/querying/timeseriesquery.html>Timeseries</a></em> is one of the types of queries that Druid can execute very efficiently. The following SQL query translates directly into a Druid <em>timeseries</em> query:</p>
 <pre tabindex=0><code>-- GRANULARITY: MONTH
-SELECT `floor\_month`(`\_\_time`), max(delta), sum(added)
-FROM druid\_table\_1
-GROUP BY `floor\_month`(`\_\_time`);
+SELECT `floor_month`(`__time`), max(delta), sum(added)
+FROM druid_table_1
+GROUP BY `floor_month`(`__time`);
 </code></pre><p>Basically, we group by a given time granularity and calculate the aggregation results for each resulting group. In particular, the <code>floor_month</code> function over the timestamp dimension __<code>time</code> represents the Druid month granularity format. Currently, we support <code>floor_year</code>, <code>floor_quarter</code>, <code>floor_month</code>, <code>floor_week</code>, <code>floor_day</code>, <code>floor_hour</code>, <code>floor_minute</code>, and <code>flo [...]
 <p>The Hive plan for the query will be the following:</p>
 <pre tabindex=0><code>hive&gt; EXPLAIN
-    &gt; SELECT `floor\_month`(`\_\_time`), max(delta), sum(added)
-    &gt; FROM druid\_table\_1
-    &gt; GROUP BY `floor\_month`(`\_\_time`);
+    &gt; SELECT `floor_month`(`__time`), max(delta), sum(added)
+    &gt; FROM druid_table_1
+    &gt; GROUP BY `floor_month`(`__time`);
 OK
 Plan optimized by CBO.
 Stage-0
   Fetch Operator
     limit:-1
-    Select Operator [SEL\_1]
-      Output:[&quot;\_col0&quot;,&quot;\_col1&quot;,&quot;\_col2&quot;]
-      TableScan [TS\_0]
-        Output:[&quot;\_\_time&quot;,&quot;$f1&quot;,&quot;$f2&quot;],
+    Select Operator [SEL_1]
+      Output:[&quot;_col0&quot;,&quot;_col1&quot;,&quot;_col2&quot;]
+      TableScan [TS_0]
+        Output:[&quot;__time&quot;,&quot;$f1&quot;,&quot;$f2&quot;],
         properties:{&quot;druid.query.json&quot;:&quot;{\&quot;queryType\&quot;:\&quot;timeseries\&quot;,\&quot;dataSource\&quot;:\&quot;wikiticker\&quot;,\&quot;descending\&quot;:\&quot;false\&quot;,\&quot;granularity\&quot;:\&quot;MONTH\&quot;,\&quot;aggregations\&quot;:[{\&quot;type\&quot;:\&quot;longMax\&quot;,\&quot;name\&quot;:\&quot;$f1\&quot;,\&quot;fieldName\&quot;:\&quot;delta\&quot;},{\&quot;type\&quot;:\&quot;longSum\&quot;,\&quot;name\&quot;:\&quot;$f2\&quot;,\&quot;fieldNam [...]
 Time taken: 0.116 seconds, Fetched: 10 row(s)
 </code></pre><p>Observe that the Druid query is in the properties attached to the TableScan. For readability, we format it properly:</p>
@@ -402,7 +402,7 @@ Time taken: 0.116 seconds, Fetched: 10 row(s)
 <p>One rather special case is <code>all</code> granularity, which we introduce by example below. Consider the following query:</p>
 <pre tabindex=0><code>-- GRANULARITY: ALL
 SELECT max(delta), sum(added)
-FROM druid\_table\_1;
+FROM druid_table_1;
 </code></pre><p>As it will do an aggregation on the complete dataset, it translates into a <em>timeseries</em> query with granularity <code>all</code>. In particular, the equivalent Druid query attached to the TableScan operator is the following:</p>
 <pre tabindex=0><code>{
   &quot;queryType&quot;:&quot;timeseries&quot;,
@@ -419,7 +419,7 @@ FROM druid\_table\_1;
 <p>The final type of queries we currently support is <em><a href=http://druid.io/docs/0.9.1.1/querying/groupbyquery.html>groupBy</a></em>. This kind of query is more expressive than <em>timeseries</em> queries; however, they are less performant. Thus, we only fall back to <em>groupBy</em> queries when we cannot transform into <em>timeseries</em> queries.</p>
 <p>For instance, the following SQL query will generate a Druid <em>groupBy</em> query:</p>
 <pre tabindex=0><code>SELECT max(delta), sum(added)
-FROM druid\_table\_1
+FROM druid_table_1
 GROUP BY `channel`, `user`;
 </code></pre><pre tabindex=0><code>{
   &quot;queryType&quot;:&quot;groupBy&quot;,
@@ -433,22 +433,22 @@ GROUP BY `channel`, `user`;
 }
 </code></pre><h3 id=queries-across-druid-and-hive>Queries across Druid and Hive</h3>
 <p>Finally, we provide an example of a query that runs across Druid and Hive. In particular, let us create a second table in Hive with some data:</p>
-<pre tabindex=0><code>CREATE TABLE hive\_table\_1 (col1 INT, col2 STRING);
-INSERT INTO hive\_table\_1 VALUES(1, '#en.wikipedia');
+<pre tabindex=0><code>CREATE TABLE hive_table_1 (col1 INT, col2 STRING);
+INSERT INTO hive_table_1 VALUES(1, '#en.wikipedia');
 </code></pre><p>Assume we want to execute the following query:</p>
 <pre tabindex=0><code>SELECT a.channel, b.col1
 FROM
 (
   SELECT `channel`, max(delta) as m, sum(added)
-  FROM druid\_table\_1
-  GROUP BY `channel`, `floor\_year`(`\_\_time`)
+  FROM druid_table_1
+  GROUP BY `channel`, `floor_year`(`__time`)
   ORDER BY m DESC
   LIMIT 1000
 ) a
 JOIN
 (
   SELECT col1, col2
-  FROM hive\_table\_1
+  FROM hive_table_1
 ) b
 ON a.channel = b.col2;
 </code></pre><p>The query is a simple join on columns <code>channel</code> and <code>col2</code>. The subquery <code>a</code> is executed completely in Druid as a <em>groupBy</em> query. Then the results are joined in Hive with the results of results of subquery <code>b</code>. The query plan and execution in Tez is shown in the following:</p>
@@ -457,68 +457,68 @@ ON a.channel = b.col2;
     &gt; FROM
     &gt; (
     &gt;   SELECT `channel`, max(delta) as m, sum(added)
-    &gt;   FROM druid\_table\_1
-    &gt;   GROUP BY `channel`, `floor\_year`(`\_\_time`)
+    &gt;   FROM druid_table_1
+    &gt;   GROUP BY `channel`, `floor_year`(`__time`)
     &gt;   ORDER BY m DESC
     &gt;   LIMIT 1000
     &gt; ) a
     &gt; JOIN
     &gt; (
     &gt;   SELECT col1, col2
-    &gt;   FROM hive\_table\_1
+    &gt;   FROM hive_table_1
     &gt; ) b
     &gt; ON a.channel = b.col2;
 OK
 Plan optimized by CBO.
 Vertex dependency in root stage
-Map 2 &lt;- Map 1 (BROADCAST\_EDGE)
+Map 2 &lt;- Map 1 (BROADCAST_EDGE)
 Stage-0
   Fetch Operator
     limit:-1
     Stage-1
       Map 2
-      File Output Operator [FS\_11]
-        Select Operator [SEL\_10] (rows=1 width=0)
-          Output:[&quot;\_col0&quot;,&quot;\_col1&quot;]
-          Map Join Operator [MAPJOIN\_16] (rows=1 width=0)
-            Conds:RS\_7.\_col0=SEL\_6.\_col1(Inner),HybridGraceHashJoin:true,Output:[&quot;\_col0&quot;,&quot;\_col2&quot;]
-          &lt;-Map 1 [BROADCAST\_EDGE]
-            BROADCAST [RS\_7]
-              PartitionCols:\_col0
-              Filter Operator [FIL\_2] (rows=1 width=0)
-                predicate:\_col0 is not null
-                Select Operator [SEL\_1] (rows=1 width=0)
-                  Output:[&quot;\_col0&quot;]
-                  TableScan [TS\_0] (rows=1 width=0)
-                    druid@druid\_table\_1,druid\_table\_1,Tbl:PARTIAL,Col:NONE,Output:[&quot;channel&quot;],properties:{&quot;druid.query.json&quot;:&quot;{\&quot;queryType\&quot;:\&quot;groupBy\&quot;,\&quot;dataSource\&quot;:\&quot;wikiticker\&quot;,\&quot;granularity\&quot;:\&quot;all\&quot;,\&quot;dimensions\&quot;:[{\&quot;type\&quot;:\&quot;default\&quot;,\&quot;dimension\&quot;:\&quot;channel\&quot;},{\&quot;type\&quot;:\&quot;extraction\&quot;,\&quot;dimension\&quot;:\&quot;\_\_t [...]
-          &lt;-Select Operator [SEL\_6] (rows=1 width=15)
-              Output:[&quot;\_col0&quot;,&quot;\_col1&quot;]
-              Filter Operator [FIL\_15] (rows=1 width=15)
+      File Output Operator [FS_11]
+        Select Operator [SEL_10] (rows=1 width=0)
+          Output:[&quot;_col0&quot;,&quot;_col1&quot;]
+          Map Join Operator [MAPJOIN_16] (rows=1 width=0)
+            Conds:RS_7._col0=SEL_6._col1(Inner),HybridGraceHashJoin:true,Output:[&quot;_col0&quot;,&quot;_col2&quot;]
+          &lt;-Map 1 [BROADCAST_EDGE]
+            BROADCAST [RS_7]
+              PartitionCols:_col0
+              Filter Operator [FIL_2] (rows=1 width=0)
+                predicate:_col0 is not null
+                Select Operator [SEL_1] (rows=1 width=0)
+                  Output:[&quot;_col0&quot;]
+                  TableScan [TS_0] (rows=1 width=0)
+                    druid@druid_table_1,druid_table_1,Tbl:PARTIAL,Col:NONE,Output:[&quot;channel&quot;],properties:{&quot;druid.query.json&quot;:&quot;{\&quot;queryType\&quot;:\&quot;groupBy\&quot;,\&quot;dataSource\&quot;:\&quot;wikiticker\&quot;,\&quot;granularity\&quot;:\&quot;all\&quot;,\&quot;dimensions\&quot;:[{\&quot;type\&quot;:\&quot;default\&quot;,\&quot;dimension\&quot;:\&quot;channel\&quot;},{\&quot;type\&quot;:\&quot;extraction\&quot;,\&quot;dimension\&quot;:\&quot;__time\&q [...]
+          &lt;-Select Operator [SEL_6] (rows=1 width=15)
+              Output:[&quot;_col0&quot;,&quot;_col1&quot;]
+              Filter Operator [FIL_15] (rows=1 width=15)
                 predicate:col2 is not null
-                TableScan [TS\_4] (rows=1 width=15)
-                  druid@hive\_table\_1,hive\_table\_1,Tbl:COMPLETE,Col:NONE,Output:[&quot;col1&quot;,&quot;col2&quot;]
+                TableScan [TS_4] (rows=1 width=15)
+                  druid@hive_table_1,hive_table_1,Tbl:COMPLETE,Col:NONE,Output:[&quot;col1&quot;,&quot;col2&quot;]
 Time taken: 0.924 seconds, Fetched: 31 row(s)
 hive&gt; SELECT a.channel, b.col1
     &gt; FROM
     &gt; (
     &gt;   SELECT `channel`, max(delta) as m, sum(added)
-    &gt;   FROM druid\_table\_1
-    &gt;   GROUP BY `channel`, `floor\_year`(`\_\_time`)
+    &gt;   FROM druid_table_1
+    &gt;   GROUP BY `channel`, `floor_year`(`__time`)
     &gt;   ORDER BY m DESC
     &gt;   LIMIT 1000
     &gt; ) a
     &gt; JOIN
     &gt; (
     &gt;   SELECT col1, col2
-    &gt;   FROM hive\_table\_1
+    &gt;   FROM hive_table_1
     &gt; ) b
     &gt; ON a.channel = b.col2;
-Query ID = user1\_20160818202329\_e9a8b3e8-18d3-49c7-bfe0-99d38d2402d3
+Query ID = user1_20160818202329_e9a8b3e8-18d3-49c7-bfe0-99d38d2402d3
 Total jobs = 1
 Launching Job 1 out of 1
-2016-08-18 20:23:30 Running Dag: dag\_1471548210492\_0001\_1
-2016-08-18 20:23:30 Starting to run new task attempt: attempt\_1471548210492\_0001\_1\_00\_000000\_0
-Status: Running (Executing on YARN cluster with App id application\_1471548210492\_0001)
+2016-08-18 20:23:30 Running Dag: dag_1471548210492_0001_1
+2016-08-18 20:23:30 Starting to run new task attempt: attempt_1471548210492_0001_1_00_000000_0
+Status: Running (Executing on YARN cluster with App id application_1471548210492_0001)
 ----------------------------------------------------------------------------------------------
         VERTICES      MODE        STATUS  TOTAL  COMPLETED  RUNNING  PENDING  FAILED  KILLED
 ----------------------------------------------------------------------------------------------
@@ -527,7 +527,7 @@ Map 2 .......... container     SUCCEEDED      1          1        0        0
 ----------------------------------------------------------------------------------------------
 VERTICES: 02/02  [==========================&gt;&gt;] 100%  ELAPSED TIME: 0.15 s
 ----------------------------------------------------------------------------------------------
-2016-08-18 20:23:31 Completed running task attempt: attempt\_1471548210492\_0001\_1\_00\_000000\_0
+2016-08-18 20:23:31 Completed running task attempt: attempt_1471548210492_0001_1_00_000000_0
 OK
 #en.wikipedia	1
 Time taken: 1.835 seconds, Fetched: 2 row(s)
diff --git a/docs/latest/dynamicpartitions_27823715/index.html b/docs/latest/dynamicpartitions_27823715/index.html
index 5a2ba91..804c09a 100644
--- a/docs/latest/dynamicpartitions_27823715/index.html
+++ b/docs/latest/dynamicpartitions_27823715/index.html
@@ -212,8 +212,8 @@ ASF
 </ol>
 <p>A dynamic partitioning column could be the result of an expression. For example:</p>
 <pre tabindex=0><code>
- -- part\_col is partitioning column
- create table T as select a, concat(&quot;part\_&quot;, part\_col) from S where part\_col is not null; 
+ -- part_col is partitioning column
+ create table T as select a, concat(&quot;part_&quot;, part_col) from S where part_col is not null; 
 
 </code></pre><p>Although currently there is not restriction on the data type of the partitioning column, allowing non-primitive columns to be partitioning column probably doesn&rsquo;t make sense. The dynamic partitioning column&rsquo;s type should be derived from the expression. The data type has to be able to be converted to a string in order to be saved as a directory name in HDFS.</p>
 <ol start=2>
@@ -234,8 +234,8 @@ ASF
 <li>If there are multiple partitioning columns, their order is significant since that translates to the directory structure in HDFS: partitioned by (ds string, dept int) implies a directory structure of ds=2009-02-26/dept=2. In a DML or DDL involving partitioned table, So if a subset of partitioning columns are specified (static), we should throw an error if a dynamic partitioning column is lower. Example:</li>
 </ol>
 <pre tabindex=0><code>
- create table nzhang\_part(a string) partitioned by (ds string, dept int);
- insert overwrite nzhang\_part (dept=1) select a, ds, dept from T where dept=1 and ds is not null;
+ create table nzhang_part(a string) partitioned by (ds string, dept int);
+ insert overwrite nzhang_part (dept=1) select a, ds, dept from T where dept=1 and ds is not null;
 
 </code></pre>
 </div>
diff --git a/docs/latest/exchange-partition_30755801/index.html b/docs/latest/exchange-partition_30755801/index.html
index 092d347..059cc0a 100644
--- a/docs/latest/exchange-partition_30755801/index.html
+++ b/docs/latest/exchange-partition_30755801/index.html
@@ -137,7 +137,7 @@ If the schemas are different, the following exception is thrown:</p>
 </ul>
 <p><code>The tables have different schemas. Their partitions cannot be exchanged</code></p>
 <h4 id=syntax>Syntax</h4>
-<pre tabindex=0><code>ALTER TABLE &lt;dest\_table&gt; EXCHANGE PARTITION (&lt;[partial] partition spec&gt;) WITH TABLE &lt;src\_table&gt;
+<pre tabindex=0><code>ALTER TABLE &lt;dest_table&gt; EXCHANGE PARTITION (&lt;[partial] partition spec&gt;) WITH TABLE &lt;src_table&gt;
 
 </code></pre><h4 id=example-usagebasic>Example Usage – Basic</h4>
 <pre tabindex=0><code>--Create two tables, partitioned by ds
diff --git a/docs/latest/genericudafcasestudy_27362093/index.html b/docs/latest/genericudafcasestudy_27362093/index.html
index 03aa242..bbe666a 100644
--- a/docs/latest/genericudafcasestudy_27362093/index.html
+++ b/docs/latest/genericudafcasestudy_27362093/index.html
@@ -385,13 +385,13 @@ build/dist/bin/hive
 </li>
 </ol>
 <pre tabindex=0><code>
-ant test -Dtestcase=TestCliDriver -Dqfile=udaf\_XXXXX.q -Doverwrite=true
+ant test -Dtestcase=TestCliDriver -Dqfile=udaf_XXXXX.q -Doverwrite=true
 
 </code></pre><ol start=6>
 <li>Run the following command to make sure your test runs fine.</li>
 </ol>
 <pre tabindex=0><code>
-ant test -Dtestcase=TestCliDriver -Dqfile=udaf\_XXXXX.q
+ant test -Dtestcase=TestCliDriver -Dqfile=udaf_XXXXX.q
 
 </code></pre><h1 id=checklist-for-open-source-submission>Checklist for open source submission</h1>
 <ul>
diff --git a/docs/latest/gettingstarted_27362090/index.html b/docs/latest/gettingstarted_27362090/index.html
index 4a7f97a..76841a0 100644
--- a/docs/latest/gettingstarted_27362090/index.html
+++ b/docs/latest/gettingstarted_27362090/index.html
@@ -203,10 +203,10 @@ Hive versions up to 0.13 also supported Hadoop 0.20.x, 0.23.x.</li>
 
 </code></pre><p>Set the environment variable <code>HIVE_HOME</code> to point to the installation directory:</p>
 <pre tabindex=0><code>  $ cd hive-x.y.z
-  $ export HIVE\_HOME={{pwd}}
+  $ export HIVE_HOME={{pwd}}
 
 </code></pre><p>Finally, add <code>$HIVE_HOME/bin</code> to your <code>PATH</code>:</p>
-<pre tabindex=0><code>  $ export PATH=$HIVE\_HOME/bin:$PATH
+<pre tabindex=0><code>  $ export PATH=$HIVE_HOME/bin:$PATH
 
 </code></pre><h3 id=building-hive-from-source>Building Hive from Source</h3>
 <p>The Hive GIT repository for the most recent Hive code is located here: <code>git clone &lt;https://git-wip-us.apache.org/repos/asf/hive.git></code> (the master branch).</p>
@@ -222,7 +222,7 @@ Hive versions up to 0.13 also supported Hadoop 0.20.x, 0.23.x.</li>
   LICENSE
   NOTICE
   README.txt
-  RELEASE\_NOTES.txt
+  RELEASE_NOTES.txt
   bin/ (all the shell scripts)
   lib/ (required jar files)
   conf/ (configuration files)
@@ -245,7 +245,7 @@ Hive versions up to 0.13 also supported Hadoop 0.20.x, 0.23.x.</li>
   LICENSE
   NOTICE
   README.txt
-  RELEASE\_NOTES.txt
+  RELEASE_NOTES.txt
   bin/ (all the shell scripts)
   lib/ (required jar files)
   conf/ (configuration files)
@@ -265,41 +265,41 @@ Hive versions up to 0.13 also supported Hadoop 0.20.x, 0.23.x.</li>
 <li><code>export HADOOP_HOME=&lt;hadoop-install-dir></code></li>
 </ul>
 <p>In addition, you must use below HDFS commands to create <code>/tmp</code> and <code>/user/hive/warehouse</code> (aka <code>hive.metastore.warehouse.dir</code>) and set them <code>chmod g+w</code> before you can create a table in Hive.</p>
-<pre tabindex=0><code>  $ $HADOOP\_HOME/bin/hadoop fs -mkdir       /tmp
-  $ $HADOOP\_HOME/bin/hadoop fs -mkdir       /user/hive/warehouse
-  $ $HADOOP\_HOME/bin/hadoop fs -chmod g+w   /tmp
-  $ $HADOOP\_HOME/bin/hadoop fs -chmod g+w   /user/hive/warehouse
+<pre tabindex=0><code>  $ $HADOOP_HOME/bin/hadoop fs -mkdir       /tmp
+  $ $HADOOP_HOME/bin/hadoop fs -mkdir       /user/hive/warehouse
+  $ $HADOOP_HOME/bin/hadoop fs -chmod g+w   /tmp
+  $ $HADOOP_HOME/bin/hadoop fs -chmod g+w   /user/hive/warehouse
 
 </code></pre><p>You may find it useful, though it&rsquo;s not necessary, to set <code>HIVE_HOME</code>:</p>
-<pre tabindex=0><code>  $ export HIVE\_HOME=&lt;hive-install-dir&gt;
+<pre tabindex=0><code>  $ export HIVE_HOME=&lt;hive-install-dir&gt;
 
 </code></pre><h4 id=running-hive-cli>Running Hive CLI</h4>
 <p>To use the Hive <a href=https://hive.apache.org/docs/latest/languagemanual-cli_27362033/>command line interface</a> (CLI) from the shell:</p>
-<pre tabindex=0><code>  $ $HIVE\_HOME/bin/hive
+<pre tabindex=0><code>  $ $HIVE_HOME/bin/hive
 
 </code></pre><h4 id=running-hiveserver2-and-beeline-1>Running HiveServer2 and Beeline</h4>
 <p>Starting from Hive 2.1, we need to run the schematool command below as an initialization step. For example, we can use &ldquo;derby&rdquo; as db type. </p>
-<pre tabindex=0><code>  $ $HIVE\_HOME/bin/schematool -dbType &lt;db type&gt; -initSchema
+<pre tabindex=0><code>  $ $HIVE_HOME/bin/schematool -dbType &lt;db type&gt; -initSchema
 
 </code></pre><p><a href=https://hive.apache.org/docs/latest/setting-up-hiveserver2_30758712/>HiveServer2</a> (introduced in Hive 0.11) has its own CLI called <a href=https://hive.apache.org/docs/latest/hiveserver2-clients_30758725/>Beeline</a>.  HiveCLI is now deprecated in favor of Beeline, as it lacks the multi-user, security, and other capabilities of HiveServer2.  To run HiveServer2 and Beeline from shell:</p>
-<pre tabindex=0><code>  $ $HIVE\_HOME/bin/hiveserver2
+<pre tabindex=0><code>  $ $HIVE_HOME/bin/hiveserver2
 
-  $ $HIVE\_HOME/bin/beeline -u jdbc:hive2://$HS2\_HOST:$HS2\_PORT
+  $ $HIVE_HOME/bin/beeline -u jdbc:hive2://$HS2_HOST:$HS2_PORT
 </code></pre><p>Beeline is started with the JDBC URL of the HiveServer2, which depends on the address and port where HiveServer2 was started.  By default, it will be (localhost:10000), so the address will look like jdbc:hive2://localhost:10000.</p>
 <p>Or to start Beeline and HiveServer2 in the same process for testing purpose, for a similar user experience to HiveCLI:</p>
-<pre tabindex=0><code>  $ $HIVE\_HOME/bin/beeline -u jdbc:hive2://
+<pre tabindex=0><code>  $ $HIVE_HOME/bin/beeline -u jdbc:hive2://
 
 </code></pre><h4 id=running-hcatalog>Running HCatalog</h4>
 <p>To run the HCatalog server from the shell in Hive release 0.11.0 and later:</p>
-<pre tabindex=0><code>  $ $HIVE\_HOME/hcatalog/sbin/hcat\_server.sh
+<pre tabindex=0><code>  $ $HIVE_HOME/hcatalog/sbin/hcat_server.sh
 
 </code></pre><p>To use the HCatalog command line interface (CLI) in Hive release 0.11.0 and later:</p>
-<pre tabindex=0><code>  $ $HIVE\_HOME/hcatalog/bin/hcat
+<pre tabindex=0><code>  $ $HIVE_HOME/hcatalog/bin/hcat
 
 </code></pre><p>For more information, see <a href=https://hive.apache.org/docs/latest/hcatalog-installhcat_34013403/>HCatalog Installation from Tarball</a> and <a href=https://hive.apache.org/docs/latest/hcatalog-cli_34013932/>HCatalog CLI</a> in the <a href=https://hive.apache.org/docs/latest/hcatalog_33299065/>HCatalog manual</a>.</p>
 <h4 id=running-webhcat-templeton>Running WebHCat (Templeton)</h4>
 <p>To run the WebHCat server from the shell in Hive release 0.11.0 and later:</p>
-<pre tabindex=0><code>  $ $HIVE\_HOME/hcatalog/sbin/webhcat\_server.sh
+<pre tabindex=0><code>  $ $HIVE_HOME/hcatalog/sbin/webhcat_server.sh
 
 </code></pre><p>For more information, see <a href=https://hive.apache.org/docs/latest/webhcat-installwebhcat_34015585/>WebHCat Installation</a> in the <a href=https://hive.apache.org/docs/latest/webhcat_33299069/>WebHCat manual</a>.</p>
 <h3 id=configuration-management-overview>Configuration Management Overview</h3>
@@ -361,7 +361,7 @@ Note: In <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?page
 </ul>
 <p>To configure a different log location, set <code>hive.log.dir</code> in $HIVE_HOME/conf/hive-log4j.properties. Make sure the directory has the sticky bit set (<code>chmod 1777 &lt;*dir*></code>).</p>
 <ul>
-<li><code>hive.log.dir=*&lt;other\_location>*</code></li>
+<li><code>hive.log.dir=*&lt;other_location>*</code></li>
 </ul>
 <p>If the user wishes, the logs can be emitted to the console by adding the arguments shown below:</p>
 <ul>
@@ -418,9 +418,9 @@ Note: In <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?page
 <h3 id=altering-and-dropping-tables>Altering and Dropping Tables</h3>
 <p>Table names can be <a href=#changed>changed</a> and columns can be <a href=#added-or-replaced>added or replaced</a>:</p>
 <pre tabindex=0><code>  hive&gt; ALTER TABLE events RENAME TO 3koobecaf;
-  hive&gt; ALTER TABLE pokes ADD COLUMNS (new\_col INT);
-  hive&gt; ALTER TABLE invites ADD COLUMNS (new\_col2 INT COMMENT 'a comment');
-  hive&gt; ALTER TABLE invites REPLACE COLUMNS (foo INT, bar STRING, baz INT COMMENT 'baz replaces new\_col2');
+  hive&gt; ALTER TABLE pokes ADD COLUMNS (new_col INT);
+  hive&gt; ALTER TABLE invites ADD COLUMNS (new_col2 INT COMMENT 'a comment');
+  hive&gt; ALTER TABLE invites REPLACE COLUMNS (foo INT, bar STRING, baz INT COMMENT 'baz replaces new_col2');
 
 </code></pre><p>Note that REPLACE COLUMNS replaces all existing columns and only changes the table&rsquo;s schema, not the data. The table must use a native SerDe. REPLACE COLUMNS can also be used to drop columns from the table&rsquo;s schema:</p>
 <pre tabindex=0><code>  hive&gt; ALTER TABLE invites REPLACE COLUMNS (foo INT COMMENT 'only keep the first column');
@@ -465,20 +465,20 @@ More are available in the Hive sources at <code>ql/src/test/queries/positive</co
 
 </code></pre><p>selects column &lsquo;foo&rsquo; from all rows of partition <code>ds=2008-08-15</code> of the <code>invites</code> table. The results are not stored anywhere, but are displayed on the console.</p>
 <p>Note that in all the examples that follow, <code>INSERT</code> (into a Hive table, local directory or HDFS directory) is optional.</p>
-<pre tabindex=0><code>  hive&gt; INSERT OVERWRITE DIRECTORY '/tmp/hdfs\_out' SELECT a.* FROM invites a WHERE a.ds='2008-08-15';
+<pre tabindex=0><code>  hive&gt; INSERT OVERWRITE DIRECTORY '/tmp/hdfs_out' SELECT a.* FROM invites a WHERE a.ds='2008-08-15';
 
 </code></pre><p>selects all rows from partition <code>ds=2008-08-15</code> of the <code>invites</code> table into an HDFS directory. The result data is in files (depending on the number of mappers) in that directory.<br>
 NOTE: partition columns if any are selected by the use of *. They can also be specified in the projection clauses.</p>
 <p>Partitioned tables must always have a partition selected in the <code>WHERE</code> clause of the statement.</p>
-<pre tabindex=0><code>  hive&gt; INSERT OVERWRITE LOCAL DIRECTORY '/tmp/local\_out' SELECT a.* FROM pokes a;
+<pre tabindex=0><code>  hive&gt; INSERT OVERWRITE LOCAL DIRECTORY '/tmp/local_out' SELECT a.* FROM pokes a;
 
 </code></pre><p>selects all rows from pokes table into a local directory.</p>
 <pre tabindex=0><code>  hive&gt; INSERT OVERWRITE TABLE events SELECT a.* FROM profiles a;
   hive&gt; INSERT OVERWRITE TABLE events SELECT a.* FROM profiles a WHERE a.key &lt; 100;
-  hive&gt; INSERT OVERWRITE LOCAL DIRECTORY '/tmp/reg\_3' SELECT a.* FROM events a;
-  hive&gt; INSERT OVERWRITE DIRECTORY '/tmp/reg\_4' select a.invites, a.pokes FROM profiles a;
-  hive&gt; INSERT OVERWRITE DIRECTORY '/tmp/reg\_5' SELECT COUNT(*) FROM invites a WHERE a.ds='2008-08-15';
-  hive&gt; INSERT OVERWRITE DIRECTORY '/tmp/reg\_5' SELECT a.foo, a.bar FROM invites a;
+  hive&gt; INSERT OVERWRITE LOCAL DIRECTORY '/tmp/reg_3' SELECT a.* FROM events a;
+  hive&gt; INSERT OVERWRITE DIRECTORY '/tmp/reg_4' select a.invites, a.pokes FROM profiles a;
+  hive&gt; INSERT OVERWRITE DIRECTORY '/tmp/reg_5' SELECT COUNT(*) FROM invites a WHERE a.ds='2008-08-15';
+  hive&gt; INSERT OVERWRITE DIRECTORY '/tmp/reg_5' SELECT a.foo, a.bar FROM invites a;
   hive&gt; INSERT OVERWRITE LOCAL DIRECTORY '/tmp/sum' SELECT SUM(a.pc) FROM pc1 a;
 
 </code></pre><p>selects the sum of a column. The avg, min, or max can also be used. Note that for versions of Hive which don&rsquo;t include <a href=https://issues.apache.org/jira/browse/HIVE-287>HIVE-287</a>, you&rsquo;ll need to use <code>COUNT(1)</code> in place of <code>COUNT(*)</code>.</p>
@@ -505,7 +505,7 @@ Similarly – streaming can be used on the reduce side (please see the <a href=h
 <h2 id=simple-example-use-cases>Simple Example Use Cases</h2>
 <h3 id=movielens-user-ratings>MovieLens User Ratings</h3>
 <p>First, create a table with tab-delimited text file format:</p>
-<pre tabindex=0><code>CREATE TABLE u\_data (
+<pre tabindex=0><code>CREATE TABLE u_data (
   userid INT,
   movieid INT,
   rating INT,
@@ -523,10 +523,10 @@ STORED AS TEXTFILE;
 <pre tabindex=0><code>unzip ml-100k.zip
 </code></pre><p>And load <code>u.data</code> into the table that was just created:</p>
 <pre tabindex=0><code>LOAD DATA LOCAL INPATH '&lt;path&gt;/u.data'
-OVERWRITE INTO TABLE u\_data;
+OVERWRITE INTO TABLE u_data;
 
 </code></pre><p>Count the number of rows in table u_data:</p>
-<pre tabindex=0><code>SELECT COUNT(*) FROM u\_data;
+<pre tabindex=0><code>SELECT COUNT(*) FROM u_data;
 
 </code></pre><p>Note that for older versions of Hive which don&rsquo;t include <a href=https://issues.apache.org/jira/browse/HIVE-287>HIVE-287</a>, you&rsquo;ll need to use COUNT(1) in place of COUNT(*).</p>
 <p>Now we can do some complex data analysis on the table <code>u_data</code>:</p>
@@ -541,7 +541,7 @@ for line in sys.stdin:
   print '\t'.join([userid, movieid, rating, str(weekday)])
 
 </code></pre><p>Use the mapper script:</p>
-<pre tabindex=0><code>CREATE TABLE u\_data\_new (
+<pre tabindex=0><code>CREATE TABLE u_data_new (
   userid INT,
   movieid INT,
   rating INT,
@@ -549,17 +549,17 @@ for line in sys.stdin:
 ROW FORMAT DELIMITED
 FIELDS TERMINATED BY '\t';
 
-add FILE weekday\_mapper.py;
+add FILE weekday_mapper.py;
 
-INSERT OVERWRITE TABLE u\_data\_new
+INSERT OVERWRITE TABLE u_data_new
 SELECT
   TRANSFORM (userid, movieid, rating, unixtime)
-  USING 'python weekday\_mapper.py'
+  USING 'python weekday_mapper.py'
   AS (userid, movieid, rating, weekday)
-FROM u\_data;
+FROM u_data;
 
 SELECT weekday, COUNT(*)
-FROM u\_data\_new
+FROM u_data_new
 GROUP BY weekday;
 
 </code></pre><p>Note that if you&rsquo;re using Hive 0.5.0 or earlier you will need to use <code>COUNT(1)</code> in place of <code>COUNT(*)</code>.</p>
diff --git a/docs/latest/hbasebulkload_27362088/index.html b/docs/latest/hbasebulkload_27362088/index.html
index 5aa4f26..15c2a4b 100644
--- a/docs/latest/hbasebulkload_27362088/index.html
+++ b/docs/latest/hbasebulkload_27362088/index.html
@@ -135,14 +135,14 @@ ASF
 <p>This page explains how to use Hive to bulk load data into a new (empty) HBase table per <a href=https://issues.apache.org/jira/browse/HIVE-1295>HIVE-1295</a>. (If you&rsquo;re not using a build which contains this functionality yet, you&rsquo;ll need to build from source and make sure this patch and HIVE-1321 are both applied.)</p>
 <h2 id=overview>Overview</h2>
 <p>Ideally, bulk load from Hive into HBase would be part of <a href=https://hive.apache.org/docs/latest/hbaseintegration_27362089/>HBaseIntegration</a>, making it as simple as this:</p>
-<pre tabindex=0><code>CREATE TABLE new\_hbase\_table(rowkey string, x int, y int) 
+<pre tabindex=0><code>CREATE TABLE new_hbase_table(rowkey string, x int, y int) 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (&quot;hbase.columns.mapping&quot; = &quot;:key,cf:x,cf:y&quot;);
 
 SET hive.hbase.bulk=true;
 
-INSERT OVERWRITE TABLE new\_hbase\_table
-SELECT rowkey\_expression, x, y FROM ...any\_hive\_query...;
+INSERT OVERWRITE TABLE new_hbase_table
+SELECT rowkey_expression, x, y FROM ...any_hive_query...;
 
 </code></pre><p>However, things aren&rsquo;t <em>quite</em> as straightforward as that yet. Instead, a procedure involving a series of SQL commands is required. It should still be a lot easier and more flexible than writing your own map/reduce program, and over time we hope to enhance Hive to move closer to the ideal.</p>
 <p>The procedure is based on <a href=http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/mapreduce/package-summary.html#bulk>underlying HBase recommendations</a>, and involves the following steps:</p>
@@ -182,21 +182,21 @@ hadoop dfs -put /usr/lib/hive/lib/hive-hbase-handler-VERSION.jar /user/hive/hive
 <p>In order to perform a parallel sort on the data, we need to range-partition it. The idea is to divide the space of row keys up into nearly equal-sized ranges, one per reducer which will be used in the parallel sort. The details will vary according to your source data, and you may need to run a number of exploratory Hive queries in order to come up with a good enough set of ranges. Here&rsquo;s one example:</p>
 <pre tabindex=0><code>add jar lib/hive-contrib-0.7.0.jar;
 set mapred.reduce.tasks=1;
-create temporary function row\_sequence as 
+create temporary function row_sequence as 
 'org.apache.hadoop.hive.contrib.udf.UDFRowSequence';
-select transaction\_id from
-(select transaction\_id
+select transaction_id from
+(select transaction_id
 from transactions
-tablesample(bucket 1 out of 10000 on transaction\_id) s 
-order by transaction\_id 
+tablesample(bucket 1 out of 10000 on transaction_id) s 
+order by transaction_id 
 limit 10000000) x
-where (row\_sequence() % 910000)=0
-order by transaction\_id
+where (row_sequence() % 910000)=0
+order by transaction_id
 limit 11;
 
 </code></pre><p>This works by ordering all of the rows in a .01% sample of the table (using a single reducer), and then selecting every nth row (here n=910000). The value of n is chosen by dividing the total number of rows in the sample by the desired number of ranges, e.g. 12 in this case (one more than the number of partitioning keys produced by the LIMIT clause). The assumption here is that the distribution in the sample matches the overall distribution in the table; if this is not th [...]
 <p>Once you have your sampling query defined, the next step is to save its results to a properly formatted file which will be used in a subsequent step. To do this, run commands like the following:</p>
-<pre tabindex=0><code>create external table hb\_range\_keys(transaction\_id\_range\_start string)
+<pre tabindex=0><code>create external table hb_range_keys(transaction_id_range_start string)
 row format serde 
 'org.apache.hadoop.hive.serde2.binarysortable.BinarySortableSerDe'
 stored as 
@@ -204,22 +204,22 @@ inputformat
 'org.apache.hadoop.mapred.TextInputFormat'
 outputformat 
 'org.apache.hadoop.hive.ql.io.HiveNullValueSequenceFileOutputFormat'
-location '/tmp/hb\_range\_keys';
+location '/tmp/hb_range_keys';
 
-insert overwrite table hb\_range\_keys
-select transaction\_id from
-(select transaction\_id
+insert overwrite table hb_range_keys
+select transaction_id from
+(select transaction_id
 from transactions
-tablesample(bucket 1 out of 10000 on transaction\_id) s 
-order by transaction\_id 
+tablesample(bucket 1 out of 10000 on transaction_id) s 
+order by transaction_id 
 limit 10000000) x
-where (row\_sequence() % 910000)=0
-order by transaction\_id
+where (row_sequence() % 910000)=0
+order by transaction_id
 limit 11;
 
 </code></pre><p>The first command creates an external table defining the format of the file to be created; be sure to set the serde and inputformat/outputformat exactly as specified.</p>
 <p>The second command populates it (using the sampling query previously defined). Usage of ORDER BY guarantees that a single file will be produced in directory <code>/tmp/hb_range_keys</code>. The filename is unknown, but it is necessary to reference the file by name later, so run a command such as the following to copy it to a specific name:</p>
-<pre tabindex=0><code>dfs -cp /tmp/hb\_range\_keys/* /tmp/hb\_range\_key\_list;
+<pre tabindex=0><code>dfs -cp /tmp/hb_range_keys/* /tmp/hb_range_key_list;
 
 </code></pre><h2 id=prepare-staging-location>Prepare Staging Location</h2>
 <p>The sort is going to produce a lot of data, so make sure you have sufficient space in your HDFS cluster, and choose the location where the files will be staged. We&rsquo;ll use <code>/tmp/hbsort</code> in this example.</p>
@@ -232,19 +232,19 @@ dfs -mkdir /tmp/hbsort;
 <pre tabindex=0><code>set hive.execution.engine=mr;
 set mapred.reduce.tasks=12;
 set hive.mapred.partitioner=org.apache.hadoop.mapred.lib.TotalOrderPartitioner;
-set total.order.partitioner.path=/tmp/hb\_range\_key\_list;
+set total.order.partitioner.path=/tmp/hb_range_key_list;
 set hfile.compression=gz;
 
-create table hbsort(transaction\_id string, user\_name string, amount double, ...)
+create table hbsort(transaction_id string, user_name string, amount double, ...)
 stored as
 INPUTFORMAT 'org.apache.hadoop.mapred.TextInputFormat'
 OUTPUTFORMAT 'org.apache.hadoop.hive.hbase.HiveHFileOutputFormat'
 TBLPROPERTIES ('hfile.family.path' = '/tmp/hbsort/cf');
 
 insert overwrite table hbsort
-select transaction\_id, user\_name, amount, ...
+select transaction_id, user_name, amount, ...
 from transactions
-cluster by transaction\_id;
+cluster by transaction_id;
 
 </code></pre><p>The CREATE TABLE creates a dummy table which controls how the output of the sort is written. Note that it uses <code>HiveHFileOutputFormat</code> to do this, with the table property <code>hfile.family.path</code> used to control the destination directory for the output. Again, be sure to set the inputformat/outputformat exactly as specified. In the example above, we select gzip (gz) compression for the result files; if you don&rsquo;t set the <code>hfile.compression</code [...]
 <p>Note that the number of reduce tasks is one more than the number of partitions - this <strong>must</strong> be true or else you will get a &ldquo;Wrong number of partitions in keyset&rdquo; error.</p>
@@ -267,9 +267,9 @@ cluster by transaction\_id;
 <p>After this script finishes, you may need to wait a minute or two for the new table to be picked up by the HBase meta scanner. Use the hbase shell to verify that the new table was created correctly, and do some sanity queries to locate individual cells and make sure they can be found.</p>
 <h2 id=map-new-table-back-into-hive>Map New Table Back Into Hive</h2>
 <p>Finally, if you&rsquo;d like to access the HBase table you just created via Hive:</p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE hbase\_transactions(transaction\_id string, user\_name string, amount double, ...) 
+<pre tabindex=0><code>CREATE EXTERNAL TABLE hbase_transactions(transaction_id string, user_name string, amount double, ...) 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
-WITH SERDEPROPERTIES (&quot;hbase.columns.mapping&quot; = &quot;:key,cf:user\_name,cf:amount,...&quot;)
+WITH SERDEPROPERTIES (&quot;hbase.columns.mapping&quot; = &quot;:key,cf:user_name,cf:amount,...&quot;)
 TBLPROPERTIES(&quot;hbase.table.name&quot; = &quot;transactions&quot;);
 
 </code></pre><h2 id=followups-needed>Followups Needed</h2>
diff --git a/docs/latest/hbaseintegration_27362089/index.html b/docs/latest/hbaseintegration_27362089/index.html
index 66d5eed..ee8c295 100644
--- a/docs/latest/hbaseintegration_27362089/index.html
+++ b/docs/latest/hbaseintegration_27362089/index.html
@@ -166,14 +166,14 @@ ASF
 <h2 id=usage>Usage</h2>
 <p>The storage handler is built as an independent module, <code>hive-hbase-handler-x.y.z.jar</code>, which must be available on the Hive client auxpath, along with HBase, Guava and ZooKeeper jars. It also requires the correct configuration property to be set in order to connect to the right HBase master. See <a href=http://hadoop.apache.org/hbase/docs/current/api/overview-summary.html#overview_description>the HBase documentation</a> for how to set up an HBase cluster.</p>
 <p>Here&rsquo;s an example using CLI from a source build environment, targeting a single-node HBase server. (Note that the jar locations and names have changed in Hive 0.9.0, so for earlier releases, some changes are needed.)</p>
-<pre tabindex=0><code>$HIVE\_SRC/build/dist/bin/hive --auxpath $HIVE\_SRC/build/dist/lib/hive-hbase-handler-0.9.0.jar,$HIVE\_SRC/build/dist/lib/hbase-0.92.0.jar,$HIVE\_SRC/build/dist/lib/zookeeper-3.3.4.jar,$HIVE\_SRC/build/dist/lib/guava-r09.jar --hiveconf hbase.master=hbase.yoyodyne.com:60000
+<pre tabindex=0><code>$HIVE_SRC/build/dist/bin/hive --auxpath $HIVE_SRC/build/dist/lib/hive-hbase-handler-0.9.0.jar,$HIVE_SRC/build/dist/lib/hbase-0.92.0.jar,$HIVE_SRC/build/dist/lib/zookeeper-3.3.4.jar,$HIVE_SRC/build/dist/lib/guava-r09.jar --hiveconf hbase.master=hbase.yoyodyne.com:60000
 
 </code></pre><p>Here&rsquo;s an example which instead targets a distributed HBase cluster where a quorum of 3 zookeepers is used to elect the HBase master:</p>
-<pre tabindex=0><code>$HIVE\_SRC/build/dist/bin/hive --auxpath $HIVE\_SRC/build/dist/lib/hive-hbase-handler-0.9.0.jar,$HIVE\_SRC/build/dist/lib/hbase-0.92.0.jar,$HIVE\_SRC/build/dist/lib/zookeeper-3.3.4.jar,$HIVE\_SRC/build/dist/lib/guava-r09.jar --hiveconf hbase.zookeeper.quorum=zk1.yoyodyne.com,zk2.yoyodyne.com,zk3.yoyodyne.com
+<pre tabindex=0><code>$HIVE_SRC/build/dist/bin/hive --auxpath $HIVE_SRC/build/dist/lib/hive-hbase-handler-0.9.0.jar,$HIVE_SRC/build/dist/lib/hbase-0.92.0.jar,$HIVE_SRC/build/dist/lib/zookeeper-3.3.4.jar,$HIVE_SRC/build/dist/lib/guava-r09.jar --hiveconf hbase.zookeeper.quorum=zk1.yoyodyne.com,zk2.yoyodyne.com,zk3.yoyodyne.com
 
 </code></pre><p>The handler requires Hadoop 0.20 or higher, and has only been tested with dependency versions hadoop-0.20.x, hbase-0.92.0 and zookeeper-3.3.4. If you are not using hbase-0.92.0, you will need to rebuild the handler with the HBase jar matching your version, and change the <code>--auxpath</code> above accordingly. Failure to use matching versions will lead to misleading connection failures such as MasterNotRunningException since the HBase RPC protocol changes often.</p>
 <p>In order to create a new HBase table which is to be managed by Hive, use the <code>STORED BY</code> clause on <code>CREATE TABLE</code>:</p>
-<pre tabindex=0><code>CREATE TABLE hbase\_table\_1(key int, value string) 
+<pre tabindex=0><code>CREATE TABLE hbase_table_1(key int, value string) 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (&quot;hbase.columns.mapping&quot; = &quot;:key,cf1:val&quot;)
 TBLPROPERTIES (&quot;hbase.table.name&quot; = &quot;xyz&quot;, &quot;hbase.mapred.output.outputtable&quot; = &quot;xyz&quot;);
@@ -189,7 +189,7 @@ xyz
 hbase(main):002:0&gt; describe &quot;xyz&quot;
 DESCRIPTION                                                             ENABLED                               
  {NAME =&gt; 'xyz', FAMILIES =&gt; [{NAME =&gt; 'cf1', COMPRESSION =&gt; 'NONE', VE true                                  
- RSIONS =&gt; '3', TTL =&gt; '2147483647', BLOCKSIZE =&gt; '65536', IN\_MEMORY =&gt;                                       
+ RSIONS =&gt; '3', TTL =&gt; '2147483647', BLOCKSIZE =&gt; '65536', IN_MEMORY =&gt;                                       
   'false', BLOCKCACHE =&gt; 'true'}]}                                                                            
 1 row(s) in 0.0220 seconds
 hbase(main):003:0&gt; scan &quot;xyz&quot;
@@ -198,21 +198,21 @@ ROW                          COLUMN+CELL
 
 </code></pre><p>Notice that even though a column name &ldquo;val&rdquo; is specified in the mapping, only the column family name &ldquo;cf1&rdquo; appears in the DESCRIBE output in the HBase shell. This is because in HBase, only column families (not columns) are known in the table-level metadata; column names within a column family are only present at the per-row level.</p>
 <p>Here&rsquo;s how to move data from Hive into the HBase table (see <a href=https://hive.apache.org/docs/latest/gettingstarted_27362090/>GettingStarted</a> for how to create the example table <code>pokes</code> in Hive first):</p>
-<pre tabindex=0><code>INSERT OVERWRITE TABLE hbase\_table\_1 SELECT * FROM pokes WHERE foo=98;
+<pre tabindex=0><code>INSERT OVERWRITE TABLE hbase_table_1 SELECT * FROM pokes WHERE foo=98;
 
 </code></pre><p>Use HBase shell to verify that the data actually got loaded:</p>
 <pre tabindex=0><code>hbase(main):009:0&gt; scan &quot;xyz&quot;
 ROW                          COLUMN+CELL                                                                      
- 98                          column=cf1:val, timestamp=1267737987733, value=val\_98                            
+ 98                          column=cf1:val, timestamp=1267737987733, value=val_98                            
 1 row(s) in 0.0110 seconds
 
 </code></pre><p>And then query it back via Hive:</p>
-<pre tabindex=0><code>hive&gt; select * from hbase\_table\_1;
+<pre tabindex=0><code>hive&gt; select * from hbase_table_1;
 Total MapReduce jobs = 1
 Launching Job 1 out of 1
 ...
 OK
-98	val\_98
+98	val_98
 Time taken: 4.582 seconds
 
 </code></pre><p>Inserting large amounts of data may be slow due to WAL overhead; if you would like to disable this, make sure you have HIVE-1383 (as of Hive 0.6), and then issue this command before the INSERT:</p>
@@ -220,10 +220,10 @@ Time taken: 4.582 seconds
 
 </code></pre><p><strong>Warning:</strong> disabling WAL may lead to data loss if an HBase failure occurs, so only use this if you have some other recovery strategy available.</p>
 <p>If you want to give Hive access to an existing HBase table, use CREATE EXTERNAL TABLE:</p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE hbase\_table\_2(key int, value string) 
+<pre tabindex=0><code>CREATE EXTERNAL TABLE hbase_table_2(key int, value string) 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (&quot;hbase.columns.mapping&quot; = &quot;cf1:val&quot;)
-TBLPROPERTIES(&quot;hbase.table.name&quot; = &quot;some\_existing\_table&quot;, &quot;hbase.mapred.output.outputtable&quot; = &quot;some\_existing\_table&quot;);
+TBLPROPERTIES(&quot;hbase.table.name&quot; = &quot;some_existing_table&quot;, &quot;hbase.mapred.output.outputtable&quot; = &quot;some_existing_table&quot;);
 
 </code></pre><p>Again, <code>hbase.columns.mapping</code> is required (and will be validated against the existing HBase table&rsquo;s column families), whereas <code>hbase.table.name</code> is optional. The <code>hbase.mapred.output.outputtable</code> is optional.</p>
 <h2 id=column-mapping>Column Mapping</h2>
@@ -251,73 +251,73 @@ TBLPROPERTIES(&quot;hbase.table.name&quot; = &quot;some\_existing\_table&quot;,
 <p>The next few sections provide detailed examples of the kinds of column mappings currently possible.</p>
 <h3 id=multiple-columns-and-families>Multiple Columns and Families</h3>
 <p>Here&rsquo;s an example with three Hive columns and two HBase column families, with two of the Hive columns (<code>value1</code> and <code>value2</code>) corresponding to one of the column families (<code>a</code>, with HBase column names <code>b</code> and <code>c</code>), and the other Hive column corresponding to a single column (<code>e</code>) in its own column family (<code>d</code>).</p>
-<pre tabindex=0><code>CREATE TABLE hbase\_table\_1(key int, value1 string, value2 int, value3 int) 
+<pre tabindex=0><code>CREATE TABLE hbase_table_1(key int, value1 string, value2 int, value3 int) 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (
 &quot;hbase.columns.mapping&quot; = &quot;:key,a:b,a:c,d:e&quot;
 );
-INSERT OVERWRITE TABLE hbase\_table\_1 SELECT foo, bar, foo+1, foo+2 
+INSERT OVERWRITE TABLE hbase_table_1 SELECT foo, bar, foo+1, foo+2 
 FROM pokes WHERE foo=98 OR foo=100;
 
 </code></pre><p>Here&rsquo;s how this looks in HBase:</p>
-<pre tabindex=0><code>hbase(main):014:0&gt; describe &quot;hbase\_table\_1&quot;
+<pre tabindex=0><code>hbase(main):014:0&gt; describe &quot;hbase_table_1&quot;
 DESCRIPTION                                                             ENABLED                               
- {NAME =&gt; 'hbase\_table\_1', FAMILIES =&gt; [{NAME =&gt; 'a', COMPRESSION =&gt; 'N true                                  
- ONE', VERSIONS =&gt; '3', TTL =&gt; '2147483647', BLOCKSIZE =&gt; '65536', IN\_M                                       
+ {NAME =&gt; 'hbase_table_1', FAMILIES =&gt; [{NAME =&gt; 'a', COMPRESSION =&gt; 'N true                                  
+ ONE', VERSIONS =&gt; '3', TTL =&gt; '2147483647', BLOCKSIZE =&gt; '65536', IN_M                                       
  EMORY =&gt; 'false', BLOCKCACHE =&gt; 'true'}, {NAME =&gt; 'd', COMPRESSION =&gt;                                        
  'NONE', VERSIONS =&gt; '3', TTL =&gt; '2147483647', BLOCKSIZE =&gt; '65536', IN                                       
- \_MEMORY =&gt; 'false', BLOCKCACHE =&gt; 'true'}]}                                                                  
+ _MEMORY =&gt; 'false', BLOCKCACHE =&gt; 'true'}]}                                                                  
 1 row(s) in 0.0170 seconds
-hbase(main):015:0&gt; scan &quot;hbase\_table\_1&quot;
+hbase(main):015:0&gt; scan &quot;hbase_table_1&quot;
 ROW                          COLUMN+CELL                                                                      
- 100                         column=a:b, timestamp=1267740457648, value=val\_100                               
+ 100                         column=a:b, timestamp=1267740457648, value=val_100                               
  100                         column=a:c, timestamp=1267740457648, value=101                                   
  100                         column=d:e, timestamp=1267740457648, value=102                                   
- 98                          column=a:b, timestamp=1267740457648, value=val\_98                                
+ 98                          column=a:b, timestamp=1267740457648, value=val_98                                
  98                          column=a:c, timestamp=1267740457648, value=99                                    
  98                          column=d:e, timestamp=1267740457648, value=100                                   
 2 row(s) in 0.0240 seconds
 
 </code></pre><p>And when queried back into Hive:</p>
-<pre tabindex=0><code>hive&gt; select * from hbase\_table\_1;
+<pre tabindex=0><code>hive&gt; select * from hbase_table_1;
 Total MapReduce jobs = 1
 Launching Job 1 out of 1
 ...
 OK
-100	val\_100	101	102
-98	val\_98	99	100
+100	val_100	101	102
+98	val_98	99	100
 Time taken: 4.054 seconds
 
 </code></pre><h3 id=hive-map-to-hbase-column-family>Hive MAP to HBase Column Family</h3>
 <p>Here&rsquo;s how a Hive MAP datatype can be used to access an entire column family. Each row can have a different set of columns, where the column names correspond to the map keys and the column values correspond to the map values.</p>
-<pre tabindex=0><code>CREATE TABLE hbase\_table\_1(value map&lt;string,int&gt;, row\_key int) 
+<pre tabindex=0><code>CREATE TABLE hbase_table_1(value map&lt;string,int&gt;, row_key int) 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (
 &quot;hbase.columns.mapping&quot; = &quot;cf:,:key&quot;
 );
-INSERT OVERWRITE TABLE hbase\_table\_1 SELECT map(bar, foo), foo FROM pokes 
+INSERT OVERWRITE TABLE hbase_table_1 SELECT map(bar, foo), foo FROM pokes 
 WHERE foo=98 OR foo=100;
 
 </code></pre><p>(This example also demonstrates using a Hive column other than the first as the HBase row key.)</p>
 <p>Here&rsquo;s how this looks in HBase (with different column names in different rows):</p>
-<pre tabindex=0><code>hbase(main):012:0&gt; scan &quot;hbase\_table\_1&quot;
+<pre tabindex=0><code>hbase(main):012:0&gt; scan &quot;hbase_table_1&quot;
 ROW                          COLUMN+CELL                                                                      
- 100                         column=cf:val\_100, timestamp=1267739509194, value=100                            
- 98                          column=cf:val\_98, timestamp=1267739509194, value=98                              
+ 100                         column=cf:val_100, timestamp=1267739509194, value=100                            
+ 98                          column=cf:val_98, timestamp=1267739509194, value=98                              
 2 row(s) in 0.0080 seconds
 
 </code></pre><p>And when queried back into Hive:</p>
-<pre tabindex=0><code>hive&gt; select * from hbase\_table\_1;
+<pre tabindex=0><code>hive&gt; select * from hbase_table_1;
 Total MapReduce jobs = 1
 Launching Job 1 out of 1
 ...
 OK
-{&quot;val\_100&quot;:100}	100
-{&quot;val\_98&quot;:98}	98
+{&quot;val_100&quot;:100}	100
+{&quot;val_98&quot;:98}	98
 Time taken: 3.808 seconds
 
 </code></pre><p>Note that the key of the MAP must have datatype string, since it is used for naming the HBase column, so the following table definition will fail:</p>
-<pre tabindex=0><code>CREATE TABLE hbase\_table\_1(key int, value map&lt;int,int&gt;) 
+<pre tabindex=0><code>CREATE TABLE hbase_table_1(key int, value map&lt;int,int&gt;) 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (
 &quot;hbase.columns.mapping&quot; = &quot;:key,cf:&quot;
@@ -326,29 +326,29 @@ FAILED: Error in metadata: java.lang.RuntimeException: MetaException(message:org
 
 </code></pre><h3 id=hive-map-to-hbase-column-prefix>Hive MAP to HBase Column Prefix</h3>
 <p>Also note that starting with <a href=https://issues.apache.org/jira/browse/HIVE-3725>Hive 0.12</a>, wildcards can also be used to retrieve columns. For instance, if you want to retrieve all columns in HBase that start with the prefix &ldquo;col_prefix&rdquo;, a query like the following should work:</p>
-<pre tabindex=0><code>CREATE TABLE hbase\_table\_1(value map&lt;string,int&gt;, row\_key int) 
+<pre tabindex=0><code>CREATE TABLE hbase_table_1(value map&lt;string,int&gt;, row_key int) 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (
-&quot;hbase.columns.mapping&quot; = &quot;cf:col\_prefix.*,:key&quot;
+&quot;hbase.columns.mapping&quot; = &quot;cf:col_prefix.*,:key&quot;
 );
 
 </code></pre><p>The same restrictions apply though. That is, the key of the map should be a string as it maps to the HBase column name and the value can be the type of value that you are retrieving. One other restriction is that all the values under the given prefix should be of the same type. That is, all of them should be of type &ldquo;int&rdquo; or type &ldquo;string&rdquo; and so on.</p>
 <h4 id=hiding-column-prefixes>Hiding Column Prefixes</h4>
 <p>Starting with <a href=https://issues.apache.org/jira/browse/HIVE-11329>Hive 1.3.0</a>, it is possible to hide column prefixes in select query results.  There is the SerDe boolean property hbase.columns.mapping.prefix.hide (false by default), which defines if the prefix should be hidden in keys of Hive map:</p>
-<pre tabindex=0><code>CREATE TABLE hbase\_table\_1(tags map&lt;string,int&gt;, row\_key string) 
+<pre tabindex=0><code>CREATE TABLE hbase_table_1(tags map&lt;string,int&gt;, row_key string) 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (
-&quot;hbase.columns.mapping&quot; = &quot;cf:tag\_.*,:key&quot;,
+&quot;hbase.columns.mapping&quot; = &quot;cf:tag_.*,:key&quot;,
 &quot;hbase.columns.mapping.prefix.hide&quot; = &quot;true&quot;
 );
 </code></pre><p>Then a value of the column &ldquo;tags&rdquo; (<code>select tags from hbase_table_1</code>) will be:</p>
 <pre tabindex=0><code>&quot;x&quot; : 1
 </code></pre><p>instead of:</p>
-<pre tabindex=0><code>&quot;tag\_x&quot; : 1
+<pre tabindex=0><code>&quot;tag_x&quot; : 1
 </code></pre><h3 id=illegal-hive-primitive-to-hbase-column-family>Illegal: Hive Primitive to HBase Column Family</h3>
 <p>Table definitions such as the following are illegal because a<br>
 Hive column mapped to an entire column family must have MAP type:</p>
-<pre tabindex=0><code>CREATE TABLE hbase\_table\_1(key int, value string) 
+<pre tabindex=0><code>CREATE TABLE hbase_table_1(key int, value string) 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (
 &quot;hbase.columns.mapping&quot; = &quot;:key,cf:&quot;
@@ -357,14 +357,14 @@ FAILED: Error in metadata: java.lang.RuntimeException: MetaException(message:org
 
 </code></pre><h3 id=example-with-binary-columns>Example with Binary Columns</h3>
 <p>Relying on the default value of <code>hbase.table.default.storage.type</code>:</p>
-<pre tabindex=0><code>CREATE TABLE hbase\_table\_1 (key int, value string, foobar double)
+<pre tabindex=0><code>CREATE TABLE hbase_table_1 (key int, value string, foobar double)
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (
 &quot;hbase.columns.mapping&quot; = &quot;:key#b,cf:val,cf:foo#b&quot;
 );
 
 </code></pre><p>Specifying <code>hbase.table.default.storage.type</code>:</p>
-<pre tabindex=0><code>CREATE TABLE hbase\_table\_1 (key int, value string, foobar double)
+<pre tabindex=0><code>CREATE TABLE hbase_table_1 (key int, value string, foobar double)
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (
 &quot;hbase.columns.mapping&quot; = &quot;:key,cf:val#s,cf:foo&quot;,
@@ -376,7 +376,7 @@ WITH SERDEPROPERTIES (
 <p>As of <a href=https://issues.apache.org/jira/browse/HIVE-2599>Hive 0.13.0</a></p>
 <p>Hive can read and write delimited composite keys to HBase by mapping the HBase row key to a Hive struct, and using ROW FORMAT DELIMITED&mldr;COLLECTION ITEMS TERMINATED BY. Example:</p>
 <pre tabindex=0><code>-- Create a table with a composite row key consisting of two string fields, delimited by '~'
-CREATE EXTERNAL TABLE delimited\_example(key struct&lt;f1:string, f2:string&gt;, value string) 
+CREATE EXTERNAL TABLE delimited_example(key struct&lt;f1:string, f2:string&gt;, value string) 
 ROW FORMAT DELIMITED 
 COLLECTION ITEMS TERMINATED BY '~' 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' 
@@ -386,12 +386,12 @@ WITH SERDEPROPERTIES (
 <p>As of Hive 0.14.0 with <a href=https://issues.apache.org/jira/browse/HIVE-6411>HIVE-6411</a> (0.13.0 also supports complex composite keys, but using a different interface–see <a href=https://issues.apache.org/jira/browse/HIVE-2599>HIVE-2599</a> for that interface)</p>
 <p>For more complex use cases, Hive allows users to specify an HBaseKeyFactory which defines the mapping of a key to fields in a Hive struct. This can be configured using the property &ldquo;hbase.composite.key.factory&rdquo; in the SERDEPROPERTIES option:</p>
 <pre tabindex=0><code>-- Parse a row key with 3 fixed width fields each of width 10
--- Example taken from: https://svn.apache.org/repos/asf/hive/trunk/hbase-handler/src/test/queries/positive/hbase\_custom\_key2.q
-CREATE TABLE hbase\_ck\_4(key struct&lt;col1:string,col2:string,col3:string&gt;, value string)
+-- Example taken from: https://svn.apache.org/repos/asf/hive/trunk/hbase-handler/src/test/queries/positive/hbase_custom_key2.q
+CREATE TABLE hbase_ck_4(key struct&lt;col1:string,col2:string,col3:string&gt;, value string)
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (
-    &quot;hbase.table.name&quot; = &quot;hbase\_custom2&quot;,
-    &quot;hbase.mapred.output.outputtable&quot; = &quot;hbase\_custom2&quot;,
+    &quot;hbase.table.name&quot; = &quot;hbase_custom2&quot;,
+    &quot;hbase.mapred.output.outputtable&quot; = &quot;hbase_custom2&quot;,
     &quot;hbase.columns.mapping&quot; = &quot;:key,cf:string&quot;,
     &quot;hbase.composite.key.factory&quot;=&quot;org.apache.hadoop.hive.hbase.SampleHBaseKeyFactory2&quot;);
 </code></pre><p>&ldquo;hbase.composite.key.factory&rdquo; should be the fully qualified class name of a class implementing <a href=http://hive.apache.org/javadocs/r1.2.0/api/org/apache/hadoop/hive/hbase/HBaseKeyFactory.html>HBaseKeyFactory</a>. See <a href=https://svn.apache.org/repos/asf/hive/trunk/hbase-handler/src/test/org/apache/hadoop/hive/hbase/SampleHBaseKeyFactory2.java>SampleHBaseKeyFactory2</a> for a fixed length example in the same package. This class must be on your classpath [...]
@@ -399,21 +399,21 @@ WITH SERDEPROPERTIES (
 <p>As of Hive 0.14.0 with <a href=https://issues.apache.org/jira/browse/HIVE-6147>HIVE-6147</a></p>
 <p>Hive 0.14.0 onward supports storing and querying Avro objects in HBase columns by making them visible as structs to Hive. This allows Hive to perform ad hoc analysis of HBase data which can be deeply structured. Prior to 0.14.0, the HBase Hive integration only supported querying primitive data types in columns.</p>
 <p>An example HiveQL statement where <code>test_col_fam</code> is the column family and <code>test_col</code> is the column name:</p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE test\_hbase\_avro
+<pre tabindex=0><code>CREATE EXTERNAL TABLE test_hbase_avro
 ROW FORMAT SERDE 'org.apache.hadoop.hive.hbase.HBaseSerDe' 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler' 
 WITH SERDEPROPERTIES (
-	&quot;hbase.columns.mapping&quot; = &quot;:key,test\_col\_fam:test\_col&quot;, 
-	&quot;test\_col\_fam.test\_col.serialization.type&quot; = &quot;avro&quot;,
-	&quot;test\_col\_fam.test\_col.avro.schema.url&quot; = &quot;hdfs://testcluster/tmp/schema.avsc&quot;)
+	&quot;hbase.columns.mapping&quot; = &quot;:key,test_col_fam:test_col&quot;, 
+	&quot;test_col_fam.test_col.serialization.type&quot; = &quot;avro&quot;,
+	&quot;test_col_fam.test_col.avro.schema.url&quot; = &quot;hdfs://testcluster/tmp/schema.avsc&quot;)
 TBLPROPERTIES (
-    &quot;hbase.table.name&quot; = &quot;hbase\_avro\_table&quot;,
-    &quot;hbase.mapred.output.outputtable&quot; = &quot;hbase\_avro\_table&quot;,
+    &quot;hbase.table.name&quot; = &quot;hbase_avro_table&quot;,
+    &quot;hbase.mapred.output.outputtable&quot; = &quot;hbase_avro_table&quot;,
     &quot;hbase.struct.autogenerate&quot;=&quot;true&quot;);
 </code></pre><p>The important properties to note are the following three:</p>
-<pre tabindex=0><code>&quot;test\_col\_fam.test\_col.serialization.type&quot; = &quot;avro&quot;
+<pre tabindex=0><code>&quot;test_col_fam.test_col.serialization.type&quot; = &quot;avro&quot;
 </code></pre><p>This property tells Hive that the given column under the given column family is an Avro column, so Hive needs to deserialize it accordingly.</p>
-<pre tabindex=0><code>&quot;test\_col\_fam.test\_col.avro.schema.url&quot; = &quot;hdfs://testcluster/tmp/schema.avsc&quot;
+<pre tabindex=0><code>&quot;test_col_fam.test_col.avro.schema.url&quot; = &quot;hdfs://testcluster/tmp/schema.avsc&quot;
 </code></pre><p>Using this property you specify where the reader schema is for the column that will be used to deserialize. This can be on HDFS like mentioned here, or provided inline using something like <code>"test_col_fam.test_col.avro.schema.literal"</code> property. If you have a custom store where you store this schema, you can write a custom implementation of <a href=https://github.com/apache/hive/blob/master/serde/src/java/org/apache/hadoop/hive/serde2/avro/AvroSchemaRetriever.ja [...]
 <pre tabindex=0><code>&quot;hbase.struct.autogenerate&quot; = &quot;true&quot;
 </code></pre><p>Specifying this property lets Hive auto-deduce the columns and types using the schema that was provided. This allows you to avoid manually creating the columns and types for Avro schemas, which can be complicated and deeply nested.</p>
@@ -462,7 +462,7 @@ SELECT COUNT(1) FROM pokes3 WHERE foo=498;
 <p>Class-level unit tests are provided under <code>hbase-handler/src/test/org/apache/hadoop/hive/hbase</code>.</p>
 <p>Positive QL tests are under <code>hbase-handler/src/test/queries</code>. These use a HBase+Zookeeper mini-cluster for hosting the fixture tables in-process, so no free-standing HBase installation is needed in order to run them. To avoid failures due to port conflicts, don&rsquo;t try to run these tests on the same machine where a real HBase master or zookeeper is running.</p>
 <p>The QL tests can be executed via ant like this:</p>
-<pre tabindex=0><code>ant test -Dtestcase=TestHBaseCliDriver -Dqfile=hbase\_queries.q
+<pre tabindex=0><code>ant test -Dtestcase=TestHBaseCliDriver -Dqfile=hbase_queries.q
 
 </code></pre><p>An Eclipse launch template remains to be defined.</p>
 <h2 id=links>Links</h2>
diff --git a/docs/latest/hcatalog-dynamicpartitions_34014006/index.html b/docs/latest/hcatalog-dynamicpartitions_34014006/index.html
index b2f83a5..39e74b8 100644
--- a/docs/latest/hcatalog-dynamicpartitions_34014006/index.html
+++ b/docs/latest/hcatalog-dynamicpartitions_34014006/index.html
@@ -135,10 +135,10 @@ ASF
 <p>The following Pig script illustrates this:</p>
 <pre tabindex=0><code>A = load 'raw' using HCatLoader(); 
 ... 
-split Z into for\_us if region='us', for\_eu if region='eu', for\_asia if region='asia'; 
-store for\_us into 'processed' using HCatStorer(&quot;ds=20110110, region=us&quot;); 
-store for\_eu into 'processed' using HCatStorer(&quot;ds=20110110, region=eu&quot;); 
-store for\_asia into 'processed' using HCatStorer(&quot;ds=20110110, region=asia&quot;); 
+split Z into for_us if region='us', for_eu if region='eu', for_asia if region='asia'; 
+store for_us into 'processed' using HCatStorer(&quot;ds=20110110, region=us&quot;); 
+store for_eu into 'processed' using HCatStorer(&quot;ds=20110110, region=eu&quot;); 
+store for_asia into 'processed' using HCatStorer(&quot;ds=20110110, region=asia&quot;); 
 
 </code></pre><p>In cases where you want to write data to multiple partitions simultaneously, this can be done by placing partition columns in the data and not specifying partition values when storing the data.</p>
 <pre tabindex=0><code>A = load 'raw' using HCatLoader(); 
diff --git a/docs/latest/hcatalog-inputoutput_34013776/index.html b/docs/latest/hcatalog-inputoutput_34013776/index.html
index d356198..f13b255 100644
--- a/docs/latest/hcatalog-inputoutput_34013776/index.html
+++ b/docs/latest/hcatalog-inputoutput_34013776/index.html
@@ -314,40 +314,40 @@ ASF
 <p>For general information about Hive data types, see <a href=https://hive.apache.org/docs/latest/languagemanual-types_27838462/>Hive Data Types</a> and <a href=#type-system>Type System</a>.</p>
 <h2 id=running-mapreduce-with-hcatalog>Running MapReduce with HCatalog</h2>
 <p>Your MapReduce program needs to be told where the Thrift server is. The easiest way to do this is to pass the location as an argument to your Java program. You need to pass the Hive and HCatalog jars to MapReduce as well, via the -libjars argument.</p>
-<pre tabindex=0><code>export HADOOP\_HOME=&lt;path\_to\_hadoop\_install&gt;
-export HCAT\_HOME=&lt;path\_to\_hcat\_install&gt;
-export HIVE\_HOME=&lt;path\_to\_hive\_install&gt;
-export LIB\_JARS=$HCAT\_HOME/share/hcatalog/hcatalog-core-0.5.0.jar,
-$HIVE\_HOME/lib/hive-metastore-0.10.0.jar,
-$HIVE\_HOME/lib/libthrift-0.7.0.jar,
-$HIVE\_HOME/lib/hive-exec-0.10.0.jar,
-$HIVE\_HOME/lib/libfb303-0.7.0.jar,
-$HIVE\_HOME/lib/jdo2-api-2.3-ec.jar,
-$HIVE\_HOME/lib/slf4j-api-1.6.1.jar
+<pre tabindex=0><code>export HADOOP_HOME=&lt;path_to_hadoop_install&gt;
+export HCAT_HOME=&lt;path_to_hcat_install&gt;
+export HIVE_HOME=&lt;path_to_hive_install&gt;
+export LIB_JARS=$HCAT_HOME/share/hcatalog/hcatalog-core-0.5.0.jar,
+$HIVE_HOME/lib/hive-metastore-0.10.0.jar,
+$HIVE_HOME/lib/libthrift-0.7.0.jar,
+$HIVE_HOME/lib/hive-exec-0.10.0.jar,
+$HIVE_HOME/lib/libfb303-0.7.0.jar,
+$HIVE_HOME/lib/jdo2-api-2.3-ec.jar,
+$HIVE_HOME/lib/slf4j-api-1.6.1.jar
 
-export HADOOP\_CLASSPATH=$HCAT\_HOME/share/hcatalog/hcatalog-core-0.5.0.jar:
-$HIVE\_HOME/lib/hive-metastore-0.10.0.jar:
-$HIVE\_HOME/lib/libthrift-0.7.0.jar:
-$HIVE\_HOME/lib/hive-exec-0.10.0.jar:
-$HIVE\_HOME/lib/libfb303-0.7.0.jar:
-$HIVE\_HOME/lib/jdo2-api-2.3-ec.jar:
-$HIVE\_HOME/conf:$HADOOP\_HOME/conf:
-$HIVE\_HOME/lib/slf4j-api-1.6.1.jar
+export HADOOP_CLASSPATH=$HCAT_HOME/share/hcatalog/hcatalog-core-0.5.0.jar:
+$HIVE_HOME/lib/hive-metastore-0.10.0.jar:
+$HIVE_HOME/lib/libthrift-0.7.0.jar:
+$HIVE_HOME/lib/hive-exec-0.10.0.jar:
+$HIVE_HOME/lib/libfb303-0.7.0.jar:
+$HIVE_HOME/lib/jdo2-api-2.3-ec.jar:
+$HIVE_HOME/conf:$HADOOP_HOME/conf:
+$HIVE_HOME/lib/slf4j-api-1.6.1.jar
 
-$HADOOP\_HOME/bin/hadoop --config $HADOOP\_HOME/conf jar &lt;path\_to\_jar&gt;
-&lt;main\_class&gt; -libjars $LIB\_JARS &lt;program\_arguments&gt;
+$HADOOP_HOME/bin/hadoop --config $HADOOP_HOME/conf jar &lt;path_to_jar&gt;
+&lt;main_class&gt; -libjars $LIB_JARS &lt;program_arguments&gt;
 
 </code></pre><p>This works but Hadoop will ship libjars every time you run the MapReduce program, treating the files as different cache entries, which is not efficient and may deplete the Hadoop distributed cache.</p>
 <p>Instead, you can optimize to ship libjars using HDFS locations. By doing this, Hadoop will reuse the entries in the distributed cache.</p>
-<pre tabindex=0><code>bin/hadoop fs -copyFromLocal $HCAT\_HOME/share/hcatalog/hcatalog-core-0.5.0.jar /tmp
-bin/hadoop fs -copyFromLocal $HIVE\_HOME/lib/hive-metastore-0.10.0.jar /tmp
-bin/hadoop fs -copyFromLocal $HIVE\_HOME/lib/libthrift-0.7.0.jar /tmp
-bin/hadoop fs -copyFromLocal $HIVE\_HOME/lib/hive-exec-0.10.0.jar /tmp
-bin/hadoop fs -copyFromLocal $HIVE\_HOME/lib/libfb303-0.7.0.jar /tmp
-bin/hadoop fs -copyFromLocal $HIVE\_HOME/lib/jdo2-api-2.3-ec.jar /tmp
-bin/hadoop fs -copyFromLocal $HIVE\_HOME/lib/slf4j-api-1.6.1.jar /tmp
+<pre tabindex=0><code>bin/hadoop fs -copyFromLocal $HCAT_HOME/share/hcatalog/hcatalog-core-0.5.0.jar /tmp
+bin/hadoop fs -copyFromLocal $HIVE_HOME/lib/hive-metastore-0.10.0.jar /tmp
+bin/hadoop fs -copyFromLocal $HIVE_HOME/lib/libthrift-0.7.0.jar /tmp
+bin/hadoop fs -copyFromLocal $HIVE_HOME/lib/hive-exec-0.10.0.jar /tmp
+bin/hadoop fs -copyFromLocal $HIVE_HOME/lib/libfb303-0.7.0.jar /tmp
+bin/hadoop fs -copyFromLocal $HIVE_HOME/lib/jdo2-api-2.3-ec.jar /tmp
+bin/hadoop fs -copyFromLocal $HIVE_HOME/lib/slf4j-api-1.6.1.jar /tmp
 
-export LIB\_JARS=hdfs:///tmp/hcatalog-core-0.5.0.jar,
+export LIB_JARS=hdfs:///tmp/hcatalog-core-0.5.0.jar,
 hdfs:///tmp/hive-metastore-0.10.0.jar,
 hdfs:///tmp/libthrift-0.7.0.jar,
 hdfs:///tmp/hive-exec-0.10.0.jar,
diff --git a/docs/latest/hcatalog-loadstore_34013511/index.html b/docs/latest/hcatalog-loadstore_34013511/index.html
index 110346c..dcd8047 100644
--- a/docs/latest/hcatalog-loadstore_34013511/index.html
+++ b/docs/latest/hcatalog-loadstore_34013511/index.html
@@ -256,28 +256,28 @@ ASF
 <p>For Pig commands that omit <code>-useHCatalog</code>, you need to tell Pig where to find your HCatalog jars and the Hive jars used by the HCatalog client. To do this, you must define the environment variable PIG_CLASSPATH with the appropriate jars.</p>
 <p>HCatalog can tell you the jars it needs. In order to do this it needs to know where Hadoop and Hive are installed. Also, you need to tell Pig the URI for your metastore, in the PIG_OPTS variable.</p>
 <p>In the case where you have installed Hadoop and Hive via tar, you can do this:</p>
-<pre tabindex=0><code>export HADOOP\_HOME=&lt;path\_to\_hadoop\_install&gt;
+<pre tabindex=0><code>export HADOOP_HOME=&lt;path_to_hadoop_install&gt;
 
-export HIVE\_HOME=&lt;path\_to\_hive\_install&gt;
+export HIVE_HOME=&lt;path_to_hive_install&gt;
 
-export HCAT\_HOME=&lt;path\_to\_hcat\_install&gt;
+export HCAT_HOME=&lt;path_to_hcat_install&gt;
 
-export PIG\_CLASSPATH=$HCAT\_HOME/share/hcatalog/hcatalog-core*.jar:\
-$HCAT\_HOME/share/hcatalog/hcatalog-pig-adapter*.jar:\
-$HIVE\_HOME/lib/hive-metastore-*.jar:$HIVE\_HOME/lib/libthrift-*.jar:\
-$HIVE\_HOME/lib/hive-exec-*.jar:$HIVE\_HOME/lib/libfb303-*.jar:\
-$HIVE\_HOME/lib/jdo2-api-*-ec.jar:$HIVE\_HOME/conf:$HADOOP\_HOME/conf:\
-$HIVE\_HOME/lib/slf4j-api-*.jar
+export PIG_CLASSPATH=$HCAT_HOME/share/hcatalog/hcatalog-core*.jar:\
+$HCAT_HOME/share/hcatalog/hcatalog-pig-adapter*.jar:\
+$HIVE_HOME/lib/hive-metastore-*.jar:$HIVE_HOME/lib/libthrift-*.jar:\
+$HIVE_HOME/lib/hive-exec-*.jar:$HIVE_HOME/lib/libfb303-*.jar:\
+$HIVE_HOME/lib/jdo2-api-*-ec.jar:$HIVE_HOME/conf:$HADOOP_HOME/conf:\
+$HIVE_HOME/lib/slf4j-api-*.jar
 
-export PIG\_OPTS=-Dhive.metastore.uris=thrift://&lt;hostname&gt;:&lt;port&gt;
+export PIG_OPTS=-Dhive.metastore.uris=thrift://&lt;hostname&gt;:&lt;port&gt;
 
 </code></pre><p>Or you can pass the jars in your command line:</p>
-<pre tabindex=0><code>&lt;path\_to\_pig\_install&gt;/bin/pig -Dpig.additional.jars=\
-$HCAT\_HOME/share/hcatalog/hcatalog-core*.jar:\
-$HCAT\_HOME/share/hcatalog/hcatalog-pig-adapter*.jar:\
-$HIVE\_HOME/lib/hive-metastore-*.jar:$HIVE\_HOME/lib/libthrift-*.jar:\
-$HIVE\_HOME/lib/hive-exec-*.jar:$HIVE\_HOME/lib/libfb303-*.jar:\
-$HIVE\_HOME/lib/jdo2-api-*-ec.jar:$HIVE\_HOME/lib/slf4j-api-*.jar  &lt;script.pig&gt;
+<pre tabindex=0><code>&lt;path_to_pig_install&gt;/bin/pig -Dpig.additional.jars=\
+$HCAT_HOME/share/hcatalog/hcatalog-core*.jar:\
+$HCAT_HOME/share/hcatalog/hcatalog-pig-adapter*.jar:\
+$HIVE_HOME/lib/hive-metastore-*.jar:$HIVE_HOME/lib/libthrift-*.jar:\
+$HIVE_HOME/lib/hive-exec-*.jar:$HIVE_HOME/lib/libfb303-*.jar:\
+$HIVE_HOME/lib/jdo2-api-*-ec.jar:$HIVE_HOME/lib/slf4j-api-*.jar  &lt;script.pig&gt;
 
 </code></pre><p>The version number found in each filepath will be substituted for *. For example, HCatalog release 0.5.0 uses these jars and conf files:</p>
 <ul>
@@ -314,34 +314,34 @@ C = filter A by date == '20100819' and country == 'US';
 ...
 
 </code></pre><p>To scan a whole table, for example:</p>
-<pre tabindex=0><code>a = load 'student\_data' using org.apache.hive.hcatalog.pig.HCatLoader();
+<pre tabindex=0><code>a = load 'student_data' using org.apache.hive.hcatalog.pig.HCatLoader();
 b = foreach a generate name, age;
 
 </code></pre><p>Notice that the schema is automatically provided to Pig; there&rsquo;s no need to declare name and age as fields, as if you were loading from a file.</p>
 <p>To scan a single partition of the table web_logs partitioned by the column datestamp, for example:</p>
-<pre tabindex=0><code>a = load 'web\_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
+<pre tabindex=0><code>a = load 'web_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
 b = filter a by datestamp == '20110924';
 
 </code></pre><p>Pig will push the datestamp filter shown here to HCatalog, so that HCatalog knows to just scan the partition where datestamp = &lsquo;20110924&rsquo;. You can combine this filter with others via &lsquo;and&rsquo;:</p>
-<pre tabindex=0><code>a = load 'web\_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
+<pre tabindex=0><code>a = load 'web_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
 b = filter a by datestamp == '20110924' and user is not null;
 
 </code></pre><p>Pig will split the above filter, pushing the datestamp portion to HCatalog and retaining the &lsquo;<code>user is not null</code>&rsquo; part to apply itself. You can also give a more complex filter to retrieve a set of partitions.</p>
 <h4 id=filter-operators>Filter Operators</h4>
 <p>A filter can contain the operators &lsquo;and&rsquo;, &lsquo;or&rsquo;, &lsquo;()&rsquo;, &lsquo;==&rsquo;, &lsquo;!=&rsquo;, &lsquo;&lt;&rsquo;, &lsquo;>&rsquo;, &lsquo;&lt;=&rsquo; and &lsquo;>=&rsquo;.</p>
 <p>For example:</p>
-<pre tabindex=0><code>a = load 'web\_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
+<pre tabindex=0><code>a = load 'web_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
 b = filter a by datestamp &gt; '20110924';
 
 </code></pre><p>A complex filter can have various combinations of operators, such as:</p>
-<pre tabindex=0><code>a = load 'web\_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
+<pre tabindex=0><code>a = load 'web_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
 b = filter a by datestamp == '20110924' or datestamp == '20110925';
 
 </code></pre><p>These two examples have the same effect:</p>
-<pre tabindex=0><code>a = load 'web\_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
+<pre tabindex=0><code>a = load 'web_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
 b = filter a by datestamp &gt;= '20110924' and datestamp &lt;= '20110925';
 
-</code></pre><pre tabindex=0><code>a = load 'web\_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
+</code></pre><pre tabindex=0><code>a = load 'web_logs' using org.apache.hive.hcatalog.pig.HCatLoader();
 b = filter a by datestamp &lt;= '20110925' and datestamp &gt;= '20110924';
 
 </code></pre><h2 id=hcatstorer>HCatStorer</h2>
@@ -352,9 +352,9 @@ b = filter a by datestamp &lt;= '20110925' and datestamp &gt;= '20110924';
 B = FOREACH A ...
 ...
 ...
-my\_processed\_data = ...
+my_processed_data = ...
 
-STORE my\_processed\_data INTO 'tablename'
+STORE my_processed_data INTO 'tablename'
    USING org.apache.hive.hcatalog.pig.HCatStorer();
 
 </code></pre><h4 id=assumptions-1>Assumptions</h4>
@@ -364,13 +364,13 @@ STORE my\_processed\_data INTO 'tablename'
 <p>If partition columns are present in data they need not be specified as a STORE argument. Instead HCatalog will use these values to place records in the appropriate partition(s). It is valid to specify some partition keys in the STORE statement and have other partition keys in the data.</p>
 <h3 id=store-examples>Store Examples</h3>
 <p>You can write to a non-partitioned table simply by using HCatStorer. The contents of the table will be overwritten:</p>
-<pre tabindex=0><code>store z into 'web\_data' using org.apache.hive.hcatalog.pig.HCatStorer();
+<pre tabindex=0><code>store z into 'web_data' using org.apache.hive.hcatalog.pig.HCatStorer();
 
 </code></pre><p>To add one new partition to a partitioned table, specify the partition value in the store function. Pay careful attention to the quoting, as the whole string must be single quoted and separated with an equals sign:</p>
-<pre tabindex=0><code>store z into 'web\_data' using org.apache.hive.hcatalog.pig.HCatStorer('datestamp=20110924');
+<pre tabindex=0><code>store z into 'web_data' using org.apache.hive.hcatalog.pig.HCatStorer('datestamp=20110924');
 
 </code></pre><p>To write into multiple partitions at once, make sure that the partition column is present in your data, then call HCatStorer with no argument:</p>
-<pre tabindex=0><code>store z into 'web\_data' using org.apache.hive.hcatalog.pig.HCatStorer();
+<pre tabindex=0><code>store z into 'web_data' using org.apache.hive.hcatalog.pig.HCatStorer();
   -- datestamp must be a field in the relation z
 
 </code></pre><h3 id=hcatstorer-data-types>HCatStorer Data Types</h3>
@@ -517,7 +517,7 @@ STORE my\_processed\_data INTO 'tablename'
 <td>0.13.0+</td>
 </tr>
 <tr>
-<td>1 Range check: If the Pig value is out of range for the target Hive column, by default NULL will be written and one warning per target column/type will be logged. The user may specify “<code>onOutOfRangeValue Throw</code>” to HCatStorer so that an error will be raised instead. For example:<code>store data into 'test\_tbl' using org.apache.hive.hcatalog.pig.HCatStorer('','','-onOutOfRangeValue Throw');</code>The only values for <code>onOutOfRangeValue</code> are <code>Throw</code> and [...]
+<td>1 Range check: If the Pig value is out of range for the target Hive column, by default NULL will be written and one warning per target column/type will be logged. The user may specify “<code>onOutOfRangeValue Throw</code>” to HCatStorer so that an error will be raised instead. For example:<code>store data into 'test_tbl' using org.apache.hive.hcatalog.pig.HCatStorer('','','-onOutOfRangeValue Throw');</code>The only values for <code>onOutOfRangeValue</code> are <code>Throw</code> and  [...]
 <td></td>
 <td></td>
 <td></td>
diff --git a/docs/latest/hcatalog-notification_34014558/index.html b/docs/latest/hcatalog-notification_34014558/index.html
index d24dad9..8bd476c 100644
--- a/docs/latest/hcatalog-notification_34014558/index.html
+++ b/docs/latest/hcatalog-notification_34014558/index.html
@@ -153,13 +153,13 @@ conn.start();
 </ul>
 <pre tabindex=0><code>HiveMetaStoreClient msc = new HiveMetaStoreClient(hiveConf);
 String topicName = msc.getTable(&quot;mydb&quot;,
-                   &quot;myTbl&quot;).getParameters().get(HCatConstants.HCAT\_MSGBUS\_TOPIC\_NAME);
+                   &quot;myTbl&quot;).getParameters().get(HCatConstants.HCAT_MSGBUS_TOPIC_NAME);
 
 </code></pre><p>``</p>
 <ul>
 <li>Use the topic name to subscribe to a topic as follows:</li>
 </ul>
-<pre tabindex=0><code>Session session = conn.createSession(true, Session.SESSION\_TRANSACTED);
+<pre tabindex=0><code>Session session = conn.createSession(true, Session.SESSION_TRANSACTED);
 Destination hcatTopic = session.createTopic(topicName);
 MessageConsumer consumer = session.createConsumer(hcatTopic);
 consumer.setMessageListener(this);
@@ -172,9 +172,9 @@ consumer.setMessageListener(this);
 </ol>
 <pre tabindex=0><code>@Override
 public void onMessage(Message msg) {
-  // We are interested in only add\_partition events on this table.
+  // We are interested in only add_partition events on this table.
   // So, check message type first.
-  if(msg.getStringProperty(HCatConstants.HCAT\_EVENT).equals(HCatConstants.HCAT\_ADD\_PARTITION\_EVENT)){
+  if(msg.getStringProperty(HCatConstants.HCAT_EVENT).equals(HCatConstants.HCAT_ADD_PARTITION_EVENT)){
        Object obj = (((ObjectMessage)msg).getObject());
   }
 }
@@ -192,7 +192,7 @@ partMap.put(&quot;date&quot;,&quot;20110711&quot;);
 partMap.put(&quot;country&quot;,&quot;*&quot;);
 
 // Mark the partition as &quot;done&quot;
-msc.markPartitionForEvent(&quot;mydb&quot;, &quot;mytbl&quot;, partMap, PartitionEventType.LOAD\_DONE);
+msc.markPartitionForEvent(&quot;mydb&quot;, &quot;mytbl&quot;, partMap, PartitionEventType.LOAD_DONE);
 
 </code></pre><p>To receive this notification, the consumer needs to do the following:</p>
 <ol>
@@ -207,17 +207,17 @@ partMap.put(&quot;date&quot;,&quot;20110711&quot;);
 partMap.put(&quot;country&quot;,&quot;*&quot;);
 
 // Mark the partition as &quot;done&quot;
-msc.markPartitionForEvent(&quot;mydb&quot;, &quot;mytbl&quot;, partMap, PartitionEventType.LOAD\_DONE);
+msc.markPartitionForEvent(&quot;mydb&quot;, &quot;mytbl&quot;, partMap, PartitionEventType.LOAD_DONE);
 
 </code></pre><p>If the consumer has registered with the message bus and is currently live, it will get the callback from the message bus once the producer marks the partition as &ldquo;done&rdquo;. Alternatively, the consumer can ask explicitly for a particular partition from the metastore. The following code illustrates the usage from a consumer&rsquo;s perspective:</p>
 <pre tabindex=0><code>// Enquire to metastore whether a particular partition has been marked or not.
-boolean marked = msc.isPartitionMarkedForEvent(&quot;mydb&quot;, &quot;mytbl&quot;, partMap, PartitionEventType.LOAD\_DONE);
+boolean marked = msc.isPartitionMarkedForEvent(&quot;mydb&quot;, &quot;mytbl&quot;, partMap, PartitionEventType.LOAD_DONE);
 
 // Or register to a message bus and get asynchronous callback.
 ConnectionFactory connFac = new ActiveMQConnectionFactory(amqurl);
 Connection conn = connFac.createConnection();
 conn.start();
-Session session = conn.createSession(true, Session.SESSION\_TRANSACTED);
+Session session = conn.createSession(true, Session.SESSION_TRANSACTED);
 Destination hcatTopic = session.createTopic(topic);
 MessageConsumer consumer = session.createConsumer(hcatTopic);
 consumer.setMessageListener(this);
diff --git a/docs/latest/hcatalog-usinghcat_34013260/index.html b/docs/latest/hcatalog-usinghcat_34013260/index.html
index 719ff6a..13cb2bb 100644
--- a/docs/latest/hcatalog-usinghcat_34013260/index.html
+++ b/docs/latest/hcatalog-usinghcat_34013260/index.html
@@ -166,13 +166,13 @@ hcat &quot;alter table rawevents add partition (ds='20100819') location 'hdfs://
 <p>Sally in data processing uses Pig to cleanse and prepare the data.</p>
 <p>Without HCatalog, Sally must be manually informed by Joe when data is available, or poll on HDFS.</p>
 <pre tabindex=0><code>A = load '/data/rawevents/20100819/data' as (alpha:int, beta:chararray, ...);
-B = filter A by bot\_finder(zeta) = 0;
+B = filter A by bot_finder(zeta) = 0;
 ...
 store Z into 'data/processedevents/20100819/data';
 
 </code></pre><p>With HCatalog, HCatalog will send a JMS message that data is available. The Pig job can then be started.</p>
 <pre tabindex=0><code>A = load 'rawevents' using org.apache.hive.hcatalog.pig.HCatLoader();
-B = filter A by date = '20100819' and by bot\_finder(zeta) = 0;
+B = filter A by date = '20100819' and by bot_finder(zeta) = 0;
 ...
 store Z into 'processedevents' using org.apache.hive.hcatalog.pig.HCatStorer(&quot;date=20100819&quot;);
 
@@ -181,16 +181,16 @@ store Z into 'processedevents' using org.apache.hive.hcatalog.pig.HCatStorer(&qu
 <p>Without HCatalog, Robert must alter the table to add the required partition.</p>
 <pre tabindex=0><code>alter table processedevents add partition 20100819 hdfs://data/processedevents/20100819/data
 
-select advertiser\_id, count(clicks)
+select advertiser_id, count(clicks)
 from processedevents
 where date = '20100819'
-group by advertiser\_id;
+group by advertiser_id;
 
 </code></pre><p>With HCatalog, Robert does not need to modify the table structure.</p>
-<pre tabindex=0><code>select advertiser\_id, count(clicks)
+<pre tabindex=0><code>select advertiser_id, count(clicks)
 from processedevents
 where date = ‘20100819’
-group by advertiser\_id;
+group by advertiser_id;
 
 </code></pre><h2 id=hcatalog-web-api>HCatalog Web API</h2>
 <p><em>WebHCat</em> is a REST API for HCatalog. (REST stands for &ldquo;<a href=http://en.wikipedia.org/wiki/Representational_state_transfer>representational state transfer</a>&rdquo;, a style of API based on HTTP verbs).  The original name of WebHCat was <em>Templeton</em>. For more information, see the <a href=https://hive.apache.org/docs/latest/webhcat_33299069/>WebHCat manual</a>.</p>
diff --git a/docs/latest/hive-iceberg-integration_282102247/index.html b/docs/latest/hive-iceberg-integration_282102247/index.html
index 43fd683..2c3ad41 100644
--- a/docs/latest/hive-iceberg-integration_282102247/index.html
+++ b/docs/latest/hive-iceberg-integration_282102247/index.html
@@ -115,76 +115,94 @@ ASF
 <div class=content>
 <div class=docs>
 <h1 id=apache-hive--hive-iceberg-integration>Apache Hive : Hive-Iceberg Integration</h1>
-<p>Apache Hive starting from 4.0 out of the box supports the Iceberg table format, the iceberg tables can be created like regular hive external or ACID tables, without the need of any need of adding any extra jars.</p>
+<p>Apache Hive starting from 4.0 out of the box supports the Iceberg table format, the iceberg tables can be created like regular hive external or ACID tables, without adding any extra jars.</p>
 <p><strong>Creating an Iceberg Table</strong></p>
-<p>An iceberg table can be created using <em><strong>STORED BY ICEBERG</strong></em>keywords while creating a table.</p>
+<p>An iceberg table can be created using <em><strong>STORED BY ICEBERG</strong></em> keywords while creating a table.</p>
 <ul>
 <li>Creating an Iceberg table using normal create command</li>
 </ul>
-<pre tabindex=0><code>CREATE TABLE TBL\_ICE (ID INT) STORED BY ICEBERG;
+<pre tabindex=0><code>CREATE TABLE TBL_ICE (ID INT) STORED BY ICEBERG;
 </code></pre><p>The above creates an iceberg table named &lsquo;TBL_ICE&rsquo;</p>
 <ul>
 <li>Creating an Iceberg Table using CTAS</li>
 </ul>
-<pre tabindex=0><code>CREATE TABLE TABLE\_CTAS AS SELECT * FROM SRCTABLE STORED BY ICEBERG;
+<pre tabindex=0><code>CREATE TABLE TABLE_CTAS AS SELECT * FROM SRCTABLE STORED BY ICEBERG;
 </code></pre><p>The above creates an iceberg table named &lsquo;TABLE_CTAS&rsquo; with schema & records as in &lsquo;SRCTABLE&rsquo; </p>
 <ul>
 <li>Creating an Iceberg Table using CTLT</li>
 </ul>
-<pre tabindex=0><code>CREATE TABLE\_CTLT LIKE SRCTABLE STORED BY ICEBERG;
+<pre tabindex=0><code>CREATE TABLE_CTLT LIKE SRCTABLE STORED BY ICEBERG;
 </code></pre><p>The above creates an iceberg table named &lsquo;TABLE_CTLT&rsquo; with schema same as SRCTABLE</p>
 <p><strong>Format Versions:</strong></p>
 <p>The iceberg tables support both v1 & v2 tables, the tables by default are created as v1 table unless explicitly specified. To create a v2 table (&lsquo;format-version&rsquo;=&lsquo;2&rsquo;)  can be specified as table property while creating the table</p>
 <p>Example:</p>
-<pre tabindex=0><code>CREATE TABLE V2\_TABLE (ID INT) STORED BY ICEBERG TBLPROPERTIES ('format-version'='2');
+<pre tabindex=0><code>CREATE TABLE V2_TABLE (ID INT) STORED BY ICEBERG TBLPROPERTIES ('format-version'='2');
 </code></pre><p><strong>File Formats:</strong></p>
 <p>The iceberg table currently supports three file formats: PARQUET, ORC & AVRO. The default file format is Parquet. The file format can be explicitily provided by using STORED AS while creating the table</p>
 <p>Example-1:</p>
-<pre tabindex=0><code>CREATE TABLE ORC\_TABLE (ID INT) STORED BY ICEBERG STORED AS ORC;
+<pre tabindex=0><code>CREATE TABLE ORC_TABLE (ID INT) STORED BY ICEBERG STORED AS ORC;
 </code></pre><p>The above creates a v1 iceberg table named &lsquo;ORC_TABLE&rsquo; of ORC file format.</p>
 <p>Example-2:</p>
-<pre tabindex=0><code>CREATE TABLE V2\_ORC\_TABLE (ID INT) STORED BY ICEBERG STORED AS ORC TBLPROPERTIES ('format-version'='2');
+<pre tabindex=0><code>CREATE TABLE V2_ORC_TABLE (ID INT) STORED BY ICEBERG STORED AS ORC TBLPROPERTIES ('format-version'='2');
 </code></pre><p>The above creates a v2 iceberg table named &lsquo;V2_ORC_TABLE&rsquo; of ORC file format.</p>
 <p>Similarly we can specify any of the supported file formats while creating the table,</p>
 <p><strong>Delete Modes:</strong></p>
 <p>Hive for delete, update & merge queries support both Copy-on-Write and Merge-on-Read, by default the tables are created with Merge-on-Read mode. The delete mode can be configured using the following TBLPROPERTIES:</p>
-<p>TODO: COPY ALL THREE </p>
-<p><strong>Migrating existing tables to Iceberg Tables</strong></p>
-<p>Any Hive external table can be converted into an iceberg tables, without actually rewriting the data files again. We can use ALTER TABLE CONVERT TO ICEBERG [TBLPROPERTIES] to convert any existing external table to an iceberg table.</p>
+<pre tabindex=0><code>CREATE TABLE tbl_x (id int) STORED BY ICEBERG TBLPROPERTIES (
+    'write.delete.mode'='copy-on-write',
+    'write.update.mode'='copy-on-write',
+    'write.merge.mode'='copy-on-write'
+);
+</code></pre><p><strong>Migrating existing tables to Iceberg Tables</strong></p>
+<p>Any Hive external table can be converted into an iceberg tables, without actually rewriting the data files again. We can use <em>ALTER TABLE CONVERT TO ICEBERG [TBLPROPERTIES]</em> to convert any existing external table to an iceberg table.</p>
 <pre tabindex=0><code>ALTER TABLE TABLE1 CONVERT TO ICEBERG TBLPROPERTIES ('format-version'='2');
 </code></pre><p>The above converts an existing external table &lsquo;TABLE1&rsquo; into a v2 Iceberg table, specifying the TBLPROPERTIES & format-version is option, if not specified the table will be converted into a v1 iceberg table.</p>
 <p><strong>Querying an Iceberg Table</strong></p>
 <p>Iceberg tables support all query statements similar to any other hive table.</p>
 <p>Example:</p>
-<pre tabindex=0><code>SELECT * FROM TBL\_ICE WHERE ID &gt; 5;
+<pre tabindex=0><code>SELECT * FROM TBL_ICE WHERE ID &gt; 5;
 </code></pre><p><strong>Writing data into iceberg tables</strong></p>
 <p>Iceberg tables supports all data ingestion methods supported with hive</p>
 <ul>
 <li>Insert-Into</li>
 </ul>
-<pre tabindex=0><code>INSERT INTO TBL\_ICE VALUES (1),(2),(3),(4);
+<pre tabindex=0><code>INSERT INTO TBL_ICE VALUES (1),(2),(3),(4);
 </code></pre><ul>
 <li>Insert-Overwrite</li>
 </ul>
-<pre tabindex=0><code>INSERT OVERWRITE TBL\_ICE SELECT * FROM TABLE1;
+<pre tabindex=0><code>INSERT OVERWRITE TBL_ICE SELECT * FROM TABLE1;
 </code></pre><ul>
 <li>Delete</li>
 </ul>
-<pre tabindex=0><code>DELETE FROM TBL\_ICE WHERE ID=5;
+<pre tabindex=0><code>DELETE FROM TBL_ICE WHERE ID=5;
 </code></pre><ul>
 <li>Update</li>
 </ul>
-<pre tabindex=0><code>UPDATE TBL\_ICE WHERE ID=8 SET ID=2;
+<pre tabindex=0><code>UPDATE TBL_ICE WHERE ID=8 SET ID=2;
 </code></pre><ul>
 <li>LOAD DATA</li>
 </ul>
-<pre tabindex=0><code>LOAD DATA LOCAL INPATH '/data/files/doctors.avro' OVERWRITE INTO TABLE ice\_avro;
+<pre tabindex=0><code>LOAD DATA LOCAL INPATH '/data/files/doctors.avro' OVERWRITE INTO TABLE ice_avro;
 </code></pre><p><em>If the config “hive.load.data.use.native.api” is set to “false”, hive will rather than using the Append api, will launch a Tez job to do the LOAD.</em></p>
 <p><strong>Metadata tables:</strong></p>
-<p>Hive supports the following metadata tables for Iceberg tables</p>
-<p>TODO: List them</p>
-<p>The metadata tables can be queried using the syntax ..</p>
-<p><strong>Branches & Tags:</strong></p>
+<p>Hive supports the following metadata tables for Iceberg tables
+The metadata tables can be queried using the syntax <code>&lt;DATABASE NAME>.&lt;TABLE NAME>.&lt;METADATA TABLE></code></p>
+<pre tabindex=0><code>ENTRIES                        SELECT * from db_name.tbl_name.entries;
+FILES                          SELECT * from db_name.tbl_name.files;
+HISTORY                        SELECT * from db_name.tbl_name.history;
+SNAPSHOTS                      SELECT * from db_name.tbl_name.snapshots;
+MANIFESTS                      SELECT * from db_name.tbl_name.manifests;
+PARTITIONS                     SELECT * from db_name.tbl_name.partitions;
+ALL_DATA_FILES                 SELECT * from db_name.tbl_name.all_data_files;
+ALL_MANIFESTS                  SELECT * from db_name.tbl_name.all_manifests;
+ALL_ENTRIES                    SELECT * from db_name.tbl_name.all_entries;
+DATA_FILES                     SELECT * from db_name.tbl_name.data_files;
+DELETE_FILES                   SELECT * from db_name.tbl_name.delete_files;
+METADATA_LOG_ENTRIES           SELECT * from db_name.tbl_name.metadata_log_entries;
+REFS                           SELECT * from db_name.tbl_name.refs;
+ALL_DELETE_FILES               SELECT * from db_name.tbl_name.all_delete_files;
+ALL_FILES                      SELECT * from db_name.tbl_name.all_files;
+</code></pre><p><strong>Branches & Tags:</strong></p>
 <p>Iceberg tables supports branches & tags, the details around the feature can be read <a href=https://medium.com/@ayushtkn/apache-hive-4-x-with-iceberg-branches-tags-3d52293ac0bf>here</a></p>
 </div>
 </div>
diff --git a/docs/latest/hive-metatool_55156221/index.html b/docs/latest/hive-metatool_55156221/index.html
index 8b857a6..381206b 100644
--- a/docs/latest/hive-metatool_55156221/index.html
+++ b/docs/latest/hive-metatool_55156221/index.html
@@ -173,7 +173,7 @@ ASF
 </table>
 <p>If you are unsure which version of Avro SerDe is used, pass both <strong>serdePropKey</strong> and <strong>tablePropKey</strong> arguments with their respective values for the keys to <strong>updateLocation</strong>.</p>
 <p>Hive Configuration Directory</p>
-<p>Note that <code>metatool</code> is a command for Hive administrators and it needs direct access to the metastore RDBMS. In some environments, the RDBMS login information (especially password or the password key) is only stored on the metastore server host or in a metastore server specific config directory (with more restrictive file system permissions). In such cases, make sure you run on the metastore server machine, as the hive user, and also set the HIVE_CONF_DIR environment variab [...]
+<p>Note that <code>metatool</code> is a command for Hive administrators and it needs direct access to the metastore RDBMS. In some environments, the RDBMS login information (especially password or the password key) is only stored on the metastore server host or in a metastore server specific config directory (with more restrictive file system permissions). In such cases, make sure you run on the metastore server machine, as the hive user, and also set the HIVE_CONF_DIR environment variab [...]
 <h3 id=usage-example>Usage Example</h3>
 <p>The following <code>metatool</code> command uses the <strong>updateLocation</strong>, <strong>tablePropKey</strong>, and <strong>serdePropKey</strong> options to update the NameNode location to hdfs://localhost:9000 from hdfs://namenode2:8020.</p>
 <pre tabindex=0><code>./hive --service metatool -updateLocation hdfs://localhost:9000 hdfs://namenode2:8020 -tablePropKey avro.schema.url -serdePropKey avro.schema.url
@@ -189,26 +189,26 @@ Initializing HiveMetaTool..
 15/04/22 14:18:44 INFO DataNucleus.Query: Reading in results for query &quot;org.datanucleus.store.rdbms.query.SQLQuery@0&quot; since the connection used is closing
 15/04/22 14:18:44 INFO metastore.MetaStoreDirectSql: Using direct SQL, underlying DB is MYSQL
 15/04/22 14:18:44 INFO metastore.ObjectStore: Initialized ObjectStore
-Looking for LOCATION\_URI field in DBS table to update..
+Looking for LOCATION_URI field in DBS table to update..
 Successfully updated the following locations..
 Updated 0 records in DBS table
 Looking for LOCATION field in SDS table to update..
 Successfully updated the following locations..
 Updated 0 records in SDS table
-Looking for value of avro.schema.url key in TABLE\_PARAMS table to update..
+Looking for value of avro.schema.url key in TABLE_PARAMS table to update..
 Successfully updated the following locations..
-Updated 0 records in TABLE\_PARAMS table
-Looking for value of avro.schema.url key in SD\_PARAMS table to update..
+Updated 0 records in TABLE_PARAMS table
+Looking for value of avro.schema.url key in SD_PARAMS table to update..
 Successfully updated the following locations..
-Updated 0 records in SD\_PARAMS table
-Looking for value of avro.schema.url key in SERDE\_PARAMS table to update..
+Updated 0 records in SD_PARAMS table
+Looking for value of avro.schema.url key in SERDE_PARAMS table to update..
 Successfully updated the following locations..
-Updated 0 records in SERDE\_PARAMS table
+Updated 0 records in SERDE_PARAMS table
 </code></pre><p> </p>
 <p>Using metatool to read out table information (for all metastore backends).</p>
-<pre tabindex=0><code>HIVE\_CONF\_DIR=/etc/hive/conf/conf.server/ hive --service metatool -executeJDOQL 'select dbName+&quot;.&quot;+tableName+&quot;::&quot;+colName+&quot;=&quot;+numDVs from org.apache.hadoop.hive.metastore.model.MTableColumnStatistics';
+<pre tabindex=0><code>HIVE_CONF_DIR=/etc/hive/conf/conf.server/ hive --service metatool -executeJDOQL 'select dbName+&quot;.&quot;+tableName+&quot;::&quot;+colName+&quot;=&quot;+numDVs from org.apache.hadoop.hive.metastore.model.MTableColumnStatistics';
 </code></pre><pre tabindex=0><code>  
- HIVE\_CONF\_DIR=/etc/hive/conf/conf.server/ hive --service metatool -executeJDOQL 'select dbName+&quot;.&quot;+tableName+&quot;(&quot;+partitionName+&quot;)::&quot;+colName+&quot;=&quot;+numDVs from org.apache.hadoop.hive.metastore.model.MPartitionColumnStatistics';
+ HIVE_CONF_DIR=/etc/hive/conf/conf.server/ hive --service metatool -executeJDOQL 'select dbName+&quot;.&quot;+tableName+&quot;(&quot;+partitionName+&quot;)::&quot;+colName+&quot;=&quot;+numDVs from org.apache.hadoop.hive.metastore.model.MPartitionColumnStatistics';
 </code></pre><p> </p>
 </div>
 </div>
diff --git a/docs/latest/hive-on-tez_33296197/index.html b/docs/latest/hive-on-tez_33296197/index.html
index 06fde77..9b33ef0 100644
--- a/docs/latest/hive-on-tez_33296197/index.html
+++ b/docs/latest/hive-on-tez_33296197/index.html
@@ -256,40 +256,40 @@ mr (default): Submit single map, single reduce plans</li>
 <p>Here’s a TPC-DS query and plans with and without Tez optimizations enabled:</p>
 <p>The query (rewritten for Hive):</p>
 <pre tabindex=0><code>select
-  i\_item\_desc
-  ,i\_category
-  ,i\_class
-  ,i\_current\_price
-  ,i\_item\_id
+  i_item_desc
+  ,i_category
+  ,i_class
+  ,i_current_price
+  ,i_item_id
   ,itemrevenue
   ,itemrevenue*100/sum(itemrevenue) over
-    (partition by i\_class) as revenueratio
+    (partition by i_class) as revenueratio
 from
   (select
-     i\_item\_desc
-     ,i\_category
-     ,i\_class
-     ,i\_current\_price
-     ,i\_item\_id
-     ,sum(ws\_ext\_sales\_price) as itemrevenue
+     i_item_desc
+     ,i_category
+     ,i_class
+     ,i_current_price
+     ,i_item_id
+     ,sum(ws_ext_sales_price) as itemrevenue
    from
-     web\_sales
-     join item on (web\_sales.ws\_item\_sk = item.i\_item\_sk)
-     join date\_dim on (web\_sales.ws\_sold\_date\_sk = date\_dim.d\_date\_sk)
+     web_sales
+     join item on (web_sales.ws_item_sk = item.i_item_sk)
+     join date_dim on (web_sales.ws_sold_date_sk = date_dim.d_date_sk)
    where
-     i\_category in ('1', '2', '3')
-     and year(d\_date) = 2001 and month(d\_date) = 10
+     i_category in ('1', '2', '3')
+     and year(d_date) = 2001 and month(d_date) = 10
    group by
-     i\_item\_id
-     ,i\_item\_desc
-     ,i\_category
-     ,i\_class
-     ,i\_current\_price) tmp
+     i_item_id
+     ,i_item_desc
+     ,i_category
+     ,i_class
+     ,i_current_price) tmp
 order by
-  i\_category
-  ,i\_class
-  ,i\_item\_id
-  ,i\_item\_desc
+  i_category
+  ,i_class
+  ,i_item_id
+  ,i_item_desc
   ,revenueratio;
 
 </code></pre><h3 id=plan-with-tez>Plan with TEZ</h3>
diff --git a/docs/latest/hive-schema-tool_34835119/index.html b/docs/latest/hive-schema-tool_34835119/index.html
index 3d5e00a..e33e37e 100644
--- a/docs/latest/hive-schema-tool_34835119/index.html
+++ b/docs/latest/hive-schema-tool_34835119/index.html
@@ -182,7 +182,7 @@ usage: schemaTool
 <li>Initialize to current schema for a new Hive setup:</li>
 </ul>
 <pre tabindex=0><code>$ schematool -dbType derby -initSchema
-Metastore connection URL:        jdbc:derby:;databaseName=metastore\_db;create=true
+Metastore connection URL:        jdbc:derby:;databaseName=metastore_db;create=true
 Metastore Connection Driver :    org.apache.derby.jdbc.EmbeddedDriver
 Metastore connection User:       APP
 Starting metastore schema initialization to 0.13.0
@@ -194,7 +194,7 @@ schemaTool completed
 <li>Get schema information:</li>
 </ul>
 <pre tabindex=0><code>$ schematool -dbType derby -info
-Metastore connection URL:        jdbc:derby:;databaseName=metastore\_db;create=true
+Metastore connection URL:        jdbc:derby:;databaseName=metastore_db;create=true
 Metastore Connection Driver :    org.apache.derby.jdbc.EmbeddedDriver
 Metastore connection User:       APP
 Hive distribution version:       0.13.0
@@ -205,7 +205,7 @@ schemaTool completed
 <li>Attempt to get schema information with older metastore:</li>
 </ul>
 <pre tabindex=0><code>$ schematool -dbType derby -info
-Metastore connection URL:        jdbc:derby:;databaseName=metastore\_db;create=true
+Metastore connection URL:        jdbc:derby:;databaseName=metastore_db;create=true
 Metastore Connection Driver :    org.apache.derby.jdbc.EmbeddedDriver
 Metastore connection User:       APP
 Hive distribution version:       0.13.0
@@ -217,7 +217,7 @@ org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema version
 <li>Upgrade schema from an 0.10.0 release by specifying the &lsquo;from&rsquo; version:</li>
 </ul>
 <pre tabindex=0><code>$ schematool -dbType derby -upgradeSchemaFrom 0.10.0
-Metastore connection URL:        jdbc:derby:;databaseName=metastore\_db;create=true
+Metastore connection URL:        jdbc:derby:;databaseName=metastore_db;create=true
 Metastore Connection Driver :    org.apache.derby.jdbc.EmbeddedDriver
 Metastore connection User:       APP
 Starting upgrade metastore schema from version 0.10.0 to 0.13.0
diff --git a/docs/latest/hive-transactions_40509723/index.html b/docs/latest/hive-transactions_40509723/index.html
index 8e1d827..7988acb 100644
--- a/docs/latest/hive-transactions_40509723/index.html
+++ b/docs/latest/hive-transactions_40509723/index.html
@@ -199,12 +199,12 @@ ASF
 <p>Previously all files for a partition (or a table if the table is not partitioned) lived in a single directory.  With these changes, any partitions (or tables) written with an ACID aware writer will have a directory for the base files and a directory for each set of delta files.  Here is what this may look like for an unpartitioned table &ldquo;t&rdquo;:</p>
 <p><strong>Filesystem Layout for Table &ldquo;t&rdquo;</strong></p>
 <pre tabindex=0><code>hive&gt; dfs -ls -R /user/hive/warehouse/t;
-drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:03 /user/hive/warehouse/t/base\_0000022
--rw-r--r--   1 ekoifman staff        602 2016-06-09 17:03 /user/hive/warehouse/t/base\_0000022/bucket\_00000
-drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:06 /user/hive/warehouse/t/delta\_0000023\_0000023\_0000
--rw-r--r--   1 ekoifman staff        611 2016-06-09 17:06 /user/hive/warehouse/t/delta\_0000023\_0000023\_0000/bucket\_00000
-drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:07 /user/hive/warehouse/t/delta\_0000024\_0000024\_0000
--rw-r--r--   1 ekoifman staff        610 2016-06-09 17:07 /user/hive/warehouse/t/delta\_0000024\_0000024\_0000/bucket\_00000
+drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:03 /user/hive/warehouse/t/base_0000022
+-rw-r--r--   1 ekoifman staff        602 2016-06-09 17:03 /user/hive/warehouse/t/base_0000022/bucket_00000
+drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:06 /user/hive/warehouse/t/delta_0000023_0000023_0000
+-rw-r--r--   1 ekoifman staff        611 2016-06-09 17:06 /user/hive/warehouse/t/delta_0000023_0000023_0000/bucket_00000
+drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:07 /user/hive/warehouse/t/delta_0000024_0000024_0000
+-rw-r--r--   1 ekoifman staff        610 2016-06-09 17:07 /user/hive/warehouse/t/delta_0000024_0000024_0000/bucket_00000
 </code></pre><h3 id=compactor>Compactor</h3>
 <p>Compactor is a set of background processes running inside the Metastore to support ACID system.  It consists of Initiator, Worker, Cleaner, AcidHouseKeeperService and a few others.</p>
 <h4 id=delta-file-compaction>Delta File Compaction</h4>
@@ -480,7 +480,7 @@ drwxr-xr-x   - ekoifman staff          0 2016-06-09 17:07 /user/hive/warehouse/t
 <p>Table properties are set with the TBLPROPERTIES clause when a table is created or altered, as described in the <a href=#create-table>Create Table</a> and <a href=#alter-table-properties>Alter Table Properties</a> sections of Hive Data Definition Language. The &ldquo;<code>transactional</code>&rdquo; and &ldquo;<code>NO_AUTO_COMPACTION</code>&rdquo; table properties are case-sensitive in Hive releases 0.x and 1.0, but they are case-insensitive starting with release 1.1.0 (<a href=https [...]
 <p>More compaction related options can be set via TBLPROPERTIES as of <a href=https://issues.apache.org/jira/browse/HIVE-13354>Hive 1.3.0 and 2.1.0</a>. They can be set at both table-level via <a href=https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-Create/Drop/TruncateTable>CREATE TABLE</a>, and on request-level via <a href=https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-AlterTable/PartitionCompact>ALTER TABLE/PA [...]
 <p><strong>Example: Set compaction options in TBLPROPERTIES at table level</strong></p>
-<pre tabindex=0><code>CREATE TABLE table\_name (
+<pre tabindex=0><code>CREATE TABLE table_name (
   id                int,
   name              string
 )
@@ -492,9 +492,9 @@ TBLPROPERTIES (&quot;transactional&quot;=&quot;true&quot;,
                                                                    -- size of base files is greater than 50%
 );
 </code></pre><p><strong>Example: Set compaction options in TBLPROPERTIES at request level</strong></p>
-<pre tabindex=0><code>ALTER TABLE table\_name COMPACT 'minor' 
+<pre tabindex=0><code>ALTER TABLE table_name COMPACT 'minor' 
    WITH OVERWRITE TBLPROPERTIES (&quot;compactor.mapreduce.map.memory.mb&quot;=&quot;3072&quot;);  -- specify compaction map job properties
-ALTER TABLE table\_name COMPACT 'major'
+ALTER TABLE table_name COMPACT 'major'
    WITH OVERWRITE TBLPROPERTIES (&quot;tblprops.orc.compress.size&quot;=&quot;8192&quot;);         -- change any other Hive table properties
 </code></pre><h1 id=talks-and-presentations>Talks and Presentations</h1>
 <p>Transactional Operations In Hive by Eugene Koifman at <a href=https://dataworkssummit.com/san-jose-2017/agenda/>Dataworks Summit 2017, San Jose, CA, USA</a></p>
diff --git a/docs/latest/hive-udfs_282102277/index.html b/docs/latest/hive-udfs_282102277/index.html
index 7c819c4..b623677 100644
--- a/docs/latest/hive-udfs_282102277/index.html
+++ b/docs/latest/hive-udfs_282102277/index.html
@@ -134,7 +134,7 @@ ASF
 <p>Every UDF&rsquo;s evaluate method is one row at a time! This means if your UDFs has complex code, it could introduce performance issue in execution time.</p>
 <p>To gain an understanding of UDFs, let&rsquo;s begin with an example to comprehend their execution pattern.</p>
 <p><strong>UDF&rsquo;s in action</strong></p>
-<pre tabindex=0><code>SELECT length(string\_col) FROM table\_name;
+<pre tabindex=0><code>SELECT length(string_col) FROM table_name;
 </code></pre><p>In this case, the <strong>length</strong> of thebuilt-in UDF evaluates each row of the string_col values. </p>
 <p>As we see how a built-in UDF works let&rsquo;s see what kind of built-in UDFs the Apache Hive has.</p>
 <p>Tipp</p>
@@ -184,37 +184,37 @@ ASF
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>variance(col), var\_pop(col)</code></td>
+<td><code>variance(col), var_pop(col)</code></td>
 <td>Returns the variance of a numeric column in the group. MODIFIED</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDAFVariance.java>GenericUDAFVariance</a></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>var\_samp(col)</code></td>
+<td><code>var_samp(col)</code></td>
 <td>Returns the unbiased sample variance of a numeric column in the group.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDAFVarianceSample.java>GenericUDAFVarianceSample</a></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>stddev\_pop(col)</code></td>
+<td><code>stddev_pop(col)</code></td>
 <td>Returns the standard deviation of a numeric column in the group.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDAFStd.java>GenericUDAFStd</a></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>stddev\_samp(col)</code></td>
+<td><code>stddev_samp(col)</code></td>
 <td>Returns the unbiased sample standard deviation of a numeric column in the group.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDAFStdSample.java>GenericUDAFStdSample</a></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>covar\_pop(col1, col2)</code></td>
+<td><code>covar_pop(col1, col2)</code></td>
 <td>Returns the population covariance of a pair of numeric columns in the group.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDAFCovariance.java>GenericUDAFCovariance</a></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>covar\_samp(col1, col2)</code></td>
+<td><code>covar_samp(col1, col2)</code></td>
 <td>Returns the sample covariance of a pair of numeric columns in the group.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDAFCovarianceSample.java>GenericUDAFCovarianceSample</a></td>
 </tr>
@@ -238,85 +238,85 @@ ASF
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>percentile\_approx(double col, p [, B])</code></td>
+<td><code>percentile_approx(double col, p [, B])</code></td>
 <td>Returns an approximate pth percentile of a numeric column (including floating point types) in the group. The B parameter controls approximation accuracy at the cost of memory. Higher values yield better approximations, and the default is 10,000. When the number of distinct values in col is smaller than B, this gives an exact percentile value.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDAFPercentileApprox.java>GenericUDAFPercentileApprox</a></td>
 </tr>
 <tr>
 <td><strong>array</strong></td>
-<td><code>percentile\_approx(double col, array(p1 [, p2]...) [, B])</code></td>
+<td><code>percentile_approx(double col, array(p1 [, p2]...) [, B])</code></td>
 <td>Same as above, but accepts and returns an array of percentile values instead of a single one.</td>
 <td></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>regr\_avgx(independent, dependent)</code></td>
+<td><code>regr_avgx(independent, dependent)</code></td>
 <td>Equivalent to avg(dependent). </td>
 <td></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>regr\_avgy(independent, dependent)</code></td>
+<td><code>regr_avgy(independent, dependent)</code></td>
 <td>Equivalent to avg(independent). </td>
 <td></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>regr\_count(independent, dependent)</code></td>
+<td><code>regr_count(independent, dependent)</code></td>
 <td>Returns the number of non-null pairs used to fit the linear regression line. </td>
 <td></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>regr\_intercept(independent, dependent)</code></td>
+<td><code>regr_intercept(independent, dependent)</code></td>
 <td>Returns the y-intercept of the <a href=https://en.wikipedia.org/wiki/Linear_regression>linear regression line</a>, i.e. the value of b in the equation dependent = a * independent + b.</td>
 <td></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>regr\_r2(independent, dependent)</code></td>
+<td><code>regr_r2(independent, dependent)</code></td>
 <td>Returns the <a href=https://en.wikipedia.org/wiki/Coefficient_of_determination>coefficient of determination</a> for the regression. </td>
 <td></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>regr\_slope(independent, dependent)</code></td>
+<td><code>regr_slope(independent, dependent)</code></td>
 <td>Returns the slope of the <a href=https://en.wikipedia.org/wiki/Linear_regression>linear regression line</a>, i.e. the value of an in the equation dependent = a * independent + b. </td>
 <td></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>regr\_sxx(independent, dependent)</code></td>
+<td><code>regr_sxx(independent, dependent)</code></td>
 <td>Equivalent to regr_count(independent, dependent) * var_pop(dependent). </td>
 <td></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>regr\_sxy(independent, dependent)</code></td>
+<td><code>regr_sxy(independent, dependent)</code></td>
 <td>Equivalent to regr_count(independent, dependent) * covar_pop(independent, dependent). </td>
 <td></td>
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>regr\_syy(independent, dependent)</code></td>
+<td><code>regr_syy(independent, dependent)</code></td>
 <td>Equivalent to regr_count(independent, dependent) * var_pop(independent).</td>
 <td></td>
 </tr>
 <tr>
 <td><strong>array&lt;struct {<code>'x','y'</code>}></strong></td>
-<td><code>histogram\_numeric(col, b)</code></td>
+<td><code>histogram_numeric(col, b)</code></td>
 <td>Computes a histogram of a numeric column in the group using b non-uniformly spaced bins. The output is an array of size b of double-valued (x,y) coordinates that represent the bin centers and heights</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDAFHistogramNumeric.java>GenericUDAFHistogramNumeric</a></td>
 </tr>
 <tr>
 <td><strong>array</strong></td>
-<td><code>collect\_set(col)</code></td>
+<td><code>collect_set(col)</code></td>
 <td>Returns a set of objects with duplicate elements eliminated.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDAFCollectSet.java>GenericUDAFCollectSet</a></td>
 </tr>
 <tr>
 <td><strong>array</strong></td>
-<td><code>collect\_list(col)</code></td>
+<td><code>collect_list(col)</code></td>
 <td>Returns a list of objects with duplicates. </td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDAFCollectList.java>GenericUDAFCollectList</a></td>
 </tr>
@@ -373,13 +373,13 @@ ASF
 </tr>
 <tr>
 <td><strong>string1,&mldr;,stringn</strong></td>
-<td><code>json\_tuple(string jsonStr, string k1,...,string kn)</code></td>
+<td><code>json_tuple(string jsonStr, string k1,...,string kn)</code></td>
 <td>Takes JSON string and a set of <em>n</em> keys, and returns a tuple of <em>n</em> values. This is a more efficient version of the <code>get_json_object</code> UDF because it can get multiple keys with just one call.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDTFJSONTuple.java>GenericUDTFJSONTuple</a></td>
 </tr>
 <tr>
 <td><strong>string 1,&mldr;,stringn</strong></td>
-<td><code>parse\_url\_tuple(string urlStr, string p1,...,string pn)</code></td>
+<td><code>parse_url_tuple(string urlStr, string p1,...,string pn)</code></td>
 <td>Takes URLstring and a set of n URL parts, and returns a tuple of n values. This is similar to the parse_url() UDF but can extract multiple parts at once out of a URL. Valid part names are HOST, PATH, QUERY, REF, PROTOCOL, AUTHORITY, FILE, USERINFO, QUERY:.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDTFParseUrlTuple.java>GenericUDTFParseUrlTuple</a></td>
 </tr>
@@ -411,7 +411,7 @@ ASF
 </tr>
 <tr>
 <td><strong>int</strong></td>
-<td><code>character\_length(string str)</code></td>
+<td><code>character_length(string str)</code></td>
 <td>Returns the number of UTF-8 characters contained in str. The function char_length is shorthand for this function.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFCharacterLength.java>GenericUDFCharacterLength</a></td>
 </tr>
@@ -429,19 +429,19 @@ ASF
 </tr>
 <tr>
 <td><strong>array&lt;struct&lt;string,double&#187;</strong></td>
-<td><code>context\_ngrams(array&lt;array&lt;string>>, array&lt;string>, int K, int pf)</code></td>
+<td><code>context_ngrams(array&lt;array&lt;string>>, array&lt;string>, int K, int pf)</code></td>
 <td>Returns the top-k contextual N-grams from a set of tokenized sentences, given a string of &ldquo;context&rdquo;. See <a href=https://hive.apache.org/docs/latest/statisticsanddatamining_27362058/>StatisticsAndDataMining</a> for more information.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDAFContextNGrams.java>GenericUDAFContextNGrams</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>concat\_ws(string SEP, string A, string B...)</code></td>
+<td><code>concat_ws(string SEP, string A, string B...)</code></td>
 <td>Like concat() above, but with custom separator SEP.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFConcatWS.java>GenericUDFConcatWS</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>concat\_ws(string SEP, array&lt;string>)</code></td>
+<td><code>concat_ws(string SEP, array&lt;string>)</code></td>
 <td>Like concat_ws() above, but taking an array ofstrings.</td>
 <td></td>
 </tr>
@@ -471,25 +471,25 @@ ASF
 </tr>
 <tr>
 <td><strong>int</strong></td>
-<td><code>find\_in\_set(string str, string strList)</code></td>
+<td><code>find_in_set(string str, string strList)</code></td>
 <td>Returns the first occurrence of str in strList where strList is a comma-delimited string. Returns null if either argument is null. Returns 0 if the first argument contains any commas. For example, find_in_set(&lsquo;ab&rsquo;, &lsquo;abc,b,ab,c,def&rsquo;) returns 3.</td>
 <td><a href=https://github.com/apache/hive/blob/1455f6201b0f7b061361bc9acc23cb810ff02483/ql/src/java/org/apache/hadoop/hive/ql/udf/UDFFindInSet.java>UDFFindInSet</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>format\_number(number x, int d)</code></td>
+<td><code>format_number(number x, int d)</code></td>
 <td>Formats the number X to a format like &lsquo;#,###,###.##&rsquo;, rounded to D decimal places, and returns the result as a string. If D is 0, the result has no decimal point or fractional part.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFFormatNumber.java>GenericUDFFormatNumber</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>get\_json\_object(string json\_string,string path)</code></td>
+<td><code>get_json_object(string json_string,string path)</code></td>
 <td>Extracts JSON object from a JSON string based on JSON path specified, and returns JSON string of the extracted JSON object. It will return null if the input JSON string is invalid.NoteThe json path can only have the characters [0-9a-z_], i.e., no upper-case or special characters. Also, the keys <em>cannot start with numbers.</em> This is due to restrictions on Hive column names.</td>
 <td><a href=https://github.com/apache/hive/blob/1455f6201b0f7b061361bc9acc23cb810ff02483/ql/src/java/org/apache/hadoop/hive/ql/udf/UDFJson.java>UDFJson</a></td>
 </tr>
 <tr>
 <td><strong>boolean</strong></td>
-<td><code>in\_file(string str, string filename)</code></td>
+<td><code>in_file(string str, string filename)</code></td>
 <td>Returns true if the string <code>str</code> appears as an entire line in <code>filename</code>.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFInFile.java>GenericUDFInFile</a></td>
 </tr>
@@ -537,13 +537,13 @@ ASF
 </tr>
 <tr>
 <td><strong>int</strong></td>
-<td><code>octet\_length(string str)</code></td>
+<td><code>octet_length(string str)</code></td>
 <td>Returns the number of octets required to hold the string str in UTF-8 encoding.  Note that octet_length(str) can be larger than character_length(str).</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFOctetLength.java>GenericUDFOctetLength</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>parse\_url(string urlString,string partToExtract [,string keyToExtract])</code></td>
+<td><code>parse_url(string urlString,string partToExtract [,string keyToExtract])</code></td>
 <td>Returns the specified part from the URL. Valid values for partToExtract include HOST, PATH, QUERY, REF, PROTOCOL, AUTHORITY, FILE, and USERINFO. For example, parse_url('<a href="http://facebook.com/path1/p.php?k1=v1&k2=v2#Ref1">http://facebook.com/path1/p.php?k1=v1&k2=v2#Ref1</a>&rsquo;, &lsquo;HOST&rsquo;) returns &lsquo;<a href=http://facebook.com>facebook.com</a>&rsquo;. Also, a value of a particular key in QUERY can be extracted by providing the key as the third argument, for exa [...]
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/UDFParseUrl.java>UDFParseUrl</a></td>
 </tr>
@@ -595,13 +595,13 @@ ASF
 <tbody>
 <tr>
 <td><strong>string</strong></td>
-<td><code>regexp\_extract(string subject, string pattern, int index)</code></td>
+<td><code>regexp_extract(string subject, string pattern, int index)</code></td>
 <td>Returns the string extracted using the pattern. For example, regexp_extract(&lsquo;foothebar&rsquo;, &lsquo;foo(.*?)(bar)&rsquo;, 2) returns &lsquo;bar.&rsquo; Note that some care is necessary in using predefined character classes: using &lsquo;\s&rsquo; as the second argument will match the letter s; &lsquo;\s&rsquo; is necessary to match whitespace, etc. The &lsquo;index&rsquo; parameter is the Java regex Matcher group() method index. </td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/UDFRegExpExtract.java>UDFRegExpExtract</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>regexp\_replace(string INITIAL\_STRING, string PATTERN, string REPLACEMENT)</code></td>
+<td><code>regexp_replace(string INITIAL_STRING, string PATTERN, string REPLACEMENT)</code></td>
 <td>Returns the string resulting from replacing all substrings in INITIAL_STRING that match the java regular expression syntax defined in PATTERN with instances of REPLACEMENT. For example, regexp_replace(&ldquo;foobar&rdquo;, &ldquo;oo|ar&rdquo;, &ldquo;") returns &lsquo;fb.&rsquo; Note that some care is necessary in using predefined character classes: using &lsquo;\s&rsquo; as the second argument will match the letter s; &lsquo;\s&rsquo; is necessary to match whitespace, etc.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/UDFRegExpReplace.java>UDFRegExpReplace</a></td>
 </tr>
@@ -655,7 +655,7 @@ ASF
 </tr>
 <tr>
 <td><strong>map&lt;string,string></strong></td>
-<td><code>str\_to\_map(text[, delimiter1, delimiter2])</code></td>
+<td><code>str_to_map(text[, delimiter1, delimiter2])</code></td>
 <td>Splits text into key-value pairs using two delimiters. Delimiter1 separates text into K-V pairs, and Delimiter2 splits each K-V pair. Default delimiters are &lsquo;,&rsquo; for delimiter1 and &lsquo;:&rsquo; for delimiter2.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFStringToMap.java>GenericUDFStringToMap</a></td>
 </tr>
@@ -673,7 +673,7 @@ ASF
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>substring\_index(string A,string delim,int count)</code></td>
+<td><code>substring_index(string A,string delim,int count)</code></td>
 <td>Returns the substring from string A before count occurrences of the delimiter delim. If the count is positive, everything to the left of the final delimiter (counting from the left) is returned. If count is negative, everything to the right of the final delimiter (counting from the right) is returned. Substring_index performs a case-sensitive match when searching for delim. Example: substring_index('<a href=http://www.apache.org>www.apache.org</a>&rsquo;, &lsquo;.&rsquo;, 2) = &lsquo [...]
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFSubstringIndex.java>GenericUDFSubstringIndex</a></td>
 </tr>
@@ -741,31 +741,31 @@ ASF
 <tbody>
 <tr>
 <td><strong>string</strong></td>
-<td><code>from\_unixtime(bigint unixtime[,string pattern])</code></td>
+<td><code>from_unixtime(bigint unixtime[,string pattern])</code></td>
 <td>Converts a number of seconds since epoch (1970-01-01 00:00:00 UTC) to a string representing the timestamp of that moment in the current time zone(using config &ldquo;hive.local.time.zone&rdquo;) using the specified pattern. If the pattern is missing the default is used (&lsquo;uuuu-MM-dd HH:mm:ss&rsquo; or yyyy-MM-dd HH:mm:ss&rsquo;). Example: from_unixtime(0)=1970-01-01 00:00:00 (hive.local.time.zone=Etc/GMT)MODIFIEDAs of Hive 4.0.0 the &ldquo;<strong>hive.datetime.formatter&rdquo;< [...]
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFFromUnixTime.java>GenericUDFFromUnixTime</a></td>
 </tr>
 <tr>
 <td><strong>bigint</strong></td>
-<td><code>unix\_timestamp()</code></td>
+<td><code>unix_timestamp()</code></td>
 <td>Gets the current Unix timestamp in seconds. This function is not deterministic and its value is not fixed for the scope of a query execution, therefore prevents proper optimization of queries - this has been deprecated since 2.0 in favor of CURRENT_TIMESTAMP constant.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFUnixTimeStamp.java>GenericUDFUnixTimeStamp</a></td>
 </tr>
 <tr>
 <td><strong>bigint</strong></td>
-<td><code>unix\_timestamp(string date)</code></td>
+<td><code>unix_timestamp(string date)</code></td>
 <td>Converts a DateTimestring to unix time (seconds since epoch) using the default pattern(s). The default accepted patterns depend on the underlying formatter implementation. The DateTime string does not contain a timezone so the conversion uses the local time zone as specified by &ldquo;hive.local.time.zone&rdquo; property. Returns null when the conversion fails. Example: unix_timestamp(&lsquo;2009-03-20 11:30:01&rsquo;) = 1237573801MODIFIEDAs of Hive 4.0.0 the &ldquo;hive.datetime.for [...]
 <td></td>
 </tr>
 <tr>
 <td><strong>bigint</strong></td>
-<td><code>unix\_timestamp(string date,string pattern)</code></td>
+<td><code>unix_timestamp(string date,string pattern)</code></td>
 <td>Converts a date-time string to unix time (seconds since epoch) using the specified pattern. The accepted patterns and their behavior depend on the underlying formatter implementation. Returns null when the conversion fails. Example: unix_timestamp(&lsquo;2009-03-20&rsquo;, &lsquo;uuuu-MM-dd&rsquo;) = 1237532400MODIFIEDAs of Hive 4.0.0 the &ldquo;hive.datetime.formatter&rdquo; property can be used to control the underlying formatter implementation and as a consequence the accepted pat [...]
 <td></td>
 </tr>
 <tr>
 <td><strong>date</strong></td>
-<td><code>to\_date(string timestamp)</code></td>
+<td><code>to_date(string timestamp)</code></td>
 <td>Returns the date part of a timestamp date object. Example: to_date(&ldquo;1970-01-01 00:00:00&rdquo;) </td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFDate.java>GenericUDFDate</a></td>
 </tr>
@@ -831,55 +831,55 @@ ASF
 </tr>
 <tr>
 <td><strong>date</strong></td>
-<td><code>date\_add(date/timestamp/string startdate, tinyint/smallint/int days)</code></td>
+<td><code>date_add(date/timestamp/string startdate, tinyint/smallint/int days)</code></td>
 <td>Adds a number of days to startdate. Example: date_add(&lsquo;2008-12-31&rsquo;, 1) = &lsquo;2009-01-01&rsquo;.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFDateAdd.java>GenericUDFDateAdd</a></td>
 </tr>
 <tr>
 <td><strong>date</strong></td>
-<td><code>date\_sub(date/timestamp/string startdate, tinyint/smallint/int days)</code></td>
+<td><code>date_sub(date/timestamp/string startdate, tinyint/smallint/int days)</code></td>
 <td>Subtracts a number of days to startdate: date_sub(&lsquo;2008-12-31&rsquo;, 1) = &lsquo;2008-12-30&rsquo;.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFDateSub.java>GenericUDFDateSub</a></td>
 </tr>
 <tr>
 <td><strong>timestamp</strong></td>
-<td><code>from\_utc\_timestamp({any primitive type} ts,string timezone)</code></td>
+<td><code>from_utc_timestamp({any primitive type} ts,string timezone)</code></td>
 <td>Converts a timestamp* in UTC to a given timezone.* timestamp is a primitive type, including timestamp/date, tinyint/smallint/int/bigint, float/double and decimal.Fractional values are considered as seconds.integer values are considered as milliseconds. For example, from_utc_timestamp(2592000.0,&lsquo;PST&rsquo;), from_utc_timestamp(2592000000,&lsquo;PST&rsquo;) and from_utc_timestamp(timestamp &lsquo;1970-01-30 16:00:00&rsquo;,&lsquo;PST&rsquo;) all return the timestamp 1970-01-30 08 [...]
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFFromUtcTimestamp.java>GenericUDFFromUtcTimestamp</a></td>
 </tr>
 <tr>
 <td><strong>timestamp</strong></td>
-<td><code>to\_utc\_timestamp({any primitive type} ts,string timezone)</code></td>
+<td><code>to_utc_timestamp({any primitive type} ts,string timezone)</code></td>
 <td>Converts a timestamp* in a given timezone to UTC.* timestamp is a primitive type, including timestamp/date, tinyint/smallint/int/bigint, float/double and decimal.Fractional values are considered as seconds.integer values are considered as milliseconds. For example, to_utc_timestamp(2592000.0,&lsquo;PST&rsquo;), to_utc_timestamp(2592000000,&lsquo;PST&rsquo;) and to_utc_timestamp(timestamp &lsquo;1970-01-30 16:00:00&rsquo;,&lsquo;PST&rsquo;) all return the timestamp 1970-01-31 00:00:00.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFToUtcTimestamp.java>GenericUDFToUtcTimestamp</a></td>
 </tr>
 <tr>
 <td><strong>date</strong></td>
-<td><code>current\_date</code></td>
+<td><code>current_date</code></td>
 <td>Returns the current date at the start of query evaluation. All calls of current_date within the same query return the same value.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFCurrentDate.java>GenericUDFCurrentDate</a></td>
 </tr>
 <tr>
 <td><strong>timestamp</strong></td>
-<td><code>current\_timestamp</code></td>
+<td><code>current_timestamp</code></td>
 <td>Returns the current timestamp at the start of query evaluation. All calls of current_timestamp within the same query return the same value.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFCurrentTimestamp.java>GenericUDFCurrentTimestamp</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>add\_months(string start\_date,int num\_months, output\_date\_format)</code></td>
+<td><code>add_months(string start_date,int num_months, output_date_format)</code></td>
 <td>Returns the date that is num_months after start_date. start_date is a string, date or timestamp. num_months is an integer. If start_date is the last day of the month or if the resulting month has fewer days than the day component of start_date, then the result is the last day of the resulting month. Otherwise, the result has the same day component as start_date. The default output format is &lsquo;yyyy-MM-dd&rsquo;.MODIFIEDBefore Hive 4.0.0, the time part of the date is ignored. As o [...]
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFAddMonths.java>GenericUDFAddMonths</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>last\_day(string date)</code></td>
+<td><code>last_day(string date)</code></td>
 <td>Returns the last day of the month to which the date belongs. <code>date</code> is a string in the format &lsquo;yyyy-MM-dd HH:mm:ss&rsquo; or &lsquo;yyyy-MM-dd&rsquo;. <strong>The time part of the date is ignored!</strong></td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFLastDay.java>GenericUDFLastDay</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>next\_day(string start\_date,string day\_of\_week)</code></td>
+<td><code>next_day(string start_date,string day_of_week)</code></td>
 <td>Returns the first date which is later than start_date and named as day_of_week.  <code>start_date</code>  is a string/date/timestamp. day_of_week is 2 letters, 3 letters or full name of the day of the week (e.g. Mo, tue, FRIDAY). <strong>The time part of start_date is ignored.</strong> Example: next_day(&lsquo;2015-01-14&rsquo;, &lsquo;TU&rsquo;) = 2015-01-20.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFNextDay.java>GenericUDFNextDay</a></td>
 </tr>
@@ -891,13 +891,13 @@ ASF
 </tr>
 <tr>
 <td><strong>double</strong></td>
-<td><code>months\_between(date1, date2)</code></td>
+<td><code>months_between(date1, date2)</code></td>
 <td>Returns the number of months between dates <code>date1</code> and <code>date2</code>. If <code>date1</code> is later than <code>date2</code>, then the result is positive. If <code>date1</code> is earlier than <code>date</code> , then the result is negative. If date1 and date2 are either the same days of the month or both last days of months, then the result is always aninteger. Otherwise, the UDF calculates the fractional portion of the result based on a 31-day month and considers th [...]
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFMonthsBetween.java>GenericUDFMonthsBetween</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>date\_format(date/timestamp/string ts,string pattern)</code></td>
+<td><code>date_format(date/timestamp/string ts,string pattern)</code></td>
 <td>Converts a date/timestamp/string to a value of string using the specified pattern. The accepted patterns and their behavior depend on the underlying formatter implementation. The pattern argument should be constant. Example: date_format(&lsquo;2015-04-08&rsquo;, &lsquo;y&rsquo;) = &lsquo;2015&rsquo;.date_format can be used to implement other UDFs, e.g.:* dayname(date) is date_format(date, &lsquo;EEEE&rsquo;) dayofyear(date) is date_format(date, &lsquo;D&rsquo;) MODIFIEDAs of Hive 4.0 [...]
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFDateFormat.java>GenericUDFDateFormat</a></td>
 </tr>
@@ -1019,7 +1019,7 @@ ASF
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>conv(bigint num,int from\_base,int to\_base), conv(STRING num,int from\_base,int to\_base)</code></td>
+<td><code>conv(bigint num,int from_base,int to_base), conv(STRING num,int from_base,int to_base)</code></td>
 <td>Converts a number from a given base to another.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/UDFConv.java>UDFConv</a></td>
 </tr>
@@ -1157,7 +1157,7 @@ ASF
 </tr>
 <tr>
 <td><strong>int</strong></td>
-<td><code>width\_bucket(NUMERIC expr, NUMERIC min\_value, NUMERIC max\_value,int num\_buckets)</code></td>
+<td><code>width_bucket(NUMERIC expr, NUMERIC min_value, NUMERIC max_value,int num_buckets)</code></td>
 <td>Returns an integer between 0 and num_buckets+1 by mapping expr into the ith equally sized bucket. Buckets are made by dividing [min_value, max_value]into equally sized regions. If expr &lt; min_value, return 1, if expr > max_value return num_buckets+1. See <a href=https://docs.oracle.com/cd/B19306_01/server.102/b14200/functions214.htm>https://docs.oracle.com/cd/B19306_01/server.102/b14200/functions214.htm</a></td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFWidthBucket.java>GenericUDFWidthBucket</a></td>
 </tr>
@@ -1201,25 +1201,25 @@ ASF
 </tr>
 <tr>
 <td><strong>array</strong></td>
-<td><code>map\_keys(Map&lt;K.V>)</code></td>
+<td><code>map_keys(Map&lt;K.V>)</code></td>
 <td>Returns an unordered array containing the keys of the input map.</td>
 <td></td>
 </tr>
 <tr>
 <td><strong>array</strong></td>
-<td><code>map\_values(Map&lt;K.V>)</code></td>
+<td><code>map_values(Map&lt;K.V>)</code></td>
 <td>Returns an unordered array containing the values of the input map.</td>
 <td></td>
 </tr>
 <tr>
 <td><strong>boolean</strong></td>
-<td><code>array\_contains(Array&lt;T>, value)</code></td>
+<td><code>array_contains(Array&lt;T>, value)</code></td>
 <td>Returns TRUE if the array contains the provided parameter value.</td>
 <td></td>
 </tr>
 <tr>
 <td><strong>array</strong></td>
-<td><code>sort\_array(Array&lt;T>)</code></td>
+<td><code>sort_array(Array&lt;T>)</code></td>
 <td>Sorts the input array in ascending order according to the natural ordering of the array elements and returns it.</td>
 <td></td>
 </tr>
@@ -1231,55 +1231,55 @@ ASF
 </tr>
 <tr>
 <td><strong>array</strong></td>
-<td><code>array\_slice(array, start, length)</code></td>
+<td><code>array_slice(array, start, length)</code></td>
 <td>NEW Returns the subset or range of elements. Example: array-slice(array(1, 2, 3, 4), 2 , 2) Result: 3,4</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFArraySlice.java>GenericUDFArraySlice</a> </td>
 </tr>
 <tr>
 <td><strong>t</strong></td>
-<td><code>array\_min((array(obj1, obj2, obj3...))</code></td>
+<td><code>array_min((array(obj1, obj2, obj3...))</code></td>
 <td>NEW The function returns the minimum value in the array with elements for which order is supported. Example: array_min(array(1, 3, 0, NULL)) Result: 0</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFArrayMin.java>GenericUDFArrayMin</a></td>
 </tr>
 <tr>
 <td><strong>t</strong></td>
-<td><code>array\_max((array(obj1, obj2, obj3...))</code></td>
+<td><code>array_max((array(obj1, obj2, obj3...))</code></td>
 <td>NEW The function returns the maximum value in the array with elements for which order is supported. Example: array_max(array(1, 3, 0, NULL)) Result: 3</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFArrayMax.java>GenericUDFArrayMax</a></td>
 </tr>
 <tr>
 <td><strong>t</strong></td>
-<td><code>array\_distinct(array(obj1, obj2, obj3...))</code></td>
+<td><code>array_distinct(array(obj1, obj2, obj3...))</code></td>
 <td>NEW The function returns an array of the same type as the input array with distinct values. Example: array_distinct(array(&lsquo;b&rsquo;, &rsquo;d', &rsquo;d', &lsquo;a&rsquo;)) Result:  [&lsquo;b&rsquo;, &rsquo;d', &lsquo;a&rsquo;]</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFArrayDistinct.java>GenericUDFArrayDistinct</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>array\_join(array, delimiter, replaceNull)</code></td>
+<td><code>array_join(array, delimiter, replaceNull)</code></td>
 <td>NEW Concatenate the elements of an array with a specified delimiter. Example: array_join(array(1, 2, NULL, 4), &lsquo;,&rsquo;,':') Result: 1,2,:,4</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFArrayJoin.java>GenericUDFArrayJoin</a></td>
 </tr>
 <tr>
 <td><strong>array</strong></td>
-<td><code>array\_expect(array1, array2)</code></td>
+<td><code>array_expect(array1, array2)</code></td>
 <td>NEW Returns an array of the elements in array1 but not in array2. Example: array_expect(array(1, 2, 3,4), array(2,3)) Result: [1,4]</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFArrayExcept.java>GenericUDFArrayExcept</a></td>
 </tr>
 <tr>
 <td><strong>array</strong></td>
-<td><code>array\_intersect(array1, array2)</code></td>
+<td><code>array_intersect(array1, array2)</code></td>
 <td>NEW Returns an array of the elements in the intersection of array1 and array2, without duplicates. Example: array_intersect(array(1, 2, 3,4), array(1,2,3)) Result: [1,2,3]</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFArrayIntersect.java>GenericUDFArrayIntersect</a></td>
 </tr>
 <tr>
 <td><strong>array</strong></td>
-<td><code>array\_union(array1, array2)</code></td>
+<td><code>array_union(array1, array2)</code></td>
 <td>NEW Returns an array of the elements in the union of array1 and array2 without duplicates. Example: array_union(array(1, 2, 2, 4), array(2, 3)) Result: [1, 2, 3, 4]</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFArrayUnion.java>GenericUDFArrayUnion</a></td>
 </tr>
 <tr>
 <td><strong>array</strong></td>
-<td><code>array\_remove(array, element)</code></td>
+<td><code>array_remove(array, element)</code></td>
 <td>NEW Removes all occurrences of elements from the array. Example: array_remove(array(1, 2, 3, 4, 2), 2) Result: [1, 3, 4]</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFArrayRemove.java>GenericUDFArrayRemove</a></td>
 </tr>
@@ -1339,7 +1339,7 @@ ASF
 </tr>
 <tr>
 <td><strong>T</strong></td>
-<td><code>nvl(T value, T default\_value)</code></td>
+<td><code>nvl(T value, T default_value)</code></td>
 <td>Returns default value if value is null else returns value.</td>
 </tr>
 <tr>
@@ -1364,7 +1364,7 @@ ASF
 </tr>
 <tr>
 <td><strong>void</strong></td>
-<td><code>assert\_true(boolean condition)</code></td>
+<td><code>assert_true(boolean condition)</code></td>
 <td>Throw an exception if &lsquo;condition&rsquo; is not true, otherwise, return null. For example, select assert_true (2&lt;1).</td>
 </tr>
 </tbody>
@@ -1389,31 +1389,31 @@ ASF
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>mask\_first\_n(string str[,int n])</code></td>
+<td><code>mask_first_n(string str[,int n])</code></td>
 <td>Returns a masked version of str with the first n values masked. Upper case letters are converted to &ldquo;X&rdquo;, lower case letters are converted to &ldquo;x&rdquo; and numbers are converted to &ldquo;n&rdquo;. For example, mask_first_n(&ldquo;1234-5678-8765-4321&rdquo;, 4) results in nnnn-5678-8765-4321.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFMaskFirstN.java>GenericUDFMaskFirstN</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>mask\_last\_n(string str[,int n])</code></td>
+<td><code>mask_last_n(string str[,int n])</code></td>
 <td>Returns a masked version of str with the last n values masked. Upper case letters are converted to &ldquo;X&rdquo;, lower case letters are converted to &ldquo;x&rdquo; and numbers are converted to &ldquo;n&rdquo;. For example, mask_last_n(&ldquo;1234-5678-8765-4321&rdquo;, 4) results in 1234-5678-8765-nnnn.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFMaskLastN.java>GenericUDFMaskLastN</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>mask\_show\_first\_n(string str[,int n])</code></td>
+<td><code>mask_show_first_n(string str[,int n])</code></td>
 <td>Returns a masked version of str, showing the first n characters unmasked. Upper case letters are converted to &ldquo;X&rdquo;, lower case letters are converted to &ldquo;x&rdquo; and numbers are converted to &ldquo;n&rdquo;. For example, mask_show_first_n(&ldquo;1234-5678-8765-4321&rdquo;, 4) results in 1234-nnnn-nnnn-nnnn.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFMaskShowFirstN.java>GenericUDFMaskShowFirstN</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>mask\_show\_last\_n(string str[,int n])</code></td>
+<td><code>mask_show_last_n(string str[,int n])</code></td>
 <td>Returns a masked version of str, showing the last n characters unmasked. Upper case letters are converted to &ldquo;X&rdquo;, lower case letters are converted to &ldquo;x&rdquo; and numbers are converted to &ldquo;n&rdquo;. For example, mask_show_last_n(&ldquo;1234-5678-8765-4321&rdquo;, 4) results in nnnn-nnnn-nnnn-4321.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFMaskShowLastN.java>GenericUDFMaskShowLastN</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>mask\_hash(string|char|varchar str)</code></td>
+<td><code>mask_hash(string|char|varchar str)</code></td>
 <td>Returns a hashed value based on str. The hash is consistent and can be used to join masked values together across tables. This function returns null for non-string types.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFMaskHash.java>GenericUDFMaskHash</a></td>
 </tr>
@@ -1433,7 +1433,7 @@ ASF
 <tbody>
 <tr>
 <td><strong>varies</strong></td>
-<td><code>java\_method(class, method[, arg1[, arg2..]])</code></td>
+<td><code>java_method(class, method[, arg1[, arg2..]])</code></td>
 <td>Synonym for <code>reflect</code>.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFReflect.java>GenericUDFReflect</a></td>
 </tr>
@@ -1451,19 +1451,19 @@ ASF
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>current\_user()</code></td>
+<td><code>current_user()</code></td>
 <td>Returns current user name from the configured authenticator manager. Could be the same as the user provided when connecting, but with some authentication managers (for example HadoopDefaultAuthenticator) it could be different.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFCurrentUser.java>GenericUDFCurrentUser</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>logged\_in\_user()</code></td>
+<td><code>logged_in_user()</code></td>
 <td>Returns the current user name from the session state. This is the username provided when connecting to Hive.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFLoggedInUser.java>GenericUDFLoggedInUser</a></td>
 </tr>
 <tr>
 <td><strong>string</strong></td>
-<td><code>current\_database()</code></td>
+<td><code>current_database()</code></td>
 <td>Returns current database name.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFCurrentDatabase.java>GenericUDFCurrentDatabase</a></td>
 </tr>
@@ -1493,13 +1493,13 @@ ASF
 </tr>
 <tr>
 <td><strong>binary</strong></td>
-<td><code>aes\_encrypt(inputstring/binary, keystring/binary)</code></td>
+<td><code>aes_encrypt(inputstring/binary, keystring/binary)</code></td>
 <td>Encrypt input using AES. Key lengths of 128, 192 or 256 bits can be used. 192 and 256 bits keys can be used if Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files are installed. If either argument is NULL or the key length is not one of the permitted values, the return value is NULL. Example: base64(aes_encrypt(&lsquo;ABC&rsquo;, &lsquo;1234567890123456&rsquo;)) = &lsquo;y6Ss+zCYObpCbgfWfyNWTw==&rsquo;.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFAesEncrypt.java>GenericUDFAesEncrypt</a></td>
 </tr>
 <tr>
 <td><strong>binary</strong></td>
-<td><code>aes\_decrypt(input binary, keystring/binary)</code></td>
+<td><code>aes_decrypt(input binary, keystring/binary)</code></td>
 <td>Decrypt input using AES. Key lengths of 128, 192 or 256 bits can be used. 192 and 256 bits keys can be used if Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files are installed. If either argument is NULL or the key length is not one of the permitted values, the return value is NULL. Example: aes_decrypt(unbase64(&lsquo;y6Ss+zCYObpCbgfWfyNWTw=='), &lsquo;1234567890123456&rsquo;) = &lsquo;ABC&rsquo;.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFAesDecrypt.java>GenericUDFAesDecrypt</a></td>
 </tr>
@@ -1511,7 +1511,7 @@ ASF
 </tr>
 <tr>
 <td><strong>bigint</strong></td>
-<td><code>surrogate\_key([write\_id\_bits, task\_id\_bits])</code></td>
+<td><code>surrogate_key([write_id_bits, task_id_bits])</code></td>
 <td>Automatically generate numerical Ids for rows as you enter data into a table. Can only be used as the default value for acid or insert-only tables.</td>
 <td><a href=https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFSurrogateKey.java>GenericUDFSurrogateKey</a></td>
 </tr>
diff --git a/docs/latest/hiveaws-hivings3nremotely_27362102/index.html b/docs/latest/hiveaws-hivings3nremotely_27362102/index.html
index 200744e..db33bcd 100644
--- a/docs/latest/hiveaws-hivings3nremotely_27362102/index.html
+++ b/docs/latest/hiveaws-hivings3nremotely_27362102/index.html
@@ -215,12 +215,12 @@ hive&gt; set mapred.job.tracker=ec2-12-34-56-78.compute-1.amazonaws.com:50002;
 <p>Now we are all setup. The sample query from TPCH (1.sql) can be tried as follows:</p>
 <pre tabindex=0><code>
 hive&gt; insert overwrite directory '/tmp/tpcresults-1.sql' 
-  select l\_returnflag, l\_linestatus, sum ( l\_quantity ) as sum\_qty, sum ( l\_extendedprice ) as sum\_base\_price,
-  sum ( l\_extendedprice * ( 1 - l\_discount )) as sub\_disc\_price, 
-  sum ( l\_extendedprice * ( 1 - l\_discount ) * ( 1 + l\_tax )) as sum\_charge,
-  avg ( l\_quantity ) as avg\_qty, avg ( l\_extendedprice ) as avg\_price, 
-  avg ( l\_discount ) as avg\_disc, count ( 1 ) as count\_order
-  from lineitem where l\_shipdate &lt;= to\_date('1998-12-01') group by l\_returnflag, l\_linestatus; 
+  select l_returnflag, l_linestatus, sum ( l_quantity ) as sum_qty, sum ( l_extendedprice ) as sum_base_price,
+  sum ( l_extendedprice * ( 1 - l_discount )) as sub_disc_price, 
+  sum ( l_extendedprice * ( 1 - l_discount ) * ( 1 + l_tax )) as sum_charge,
+  avg ( l_quantity ) as avg_qty, avg ( l_extendedprice ) as avg_price, 
+  avg ( l_discount ) as avg_disc, count ( 1 ) as count_order
+  from lineitem where l_shipdate &lt;= to_date('1998-12-01') group by l_returnflag, l_linestatus; 
 
 </code></pre><p>This launches one map-reduce job and on 10 nodes with default hadoop/hive settings - this took about 10 minutes. The results in this case are stored in HDFS and can be obtained by doing a <code>dfs -cat /tmp/tpcresults/1-2.sql/*</code> - either from bin/hadoop or from hive CLI. The query above differs from the TPCH query in skipping the order by clause - since it&rsquo;s not implemented by Hive currently.</p>
 <h2 id=storing-results-back-in-s3>Storing results back in S3</h2>
@@ -238,10 +238,10 @@ hive&gt; insert overwrite table t1 select ...;
 <h2 id=using-tmp-tables-in-hdfs>Using tmp tables in HDFS</h2>
 <p>Currently, Hive does not have any explicit support tmp tables. But tables defined over HDFS in EC2 are like tmp tables since they only last for the duration of the Hadoop cluster. Since they are likely to be much faster than accessing S3 directly - they can be used to stage data that may be accessed repeatedly during a session. For example - for the TPCH dataset - one may want to do some analysis of customer attributes against order details - and it would be first beneficial to materi [...]
 <pre tabindex=0><code>
-hive&gt; create table cust\_order (nationkey string, acctbal double, mktsegment string, orderstatus string, totalprice double);
-hive&gt; from customer c left outer join orders o on (c.c\_custkey = o.o\_custkey)
-  insert overwrite table cust\_order
-  select c.c\_nationkey, c.c\_acctbal, c.c\_mktsegment, o.o\_orderstatus, o.o\_totalprice;
+hive&gt; create table cust_order (nationkey string, acctbal double, mktsegment string, orderstatus string, totalprice double);
+hive&gt; from customer c left outer join orders o on (c.c_custkey = o.o_custkey)
+  insert overwrite table cust_order
+  select c.c_nationkey, c.c_acctbal, c.c_mktsegment, o.o_orderstatus, o.o_totalprice;
 
 </code></pre><h2 id=appendix>Appendix</h2>
 <p>&#171;Anchor(ConfigHell)&#187;</p>
diff --git a/docs/latest/hiveclient_27362101/index.html b/docs/latest/hiveclient_27362101/index.html
index 2cd20e1..92a7623 100644
--- a/docs/latest/hiveclient_27362101/index.html
+++ b/docs/latest/hiveclient_27362101/index.html
@@ -218,10 +218,10 @@ $ javac HiveJdbcClient.java
 
 # To run the program in standalone mode, we need the following jars in the classpath
 # from hive/build/dist/lib
-#     hive\_exec.jar
-#     hive\_jdbc.jar
-#     hive\_metastore.jar
-#     hive\_service.jar
+#     hive_exec.jar
+#     hive_jdbc.jar
+#     hive_metastore.jar
+#     hive_service.jar
 #     libfb303.jar
 #     log4j-1.2.15.jar
 #
@@ -244,16 +244,16 @@ $ java -cp $CLASSPATH HiveJdbcClient
 # and build your classpath before invoking the client.
 
 #!/bin/bash
-HADOOP\_HOME=/your/path/to/hadoop
-HIVE\_HOME=/your/path/to/hive
+HADOOP_HOME=/your/path/to/hadoop
+HIVE_HOME=/your/path/to/hive
 
 echo -e '1\x01foo' &gt; /tmp/a.txt
 echo -e '2\x01bar' &gt;&gt; /tmp/a.txt
 
-HADOOP\_CORE={{ls $HADOOP\_HOME/hadoop-*-core.jar}}
-CLASSPATH=.:$HADOOP\_CORE:$HIVE\_HOME/conf
+HADOOP_CORE={{ls $HADOOP_HOME/hadoop-*-core.jar}}
+CLASSPATH=.:$HADOOP_CORE:$HIVE_HOME/conf
 
-for i in ${HIVE\_HOME}/lib/*.jar ; do
+for i in ${HIVE_HOME}/lib/*.jar ; do
     CLASSPATH=$CLASSPATH:$i
 done
 
@@ -303,12 +303,12 @@ except Thrift.TException, tx:
 </code></pre><h1 id=php>PHP</h1>
 <p>Operates only on a standalone server.</p>
 <pre tabindex=0><code>&lt;?php
-// set THRIFT\_ROOT to php directory of the hive distribution
-$GLOBALS['THRIFT\_ROOT'] = '/lib/php/';
+// set THRIFT_ROOT to php directory of the hive distribution
+$GLOBALS['THRIFT_ROOT'] = '/lib/php/';
 // load the required files for connecting to Hive
-require\_once $GLOBALS['THRIFT\_ROOT'] . 'packages/hive\_service/ThriftHive.php';
-require\_once $GLOBALS['THRIFT\_ROOT'] . 'transport/TSocket.php';
-require\_once $GLOBALS['THRIFT\_ROOT'] . 'protocol/TBinaryProtocol.php';
+require_once $GLOBALS['THRIFT_ROOT'] . 'packages/hive_service/ThriftHive.php';
+require_once $GLOBALS['THRIFT_ROOT'] . 'transport/TSocket.php';
+require_once $GLOBALS['THRIFT_ROOT'] . 'protocol/TBinaryProtocol.php';
 // Set up the transport/protocol/client
 $transport = new TSocket('localhost', 10000);
 $protocol = new TBinaryProtocol($transport);
@@ -317,7 +317,7 @@ $transport-&gt;open();
 
 // run queries, metadata calls etc
 $client-&gt;execute('SELECT * from src');
-var\_dump($client-&gt;fetchAll());
+var_dump($client-&gt;fetchAll());
 $transport-&gt;close();
 
 </code></pre><h1 id=odbc>ODBC</h1>
diff --git a/docs/latest/hivederbyservermode_27362068/index.html b/docs/latest/hivederbyservermode_27362068/index.html
index a908bfe..1dfec4e 100644
--- a/docs/latest/hivederbyservermode_27362068/index.html
+++ b/docs/latest/hivederbyservermode_27362068/index.html
@@ -146,10 +146,10 @@ mkdir db-derby-10.4.1.3-bin/data
 </code></pre><h3 id=set-environment>Set Environment</h3>
 <p>The variable to set has changed over the years. DERBY_HOME is now the proper name. I set this and the legacy name.</p>
 <p><code>/etc/profile.d/derby.sh</code></p>
-<pre tabindex=0><code>DERBY\_INSTALL=/opt/hadoop/db-derby-10.4.1.3-bin
-DERBY\_HOME=/opt/hadoop/db-derby-10.4.1.3-bin
-export DERBY\_INSTALL
-export DERBY\_HOME
+<pre tabindex=0><code>DERBY_INSTALL=/opt/hadoop/db-derby-10.4.1.3-bin
+DERBY_HOME=/opt/hadoop/db-derby-10.4.1.3-bin
+export DERBY_INSTALL
+export DERBY_HOME
 
 </code></pre><p>Hive also likes to know where Hadoop is installed:</p>
 <p><code>/etc/profile.d/hive.sh</code></p>
@@ -170,7 +170,7 @@ nohup /opt/hadoop/db-derby-10.4.1.3-bin/startNetworkServer -h 0.0.0.0 &amp;
 <p><code>/opt/hadoop/hive/conf/hive-site.xml</code></p>
 <pre tabindex=0><code>&lt;property&gt;
   &lt;name&gt;javax.jdo.option.ConnectionURL&lt;/name&gt;
-  &lt;value&gt;jdbc:derby://hadoop1:1527/metastore\_db;create=true&lt;/value&gt;
+  &lt;value&gt;jdbc:derby://hadoop1:1527/metastore_db;create=true&lt;/value&gt;
   &lt;description&gt;JDBC connect string for a JDBC metastore&lt;/description&gt;
 &lt;/property&gt;
 
@@ -191,11 +191,11 @@ org.jpox.validateConstraints=false
 org.jpox.storeManagerType=rdbms
 org.jpox.autoCreateSchema=true
 org.jpox.autoStartMechanismMode=checked
-org.jpox.transactionIsolation=read\_committed
+org.jpox.transactionIsolation=read_committed
 javax.jdo.option.DetachAllOnCommit=true
 javax.jdo.option.NontransactionalRead=true
 javax.jdo.option.ConnectionDriverName=org.apache.derby.jdbc.ClientDriver
-javax.jdo.option.ConnectionURL=jdbc:derby://hadoop1:1527/metastore\_db;create=true
+javax.jdo.option.ConnectionURL=jdbc:derby://hadoop1:1527/metastore_db;create=true
 javax.jdo.option.ConnectionUserName=APP
 javax.jdo.option.ConnectionPassword=mine
 
diff --git a/docs/latest/hivedeveloperfaq_27823747/index.html b/docs/latest/hivedeveloperfaq_27823747/index.html
index ba902de..da6232e 100644
--- a/docs/latest/hivedeveloperfaq_27823747/index.html
+++ b/docs/latest/hivedeveloperfaq_27823747/index.html
@@ -312,30 +312,30 @@ mvn test -Dtest=TestCliDriver
 mvn test -Dtest=TestNegativeCliDriver -Dqfile=alter1.q 
 </code></pre><p>To run all of the clientpositive tests that match a regex, for example the partition_wise_fileformat tests</p>
 <pre tabindex=0><code>cd itests/qtest
-mvn test -Dtest=TestCliDriver -Dqfile\_regex=partition\_wise\_fileformat.* 
+mvn test -Dtest=TestCliDriver -Dqfile_regex=partition_wise_fileformat.* 
 
 # Alternatively, you can specify comma separated list with &quot;-Dqfile&quot; argument
-mvn test -Dtest=TestMiniLlapLocalCliDriver -Dqfile='vectorization\_0.q,vectorization\_17.q,vectorization\_8.q'
+mvn test -Dtest=TestMiniLlapLocalCliDriver -Dqfile='vectorization_0.q,vectorization_17.q,vectorization_8.q'
 </code></pre><p>To run a single contrib test alter1.q and overwrite the result file</p>
 <pre tabindex=0><code>cd itests/qtest
 mvn test -Dtest=TestContribCliDriver -Dqfile=alter1.q -Dtest.output.overwrite=true 
 </code></pre><h3 id=how-do-i-run-with-postgremysqloracle>How do I run with Postgre/MySQL/Oracle?</h3>
 <p>To run test test with a specified DB it is possible by adding &ldquo;-Dtest.metastore.db&rdquo; parameter like in the following commands:</p>
-<pre tabindex=0><code>mvn test -Pitests -pl itests/qtest -Dtest=TestCliDriver -Dqfile=partition\_params\_postgres.q -Dtest.metastore.db=postgres
+<pre tabindex=0><code>mvn test -Pitests -pl itests/qtest -Dtest=TestCliDriver -Dqfile=partition_params_postgres.q -Dtest.metastore.db=postgres
 
-mvn test -Pitests -pl itests/qtest -Dtest=TestCliDriver -Dqfile=partition\_params\_postgres.q -Dtest.metastore.db=mssql
-mvn test -Pitests -pl itests/qtest -Dtest=TestCliDriver -Dqfile=partition\_params\_postgres.q -Dtest.metastore.db=mysql
-mvn test -Pitests -pl itests/qtest -Dtest=TestCliDriver -Dqfile=partition\_params\_postgres.q -Dtest.metastore.db=oracle -Ditest.jdbc.jars=/path/to/your/god/damn/oracle/jdbc/driver/ojdbc6.jar
+mvn test -Pitests -pl itests/qtest -Dtest=TestCliDriver -Dqfile=partition_params_postgres.q -Dtest.metastore.db=mssql
+mvn test -Pitests -pl itests/qtest -Dtest=TestCliDriver -Dqfile=partition_params_postgres.q -Dtest.metastore.db=mysql
+mvn test -Pitests -pl itests/qtest -Dtest=TestCliDriver -Dqfile=partition_params_postgres.q -Dtest.metastore.db=oracle -Ditest.jdbc.jars=/path/to/your/god/damn/oracle/jdbc/driver/ojdbc6.jar
 </code></pre><p>Without specifying -Dqfile it will run all .q files .</p>
 <h3 id=how-do-i-remote-debug-a-qtest>How do I remote debug a qtest?</h3>
 <pre tabindex=0><code>cd itests/qtest
-mvn -Dmaven.surefire.debug=&quot;-Xdebug -Xrunjdwp:transport=dt\_socket,server=y,suspend=y,address=8000 -Xnoagent -Djava.compiler=NONE&quot; test -Dtest=TestCliDriver -Dqfile=&lt;test&gt;.q
+mvn -Dmaven.surefire.debug=&quot;-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000 -Xnoagent -Djava.compiler=NONE&quot; test -Dtest=TestCliDriver -Dqfile=&lt;test&gt;.q
 </code></pre><h3 id=how-do-i-modify-the-init-script-when-testing>How do I modify the init script when testing?</h3>
 <p>The option to skip the init script or supply a custom init script was added in Hive 2.0 (see <a href=https://issues.apache.org/jira/browse/HIVE-11538>HIVE-11538</a>).</p>
 <p>To skip initialization:</p>
-<pre tabindex=0><code>mvn test -Dtest=TestCliDriver -Phadoop-2 -Dqfile=test\_to\_run.q  -DinitScript=
+<pre tabindex=0><code>mvn test -Dtest=TestCliDriver -Phadoop-2 -Dqfile=test_to_run.q  -DinitScript=
 </code></pre><p>To supply a custom script:</p>
-<pre tabindex=0><code>mvn test -Dtest=TestCliDriver -Phadoop-2 -Dtest.output.overwrite=true -Dqfile=test\_to\_run.q  -DinitScript=custom\_script.sql
+<pre tabindex=0><code>mvn test -Dtest=TestCliDriver -Phadoop-2 -Dtest.output.overwrite=true -Dqfile=test_to_run.q  -DinitScript=custom_script.sql
 </code></pre><h3 id=how-do-i-update-the-output-of-a-clidriver-testcase>How do I update the output of a CliDriver testcase?</h3>
 <pre tabindex=0><code>cd itests/qtest
 mvn test -Dtest=TestCliDriver -Dqfile=alter1.q -Dtest.output.overwrite=true 
@@ -343,17 +343,17 @@ mvn test -Dtest=TestCliDriver -Dqfile=alter1.q -Dtest.output.overwrite=true
 </code></pre><h3 id=how-do-i-update-the-results-of-many-test-cases>How do I update the results of many test cases?</h3>
 <p>Assume that you have a file like below which you&rsquo;d like to re-generate output files for. Such a file could be created by copying the output from the precommit tests.</p>
 <pre tabindex=0><code>head -2 /tmp/failed-TestCliDriver-file-tests
-org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver\_allcolref\_in\_udf
-org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver\_annotate\_stats\_join
+org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_allcolref_in_udf
+org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_annotate_stats_join
 </code></pre><p>You can re-generate all those output files in batches of 20 with the command below</p>
-<pre tabindex=0><code>egrep 'TestCliDriver' /tmp/failed-TestCliDriver-file-tests | perl -pe 's@.*testCliDriver\_@@g' | awk '{print $1 &quot;.q&quot;}' | xargs -n 30 | perl -pe 's@ @,@g' | xargs -I{} mvn test -Dtest=TestCliDriver -Dtest.output.overwrite=true -Dqfile={}
+<pre tabindex=0><code>egrep 'TestCliDriver' /tmp/failed-TestCliDriver-file-tests | perl -pe 's@.*testCliDriver_@@g' | awk '{print $1 &quot;.q&quot;}' | xargs -n 30 | perl -pe 's@ @,@g' | xargs -I{} mvn test -Dtest=TestCliDriver -Dtest.output.overwrite=true -Dqfile={}
 </code></pre><p>To do the same from the output of a precommit result, with multiple drivers, you can do</p>
 <pre tabindex=0><code>import re
 from itertools import groupby
 s = &quot;&quot;&quot;
-org.apache.hadoop.hive.cli.TestBeeLineDriver.testCliDriver[drop\_with\_concurrency] (batchId=231)
+org.apache.hadoop.hive.cli.TestBeeLineDriver.testCliDriver[drop_with_concurrency] (batchId=231)
 org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[comments] (batchId=35)
-org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vector\_if\_expr] (batchId=141)
+org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vector_if_expr] (batchId=141)
 &quot;&quot;&quot;
 PAT = re.compile(&quot;org.apache.hadoop.hive.cli.([^\.]*).*\[([^\]]*).*&quot;)
 l = [PAT.match(x.strip()) for x in s.split(&quot;\n&quot;) if x.strip()]
@@ -426,15 +426,15 @@ java.lang.SecurityException: class &quot;javax.servlet.FilterRegistration&quot;'
 <h3 id=how-do-i-debug-into-asingle-testin-eclipse>How do I debug into a single test in Eclipse?</h3>
 <p>You can debug into a single JUnit test in <a href=https://www.eclipse.org/users/>Eclipse</a> by first making sure you&rsquo;ve built the Eclipse files and imported the project into Eclipse as described <a href=#here>here</a>. Then set one or more breakpoints, highlight the method name of the JUnit test method you want to debug into, and do <code>Run->Debug</code>.</p>
 <p>Another useful method to debug these tests is to attach a remote debugger. When you run the test, enable the debug mode for surefire by passing in &ldquo;<code>-Dmaven.surefire.debug</code>&rdquo;. Additional details on how to turning on debugging for surefire can be found <a href=http://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html>here</a>. Now when you run the tests, it will wait with a message similar to</p>
-<pre tabindex=0><code>Listening for transport dt\_socket at address: 5005
+<pre tabindex=0><code>Listening for transport dt_socket at address: 5005
 </code></pre><p>Note that this assumes that you are still using the default port 5005 for surefire. Otherwise you might see a different port. Once you see this message, in Eclipse right click on the project you want to debug, go to &ldquo;Debug As -> Debug Configurations -> Remote Java Application&rdquo; and hit the &ldquo;+&rdquo; sign on far left top. This should bring up a dialog box. Make sure that the host is &ldquo;localhost&rdquo; and the port is &ldquo;5005&rdquo;. Before you sta [...]
 <h3 id=how-do-i-debug-my-queries-in-hive>How do I debug my queries in Hive?</h3>
 <p>You can also interactively debug your queries in Hive by attaching a remote debugger. To do so, start <a href=#beeline>Beeline</a> with the &ldquo;<code>--debug</code>&rdquo; option.</p>
 <pre tabindex=0><code>$ beeline --debug
-Listening for transport dt\_socket at address: 8000
+Listening for transport dt_socket at address: 8000
 </code></pre><p>Once you see this message, in Eclipse right click on the project you want to debug, go to &ldquo;Debug As -> Debug Configurations -> Remote Java Application&rdquo; and hit the &ldquo;+&rdquo; sign on far left top. This should bring up a dialog box. Make sure that the host is the host on which the Beeline CLI is running and the port is &ldquo;8000&rdquo;. Before you start debugging, make sure that you have set appropriate debug breakpoints in the code. Once ready, hit &ldq [...]
 <pre tabindex=0><code>$ beeline --debug
-Listening for transport dt\_socket at address: 8000
+Listening for transport dt_socket at address: 8000
 Beeline version 1.2.0 by Apache Hive
 beeline&gt;
 </code></pre><p>At this point, run your queries as normal and it should stop at the breakpoints that you set so that you can start debugging.</p>
diff --git a/docs/latest/hivejdbcinterface_27362100/index.html b/docs/latest/hivejdbcinterface_27362100/index.html
index 91cdd5a..0fe180f 100644
--- a/docs/latest/hivejdbcinterface_27362100/index.html
+++ b/docs/latest/hivejdbcinterface_27362100/index.html
@@ -133,10 +133,10 @@ ASF
 </ol>
 <pre tabindex=0><code>#!/bin/sh
 
-HADOOP\_CORE={{ls $HADOOP\_HOME/hadoop-*-core.jar}}
-CLASSPATH=.:$HADOOP\_CORE:$HIVE\_HOME/conf
+HADOOP_CORE={{ls $HADOOP_HOME/hadoop-*-core.jar}}
+CLASSPATH=.:$HADOOP_CORE:$HIVE_HOME/conf
 
-for i in ${HIVE\_HOME}/lib/*.jar ; do
+for i in ${HIVE_HOME}/lib/*.jar ; do
   CLASSPATH=$CLASSPATH:$i
 done
 
@@ -188,8 +188,8 @@ java -XX:MaxPermSize=512m -cp $CLASSPATH org.pentaho.commons.launcher.Launcher
 <p>Select &lsquo;Extra Class Path -> Add&rsquo; to add the following jars from your local Hive and Hadoop distribution.</p>
 </li>
 </ol>
-<pre tabindex=0><code>   HIVE\_HOME/build/dist/lib/*.jar
-   HADOOP\_HOME/hadoop-*-core.jar
+<pre tabindex=0><code>   HIVE_HOME/build/dist/lib/*.jar
+   HADOOP_HOME/hadoop-*-core.jar
 </code></pre><ol start=4>
 <li>Select &lsquo;List Drivers&rsquo;. This will cause SQuirrel to parse your jars for JDBC drivers and might take a few seconds. From the &lsquo;Class Name&rsquo; input box select the Hive driver:</li>
 </ol>
diff --git a/docs/latest/hiveodbc_27362099/index.html b/docs/latest/hiveodbc_27362099/index.html
index 6e179de..b3ecb8b 100644
--- a/docs/latest/hiveodbc_27362099/index.html
+++ b/docs/latest/hiveodbc_27362099/index.html
@@ -178,19 +178,19 @@ There is no ODBC driver available for <a href=https://hive.apache.org/docs/lates
 <p>The ODBC driver is broken on trunk!</p>
 <p>Currently the C++ Thrift client library that the ODBC driver depends on will not build on trunk. This issue is being tracked in <a href=https://issues.apache.org/jira/browse/HIVE-4433>HIVE-4433</a>. If you are using trunk prior to release 0.12 check the status of this ticket before proceeding. Also see <a href=https://issues.apache.org/jira/browse/HIVE-4492>HIVE-4492</a>.
 2. Build the Hive client by running the following command from HIVE_SRC_ROOT. This will compile and copy the libraries and header files to <code>HIVE_SRC_ROOT/build/odbc/</code>. Please keep in mind that all paths should be fully specified (no relative paths). If you encounter an &ldquo;<code>undefined reference to vtables</code>&rdquo; error, make sure that you have specified the absolute path for thrift.home.</p>
-<pre tabindex=0><code> $ ant compile-cpp -Dthrift.home=&lt;THRIFT\_HOME&gt;
+<pre tabindex=0><code> $ ant compile-cpp -Dthrift.home=&lt;THRIFT_HOME&gt;
  
 </code></pre><p>MVN:</p>
 <pre tabindex=0><code>$ cd odbc
 $ mvn compile -Podbc,hadoop-1 -Dthrift.home=/usr/local -Dboost.home=/usr/local
  
 </code></pre><p>You can optionally force Hive client to compile into a non-native bit architecture by specifying the additional parameter (assuming you have the proper compilation libraries):</p>
-<pre tabindex=0><code> $ ant compile-cpp -Dthrift.home=&lt;THRIFT\_HOME&gt; -Dword.size=&lt;32 or 64&gt;
+<pre tabindex=0><code> $ ant compile-cpp -Dthrift.home=&lt;THRIFT_HOME&gt; -Dword.size=&lt;32 or 64&gt;
  
 </code></pre><ol>
 <li>You can verify the entire Hive compilation by running the Hive test suite from HIVE_SRC_ROOT. Specifying the argument &lsquo;-Dthrift.home=&lt;THRIFT_HOME>&rsquo; will enable the tests for the Hive client. If you do NOT specify thrift.home, the Hive client tests will not be run and will just return successful.</li>
 </ol>
-<pre tabindex=0><code> $ ant test -Dthrift.home=&lt;THRIFT\_HOME&gt;
+<pre tabindex=0><code> $ ant test -Dthrift.home=&lt;THRIFT_HOME&gt;
  
 </code></pre><p>MVN:</p>
 <pre tabindex=0><code>$ cd odbc
@@ -198,7 +198,7 @@ $ mvn test -Podbc,hadoop-1 -Dthrift.home=/usr/local -Dboost.home=/usr/local
  
 </code></pre><p>You can specifically execute the Hive client tests by running the above command from <code>HIVE_SRC_ROOT/odbc/</code>. NOTE: Hive client tests require that a local Hive Server be operating on port 10000.
 2. To install the Hive client libraries onto your machine, run the following command from <code>HIVE_SRC_ROOT/odbc/</code>. NOTE: The install path defaults to <code>/usr/local</code>. While there is no current way to change this default directory from the ant build process, a manual install may be performed by skipping the command below and copying out the contents of <code>HIVE_SRC_ROOT/build/odbc/lib</code> and <code>HIVE_SRC_ROOT/build/odbc/include</code> into their local file system  [...]
-<pre tabindex=0><code> $ sudo ant install -Dthrift.home=&lt;THRIFT\_HOME&gt;
+<pre tabindex=0><code> $ sudo ant install -Dthrift.home=&lt;THRIFT_HOME&gt;
  
 </code></pre><p>NOTE: The compiled static library, libhiveclient.a, requires linking with stdc++ as well as thrift libraries to function properly.<br>
 NOTE: Currently, there is no way to specify non-system library and header directories to the unixODBC build process. Thus, the Hive client libraries and headers MUST be installed to a default system location in order for the unixODBC build process to detect these files. This issue may be remedied in the future.</p>
@@ -207,13 +207,13 @@ NOTE: Currently, there is no way to specify non-system library and header direct
 <ol>
 <li>In the unixODBC root directory, run the following command:</li>
 </ol>
-<pre tabindex=0><code> $ ./configure --enable-gui=no --prefix=&lt;unixODBC\_INSTALL\_DIR&gt;
+<pre tabindex=0><code> $ ./configure --enable-gui=no --prefix=&lt;unixODBC_INSTALL_DIR&gt;
  
 </code></pre><p>If you encounter the the errors: &ldquo;<code>redefinition of 'struct _hist_entry'</code>&rdquo; or &ldquo;<code>previous declaration of 'add_history' was here</code>&rdquo; then re-execute the configure with the following command:</p>
-<pre tabindex=0><code> $ ./configure --enable-gui=no --enable-readline=no --prefix=&lt;unixODBC\_INSTALL\_DIR&gt;
+<pre tabindex=0><code> $ ./configure --enable-gui=no --enable-readline=no --prefix=&lt;unixODBC_INSTALL_DIR&gt;
  
 </code></pre><p>To force the compilation of the unixODBC API wrapper into a non-native bit architecture, modify the CC and CXX environment variables to include the appropriate flags. For example:</p>
-<pre tabindex=0><code> $ CC=&quot;gcc -m32&quot; CXX=&quot;g++ -m32&quot; ./configure --enable-gui=no --enable-readline=no --prefix=&lt;unixODBC\_INSTALL\_DIR&gt;
+<pre tabindex=0><code> $ CC=&quot;gcc -m32&quot; CXX=&quot;g++ -m32&quot; ./configure --enable-gui=no --enable-readline=no --prefix=&lt;unixODBC_INSTALL_DIR&gt;
  
 </code></pre><ol start=2>
 <li>Compile the unixODBC API wrapper with the following:</li>
@@ -228,8 +228,8 @@ If you only want to obtain the Hive ODBC driver shared object library:
 3. After compilation, the driver will be located at <code>&lt;unixODBC_BUILD_DIR>/Drivers/hive/.libs/libodbchive.so.1.0.0</code>.<br>
 This may be copied to any other location as desired. Keep in mind that the Hive ODBC driver has a dependency on the Hive client shared object library: <code>libhiveclient.so</code> and <code>libthrift.so.0</code>.<br>
 You can manually install the unixODBC API wrapper by doing the following:</p>
-<pre tabindex=0><code>  $ cp &lt;unixODBC\_BUILD\_DIR&gt;/Drivers/hive/.libs/libodbchive.so.1.0.0 &lt;SYSTEM\_INSTALL\_DIR&gt;
-  $ cd &lt;SYSTEM\_INSTALL\_DIR&gt;
+<pre tabindex=0><code>  $ cp &lt;unixODBC_BUILD_DIR&gt;/Drivers/hive/.libs/libodbchive.so.1.0.0 &lt;SYSTEM_INSTALL_DIR&gt;
+  $ cd &lt;SYSTEM_INSTALL_DIR&gt;
   $ ln -s libodbchive.so.1.0.0 libodbchive.so
   $ ldconfig
   
@@ -261,11 +261,11 @@ You can manually install the unixODBC API wrapper by doing the following:</p>
 </li>
 </ol>
 <pre tabindex=0><code> [Hive]
- Driver = &lt;path\_to\_libodbchive.so&gt;
+ Driver = &lt;path_to_libodbchive.so&gt;
  Description = Hive Driver v1
  DATABASE = default
- HOST = &lt;Hive\_server\_address&gt;
- PORT = &lt;Hive\_server\_port&gt;
+ HOST = &lt;Hive_server_address&gt;
+ PORT = &lt;Hive_server_port&gt;
  FRAMED = 0
  
 </code></pre><h3 id=testing-with-isql>Testing with ISQL</h3>
diff --git a/docs/latest/hiveplugins_27362098/index.html b/docs/latest/hiveplugins_27362098/index.html
index 44516e7..0353ee7 100644
--- a/docs/latest/hiveplugins_27362098/index.html
+++ b/docs/latest/hiveplugins_27362098/index.html
@@ -136,33 +136,33 @@ public final class Lower extends UDF {
 </code></pre><p>(Note that there&rsquo;s already a built-in function for this, it&rsquo;s just an easy example).</p>
 <p>After compiling your code to a jar, you need to add this to the Hive classpath. See the section below on deploying jars.</p>
 <p>Once Hive is started up with your jars in the classpath, the final step is to register your function as described in <a href=#create-function>Create Function</a>:</p>
-<pre tabindex=0><code>create temporary function my\_lower as 'com.example.hive.udf.Lower';
+<pre tabindex=0><code>create temporary function my_lower as 'com.example.hive.udf.Lower';
 
 </code></pre><p>Now you can start using it:</p>
-<pre tabindex=0><code>hive&gt; select my\_lower(title), sum(freq) from titles group by my\_lower(title);
+<pre tabindex=0><code>hive&gt; select my_lower(title), sum(freq) from titles group by my_lower(title);
 
 ...
 
-Ended Job = job\_200906231019\_0006
+Ended Job = job_200906231019_0006
 OK
 cmo	13.0
 vp	7.0
 
 </code></pre><p>For a more involved example, see <a href=https://hive.apache.org/docs/latest/genericudafcasestudy_27362093/>this page</a>.</p>
 <p>As of <a href=https://issues.apache.org/jira/browse/HIVE-6047>Hive 0.13</a>, you can register your function as a permanent UDF either in the current database or in a specified database, as described in <a href=#permanent-functions>Permanent Functions</a>. For example:</p>
-<pre tabindex=0><code>create function my\_db.my\_lower as 'com.example.hive.udf.Lower';
+<pre tabindex=0><code>create function my_db.my_lower as 'com.example.hive.udf.Lower';
 </code></pre><h2 id=deploying-jars-for-user-defined-functions-and-user-defined-serdes>Deploying Jars for User Defined Functions and User Defined SerDes</h2>
 <p>In order to start using your UDF, you first need to add the code to the classpath:</p>
-<pre tabindex=0><code>hive&gt; add jar my\_jar.jar;
-Added my\_jar.jar to class path
+<pre tabindex=0><code>hive&gt; add jar my_jar.jar;
+Added my_jar.jar to class path
 
 </code></pre><p>By default, it will look in the current directory. You can also specify a full path:</p>
-<pre tabindex=0><code>hive&gt; add jar /tmp/my\_jar.jar;
-Added /tmp/my\_jar.jar to class path
+<pre tabindex=0><code>hive&gt; add jar /tmp/my_jar.jar;
+Added /tmp/my_jar.jar to class path
 
 </code></pre><p>Your jar will then be on the classpath for all jobs initiated from that session. To see which jars have been added to the classpath you can use:</p>
 <pre tabindex=0><code>hive&gt; list jars;
-my\_jar.jar
+my_jar.jar
 
 </code></pre><p>See <a href=#hive-cli>Hive CLI</a> for full syntax and more examples.</p>
 <p>As of <a href=https://issues.apache.org/jira/browse/HIVE-6380>Hive 0.13</a>, UDFs also have the option of being able to specify required jars in the <a href=#create-function>CREATE FUNCTION</a> statement:</p>
diff --git a/docs/latest/hivereplicationv2development_66850051/index.html b/docs/latest/hivereplicationv2development_66850051/index.html
index e0a8077..ef40806 100644
--- a/docs/latest/hivereplicationv2development_66850051/index.html
+++ b/docs/latest/hivereplicationv2development_66850051/index.html
@@ -285,8 +285,8 @@ Event 120: ALTER TABLE tbl ADD PARTITION (p=1) SET LOCATION &lt;location&gt;;
 <p>The current implementation of replication is built upon existing commands EXPORT and IMPORT. These commands are semantically more suited to the task of exporting and importing, than of a direct notion of an applicable event log. The notion of a lazy _files behaviour on EXPORT is not a good fit, since EXPORTs are done with the understanding that they need to be a stable copy irrespective of cleanup policies on the source. In addition, EXPORTing &ldquo;events&rdquo; is something that is [...]
 <h2 id=repl-dump>REPL DUMP</h2>
 <h4 id=syntax>Syntax:</h4>
-<p><code>REPL DUMP &lt;repl\_policy> {REPLACE &lt;old\_repl\_policy>} {FROM &lt;init-evid> {TO &lt;end-evid>} {LIMIT &lt;num-evids>} } {WITH ('key1'='value1', 'key2'='value2')};</code></p>
-<p><code>Replication policy: &lt;dbname>{{.[&lt;comma\_separated\_include\_tables\_regex\_list>]}{.[&lt;comma\_separated\_exclude\_tables\_regex\_list>]}}</code></p>
+<p><code>REPL DUMP &lt;repl_policy> {REPLACE &lt;old_repl_policy>} {FROM &lt;init-evid> {TO &lt;end-evid>} {LIMIT &lt;num-evids>} } {WITH ('key1'='value1', 'key2'='value2')};</code></p>
+<p><code>Replication policy: &lt;dbname>{{.[&lt;comma_separated_include_tables_regex_list>]}{.[&lt;comma_separated_exclude_tables_regex_list>]}}</code></p>
 <p>This is better described via various examples of each of the pieces of the command syntax, as follows:</p>
 <p>(a) REPL DUMP sales;       REPL DUMP sales.['.*?']Replicates out sales database for bootstrap, from =0 (bootstrap case) to = with a batch size of 0, i.e. no batching.</p>
 <p>(b) REPL DUMP sales.[&lsquo;T3&rsquo;, &lsquo;[a-z]+'];</p>
diff --git a/docs/latest/hiveserver2-clients_30758725/index.html b/docs/latest/hiveserver2-clients_30758725/index.html
index ce4e70b..4d462bb 100644
--- a/docs/latest/hiveserver2-clients_30758725/index.html
+++ b/docs/latest/hiveserver2-clients_30758725/index.html
@@ -217,18 +217,18 @@ beeline&gt; !connect jdbc:hive2://localhost:10000 scott tiger
 Connecting to jdbc:hive2://localhost:10000
 Connected to: Hive (version 0.10.0)
 Driver: Hive (version 0.10.0-SNAPSHOT)
-Transaction isolation: TRANSACTION\_REPEATABLE\_READ
+Transaction isolation: TRANSACTION_REPEATABLE_READ
 0: jdbc:hive2://localhost:10000&gt; show tables;
 show tables;
 +-------------------+
-|     tab\_name      |
+|     tab_name      |
 +-------------------+
 | primitives        |
 | src               |
 | src1              |
-| src\_json          |
-| src\_sequencefile  |
-| src\_thrift        |
+| src_json          |
+| src_sequencefile  |
+| src_thrift        |
 | srcbucket         |
 | srcbucket2        |
 | srcpart           |
@@ -236,7 +236,7 @@ show tables;
 9 rows selected (1.079 seconds)
 
 </code></pre><p>You can also specify the connection parameters on command line. This means you can find the command with the connection string from your UNIX shell history. </p>
-<pre tabindex=0><code>% beeline -u jdbc:hive2://localhost:10000/default -n scott -w password\_file
+<pre tabindex=0><code>% beeline -u jdbc:hive2://localhost:10000/default -n scott -w password_file
 Hive version 0.11.0-SNAPSHOT by Apache
 
 Connecting to jdbc:hive2://localhost:10000/default
@@ -492,7 +492,7 @@ beeline&gt; !connect jdbc:hive2://&lt;host&gt;:&lt;port&gt;/&lt;db&gt;;auth=noS
 </tr>
 <tr>
 <td>**&ndash;isolation=**LEVEL</td>
-<td>Set the transaction isolation level to TRANSACTION_READ_COMMITTED or TRANSACTION_SERIALIZABLE. See the &ldquo;Field Detail&rdquo; section in the Java <a href=http://docs.oracle.com/javase/7/docs/api/java/sql/Connection.html>Connection</a> documentation.Usage: <code>beeline --isolation=TRANSACTION\_SERIALIZABLE</code></td>
+<td>Set the transaction isolation level to TRANSACTION_READ_COMMITTED or TRANSACTION_SERIALIZABLE. See the &ldquo;Field Detail&rdquo; section in the Java <a href=http://docs.oracle.com/javase/7/docs/api/java/sql/Connection.html>Connection</a> documentation.Usage: <code>beeline --isolation=TRANSACTION_SERIALIZABLE</code></td>
 </tr>
 <tr>
 <td><strong>&ndash;nullemptystring=</strong>[true/false]</td>
@@ -673,7 +673,7 @@ Please be aware that these output formats are deprecated and only maintained for
 <p>Beeline can be run disconnected from a terminal for batch processing and automation scripts using commands such as <em>nohup</em> and <em>disown</em>.</p>
 <p>Some versions of Beeline client may require a workaround to allow the <em>nohup</em> command to correctly put the Beeline process in the background without stopping it.  See <a href=https://issues.apache.org/jira/browse/HIVE-11717>HIVE-11717</a>, <a href=https://issues.apache.org/jira/browse/HIVE-6758>H</a><a href=https://issues.apache.org/jira/browse/HIVE-6758>IVE-6758</a>.</p>
 <p>The following environment variable can be updated:</p>
-<pre tabindex=0><code>export HADOOP\_CLIENT\_OPTS=&quot;$HADOOP\_CLIENT\_OPTS -Djline.terminal=jline.UnsupportedTerminal&quot;
+<pre tabindex=0><code>export HADOOP_CLIENT_OPTS=&quot;$HADOOP_CLIENT_OPTS -Djline.terminal=jline.UnsupportedTerminal&quot;
 </code></pre><p>Running with nohangup (nohup) and ampersand (&) will place the process in the background and allow the terminal to disconnect while keeping the Beeline process running.  </p>
 <pre tabindex=0><code>nohup beeline --silent=true --showHeader=true --outputformat=dsv -f query.hql &lt;/dev/null &gt; /tmp/output.log 2&gt; /tmp/error.log &amp;
 </code></pre><h1 id=jdbc>JDBC</h1>
@@ -966,23 +966,23 @@ $ javac HiveJdbcClient.java
 #     jpox-rdbms-1.2.2.jar
 # and from hadoop/build
 #     hadoop-core*.jar
-# as well as hive/build/dist/conf, any HIVE\_AUX\_JARS\_PATH set, 
+# as well as hive/build/dist/conf, any HIVE_AUX_JARS_PATH set, 
 # and hadoop jars necessary to run MR jobs (eg lzo codec)
 
 $ java -cp $CLASSPATH HiveJdbcClient
 
 </code></pre><p>Alternatively, you can run the following bash script, which will seed the data file and build your classpath before invoking the client. The script adds all the additional jars needed for using HiveServer2 in embedded mode as well.</p>
 <pre tabindex=0><code>#!/bin/bash
-HADOOP\_HOME=/your/path/to/hadoop
-HIVE\_HOME=/your/path/to/hive
+HADOOP_HOME=/your/path/to/hadoop
+HIVE_HOME=/your/path/to/hive
 
 echo -e '1\x01foo' &gt; /tmp/a.txt
 echo -e '2\x01bar' &gt;&gt; /tmp/a.txt
 
-HADOOP\_CORE=$(ls $HADOOP\_HOME/hadoop-core*.jar)
-CLASSPATH=.:$HIVE\_HOME/conf:$(hadoop classpath)
+HADOOP_CORE=$(ls $HADOOP_HOME/hadoop-core*.jar)
+CLASSPATH=.:$HIVE_HOME/conf:$(hadoop classpath)
 
-for i in ${HIVE\_HOME}/lib/*.jar ; do
+for i in ${HIVE_HOME}/lib/*.jar ; do
     CLASSPATH=$CLASSPATH:$i
 done
 
@@ -1111,12 +1111,12 @@ See examples in <a href=https://github.com/apache/hive/blob/master/beeline/src/
                public Object run()
                {
                        Connection con = null;
-                       String JDBC\_DB\_URL = &quot;jdbc:hive2://HiveHost:10000/default;&quot; ||
+                       String JDBC_DB_URL = &quot;jdbc:hive2://HiveHost:10000/default;&quot; ||
                                               &quot;principal=hive/localhost.localdomain@EXAMPLE.COM;&quot; || 
                                               &quot;kerberosAuthType=fromSubject&quot;;
                        try {
-                               Class.forName(JDBC\_DRIVER);
-                               con =  DriverManager.getConnection(JDBC\_DB\_URL);
+                               Class.forName(JDBC_DRIVER);
+                               con =  DriverManager.getConnection(JDBC_DB_URL);
                        } catch (SQLException e) {
                                e.printStackTrace();
                        } catch (ClassNotFoundException e) {
@@ -1168,8 +1168,8 @@ See examples in <a href=https://github.com/apache/hive/blob/master/beeline/src/
 <p>Select &lsquo;Extra Class Path -> Add&rsquo; to add the following jars from your local Hive and Hadoop distribution.</p>
 </li>
 </ol>
-<pre tabindex=0><code>   HIVE\_HOME/lib/hive-jdbc-*-standalone.jar
-   HADOOP\_HOME/share/hadoop/common/hadoop-common-*.jar 
+<pre tabindex=0><code>   HIVE_HOME/lib/hive-jdbc-*-standalone.jar
+   HADOOP_HOME/share/hadoop/common/hadoop-common-*.jar 
 </code></pre><p>Version information</p>
 <p>Hive JDBC standalone jars are used in Hive 0.14.0 onward (<a href=https://issues.apache.org/jira/browse/HIVE-538>HIVE-538</a>); for previous versions of Hive, use <code>HIVE_HOME/build/dist/lib/*.jar</code> instead.</p>
 <p>The hadoop-common jars are for Hadoop 2.0; for previous versions of Hadoop, use <code>HADOOP_HOME/hadoop-*-core.jar</code> instead.
@@ -1235,7 +1235,7 @@ See examples in <a href=https://github.com/apache/hive/blob/master/beeline/src/
 <p>This option is available starting in <a href=https://issues.apache.org/jira/browse/HIVE-10339>Hive 1.2.0</a>.</p>
 <p><a href=https://issues.apache.org/jira/browse/HIVE-10339>HIVE-10339</a> introduced an option for clients to provide custom HTTP headers that can be sent to the underlying server (Hive 1.2.0 and later).</p>
 <p>JDBC connection URL:</p>
-<p><code>jdbc:hive2://&lt;host>:&lt;port>/&lt;db>;transportMode=http;httpPath=&lt;http\_endpoint>;http.header.&lt;name1>=&lt;value1>;http.header.&lt;name2>=&lt;value2></code></p>
+<p><code>jdbc:hive2://&lt;host>:&lt;port>/&lt;db>;transportMode=http;httpPath=&lt;http_endpoint>;http.header.&lt;name1>=&lt;value1>;http.header.&lt;name2>=&lt;value2></code></p>
 <p>When the above URL is specified, Beeline will call underlying requests to add an HTTP header set to <em></em> and <em></em> and another HTTP header set to <em></em> and <em></em>. This is helpful when the end user needs to send identity in an HTTP header down to intermediate servers such as Knox via Beeline for authentication, for example <code>http.header.USERNAME=&lt;value1>;http.header.PASSWORD=&lt;value2></code>.</p>
 <p>For versions earlier than 0.14, see the <a href=#version-note>version note</a> above. </p>
 <h3 id=passing-custom-http-cookie-keyvalue-pairs-via-jdbc-driver>Passing Custom HTTP Cookie Key/Value Pairs via JDBC Driver</h3>
diff --git a/docs/latest/hiveserver2-thrift-api_27843687/index.html b/docs/latest/hiveserver2-thrift-api_27843687/index.html
index 3cf854d..ac28547 100644
--- a/docs/latest/hiveserver2-thrift-api_27843687/index.html
+++ b/docs/latest/hiveserver2-thrift-api_27843687/index.html
@@ -167,68 +167,68 @@ namespace cpp Apache.Hive
 // List of protocol versions. A new token should be
 // added to the end of this list every time a change is made.
 enum ProtocolVersion {
-  HIVE\_SERVER2\_PROTOCOL\_V1
+  HIVE_SERVER2_PROTOCOL_V1
 }
 
 enum TType {
-  BOOLEAN\_TYPE,
-  TINYINT\_TYPE,
-  SMALLINT\_TYPE,
-  INT\_TYPE,
-  BIGINT\_TYPE,
-  FLOAT\_TYPE,
-  DOUBLE\_TYPE,
-  STRING\_TYPE,
-  TIMESTAMP\_TYPE,
-  BINARY\_TYPE,
-  ARRAY\_TYPE,
-  MAP\_TYPE,
-  STRUCT\_TYPE,
-  UNION\_TYPE,
-  USER\_DEFINED\_TYPE
+  BOOLEAN_TYPE,
+  TINYINT_TYPE,
+  SMALLINT_TYPE,
+  INT_TYPE,
+  BIGINT_TYPE,
+  FLOAT_TYPE,
+  DOUBLE_TYPE,
+  STRING_TYPE,
+  TIMESTAMP_TYPE,
+  BINARY_TYPE,
+  ARRAY_TYPE,
+  MAP_TYPE,
+  STRUCT_TYPE,
+  UNION_TYPE,
+  USER_DEFINED_TYPE
 }
   
-const set&lt;TType&gt; PRIMITIVE\_TYPES = [
-  TType.BOOLEAN\_TYPE
-  TType.TINYINT\_TYPE
-  TType.SMALLINT\_TYPE
-  TType.INT\_TYPE
-  TType.BIGINT\_TYPE
-  TType.FLOAT\_TYPE
-  TType.DOUBLE\_TYPE
-  TType.STRING\_TYPE
-  TType.TIMESTAMP\_TYPE
-  TType.BINARY\_TYPE
+const set&lt;TType&gt; PRIMITIVE_TYPES = [
+  TType.BOOLEAN_TYPE
+  TType.TINYINT_TYPE
+  TType.SMALLINT_TYPE
+  TType.INT_TYPE
+  TType.BIGINT_TYPE
+  TType.FLOAT_TYPE
+  TType.DOUBLE_TYPE
+  TType.STRING_TYPE
+  TType.TIMESTAMP_TYPE
+  TType.BINARY_TYPE
 ]
 
-const set&lt;TType&gt; COMPLEX\_TYPES = [
-  TType.ARRAY\_TYPE
-  TType.MAP\_TYPE
-  TType.STRUCT\_TYPE
-  TType.UNION\_TYPE
-  TType.USER\_DEFINED\_TYPE
+const set&lt;TType&gt; COMPLEX_TYPES = [
+  TType.ARRAY_TYPE
+  TType.MAP_TYPE
+  TType.STRUCT_TYPE
+  TType.UNION_TYPE
+  TType.USER_DEFINED_TYPE
 ]
 
-const set&lt;TType&gt; COLLECTION\_TYPES = [
-  TType.ARRAY\_TYPE
-  TType.MAP\_TYPE
+const set&lt;TType&gt; COLLECTION_TYPES = [
+  TType.ARRAY_TYPE
+  TType.MAP_TYPE
 ]
 
-const map&lt;TType,string&gt; TYPE\_NAMES = {
-  TType.BOOLEAN\_TYPE: &quot;BOOLEAN&quot;,
-  TType.TINYINT\_TYPE: &quot;TINYINT&quot;,
-  TType.SMALLINT\_TYPE: &quot;SMALLINT&quot;,
-  TType.INT\_TYPE: &quot;INT&quot;,
-  TType.BIGINT\_TYPE: &quot;BIGINT&quot;,
-  TType.FLOAT\_TYPE: &quot;FLOAT&quot;,
-  TType.DOUBLE\_TYPE: &quot;DOUBLE&quot;,
-  TType.STRING\_TYPE: &quot;STRING&quot;,
-  TType.TIMESTAMP\_TYPE: &quot;TIMESTAMP&quot;,
-  TType.BINARY\_TYPE: &quot;BINARY&quot;,
-  TType.ARRAY\_TYPE: &quot;ARRAY&quot;,
-  TType.MAP\_TYPE: &quot;MAP&quot;,
-  TType.STRUCT\_TYPE: &quot;STRUCT&quot;,
-  TType.UNION\_TYPE: &quot;UNIONTYPE&quot;
+const map&lt;TType,string&gt; TYPE_NAMES = {
+  TType.BOOLEAN_TYPE: &quot;BOOLEAN&quot;,
+  TType.TINYINT_TYPE: &quot;TINYINT&quot;,
+  TType.SMALLINT_TYPE: &quot;SMALLINT&quot;,
+  TType.INT_TYPE: &quot;INT&quot;,
+  TType.BIGINT_TYPE: &quot;BIGINT&quot;,
+  TType.FLOAT_TYPE: &quot;FLOAT&quot;,
+  TType.DOUBLE_TYPE: &quot;DOUBLE&quot;,
+  TType.STRING_TYPE: &quot;STRING&quot;,
+  TType.TIMESTAMP_TYPE: &quot;TIMESTAMP&quot;,
+  TType.BINARY_TYPE: &quot;BINARY&quot;,
+  TType.ARRAY_TYPE: &quot;ARRAY&quot;,
+  TType.MAP_TYPE: &quot;MAP&quot;,
+  TType.STRUCT_TYPE: &quot;STRUCT&quot;,
+  TType.UNION_TYPE: &quot;UNIONTYPE&quot;
 }
 
 // Thrift does not support recursively defined types or forward declarations,
@@ -240,8 +240,8 @@ const map&lt;TType,string&gt; TYPE\_NAMES = {
 // &quot;INT&quot;:
 // TTypeDesc {
 //   types = [
-//     TTypeEntry.primitive\_entry {
-//       type = INT\_TYPE
+//     TTypeEntry.primitive_entry {
+//       type = INT_TYPE
 //     }
 //   ]
 // }
@@ -249,11 +249,11 @@ const map&lt;TType,string&gt; TYPE\_NAMES = {
 // &quot;ARRAY&lt;INT&gt;&quot;:
 // TTypeDesc {
 //   types = [
-//     TTypeEntry.array\_entry {
-//       object\_type\_ptr = 1
+//     TTypeEntry.array_entry {
+//       object_type_ptr = 1
 //     },
-//     TTypeEntry.primitive\_entry {
-//       type = INT\_TYPE
+//     TTypeEntry.primitive_entry {
+//       type = INT_TYPE
 //     }
 //   ]
 // }
@@ -261,15 +261,15 @@ const map&lt;TType,string&gt; TYPE\_NAMES = {
 // &quot;MAP&lt;INT,STRING&gt;&quot;:
 // TTypeDesc {
 //   types = [
-//     TTypeEntry.map\_entry {
-//       key\_type\_ptr = 1
-//       value\_type\_ptr = 2
+//     TTypeEntry.map_entry {
+//       key_type_ptr = 1
+//       value_type_ptr = 2
 //     },
-//     TTypeEntry.primitive\_entry {
-//       type = INT\_TYPE
+//     TTypeEntry.primitive_entry {
+//       type = INT_TYPE
 //     },
-//     TTypeEntry.primitive\_entry {
-//       type = STRING\_TYPE
+//     TTypeEntry.primitive_entry {
+//       type = STRING_TYPE
 //     }
 //   ]
 // }
@@ -279,29 +279,29 @@ typedef i32 TTypeEntryPtr
 // Type entry for a primitive type.
 struct TPrimitiveTypeEntry {
   // The primitive type token. This must satisfy the condition
-  // that type is in the PRIMITIVE\_TYPES set.
+  // that type is in the PRIMITIVE_TYPES set.
   1: required TType type
 }
 
 // Type entry for an ARRAY type.
 struct TArrayTypeEntry {
-  1: required TTypeEntryPtr object\_type\_ptr
+  1: required TTypeEntryPtr object_type_ptr
 }
 
 // Type entry for a MAP type.
 struct TMapTypeEntry {
-  1: required TTypeEntryPtr key\_type\_ptr
-  2: required TTypeEntryPtr value\_type\_ptr
+  1: required TTypeEntryPtr key_type_ptr
+  2: required TTypeEntryPtr value_type_ptr
 }
 
 // Type entry for a STRUCT type.
 struct TStructTypeEntry {
-  1: required map&lt;string, TTypeEntryPtr&gt; name\_to\_type\_ptr
+  1: required map&lt;string, TTypeEntryPtr&gt; name_to_type_ptr
 }
 
 // Type entry for a UNIONTYPE type.
 struct TUnionTypeEntry {
-  1: required map&lt;string, TTypeEntryPtr&gt; name\_to\_type\_ptr
+  1: required map&lt;string, TTypeEntryPtr&gt; name_to_type_ptr
 }
 
 struct TUserDefinedTypeEntry {
@@ -311,12 +311,12 @@ struct TUserDefinedTypeEntry {
 
 // We use a union here since Thrift does not support inheritance.
 union TTypeEntry {
-  1: TPrimitiveTypeEntry primitive\_entry
-  2: TArrayTypeEntry array\_entry
-  3: TMapTypeEntry map\_entry
-  4: TStructTypeEntry struct\_entry
-  5: TUnionTypeEntry union\_entry
-  6: TUserDefinedTypeEntry user\_defined\_type\_entry
+  1: TPrimitiveTypeEntry primitive_entry
+  2: TArrayTypeEntry array_entry
+  3: TMapTypeEntry map_entry
+  4: TStructTypeEntry struct_entry
+  5: TUnionTypeEntry union_entry
+  6: TUserDefinedTypeEntry user_defined_type_entry
 }
 
 // Type descriptor for columns.
@@ -330,10 +330,10 @@ struct TTypeDesc {
 // A result set column descriptor.
 struct TColumnDesc {
   // The name of the column
-  1: required string col\_name
+  1: required string col_name
 
   // The type descriptor for this column
-  2: required TTypeDesc type\_desc
+  2: required TTypeDesc type_desc
   
   // The ordinal position of this column in the schema
   3: required i32 position
@@ -354,13 +354,13 @@ struct TTableSchema {
 // disambiguated by looking at the Schema of the
 // result set.
 union TColumnValue {
-  1: bool   bool\_val      // BOOLEAN
-  2: byte   byte\_val      // TINYINT
-  3: i16    i16\_val       // SMALLINT
-  4: i32    i32\_val       // INT
-  5: i64    i64\_val       // BIGINT, TIMESTAMP
-  6: double double\_val    // FLOAT, DOUBLE
-  7: string string\_val    // STRING, LIST, MAP, STRUCT, UNIONTYPE, BINARY
+  1: bool   bool_val      // BOOLEAN
+  2: byte   byte_val      // TINYINT
+  3: i16    i16_val       // SMALLINT
+  4: i32    i32_val       // INT
+  5: i64    i64_val       // BIGINT, TIMESTAMP
+  6: double double_val    // FLOAT, DOUBLE
+  7: string string_val    // STRING, LIST, MAP, STRUCT, UNIONTYPE, BINARY
 }
 
 // Represents a row in a rowset.
@@ -371,31 +371,31 @@ struct TRow {
 // Represents a rowset
 struct TRowSet {
   // The starting row offset of this rowset.
-  1: i64 start\_row\_offset
+  1: i64 start_row_offset
   2: list&lt;TRow&gt; rows
 }
 
 // The return status code contained in each response.
 enum TStatusCode {
   SUCCESS,
-  SUCCESS\_WITH\_INFO,
-  SQL\_STILL\_EXECUTING,
+  SUCCESS_WITH_INFO,
+  SQL_STILL_EXECUTING,
   ERROR,
-  INVALID\_HANDLE
+  INVALID_HANDLE
 }
 
 // The return status of a remote request
 struct TStatus {
-  1: required TStatusCode status\_code
+  1: required TStatusCode status_code
 
-  // If status is SUCCESS\_WITH\_INFO, info\_msgs may be populated with
+  // If status is SUCCESS_WITH_INFO, info_msgs may be populated with
   // additional diagnostic information.
-  2: optional list&lt;string&gt; info\_msgs
+  2: optional list&lt;string&gt; info_msgs
 
   // If status is ERROR, then the following fields may be set
-  3: optional string sql\_state  // as defined in the ISO/IEF CLI specification
-  4: optional i32 error\_code    // internal error code
-  5: optional string error\_message
+  3: optional string sql_state  // as defined in the ISO/IEF CLI specification
+  4: optional i32 error_code    // internal error code
+  5: optional string error_message
 }
 
 // The state of an operation (i.e. a query or other
@@ -423,10 +423,10 @@ typedef string TIdentifier
 // A search pattern.
 //
 // Valid search pattern characters:
-// '\_': Any single character.
+// '_': Any single character.
 // '%': Any sequence of zero or more characters.
 // '\': Escape character used to include special characters,
-//      e.g. '\_', '%', '\'. If a '\' precedes a non-special
+//      e.g. '_', '%', '\'. If a '\' precedes a non-special
 //      character it has no special meaning and is interpreted
 //      literally.
 typedef string TPattern
@@ -453,23 +453,23 @@ struct THandleIdentifier {
 // Client-side handle to persistent
 // session information on the server-side.
 struct TSessionHandle {
-  1: required THandleIdentifier sess\_id
+  1: required THandleIdentifier sess_id
 }
 
 // The subtype of an OperationHandle.
 enum TOperationType {
-  EXECUTE\_STATEMENT,
-  GET\_TYPE\_INFO,
-  GET\_TABLES,
-  GET\_COLUMNS,
-  GET\_FUNCTIONS,
+  EXECUTE_STATEMENT,
+  GET_TYPE_INFO,
+  GET_TABLES,
+  GET_COLUMNS,
+  GET_FUNCTIONS,
 }
 
 // Client-side reference to a task running
 // asynchronously on the server.
 struct TOperationHandle {
-  1: required THandleIdentifier op\_id
-  2: required TOperationType op\_type
+  1: required THandleIdentifier op_id
+  2: required TOperationType op_type
 }
 
 // OpenSession()
@@ -478,7 +478,7 @@ struct TOperationHandle {
 // which operations may be executed. 
 struct TOpenSessionReq {
   // The version of the HiveServer2 protocol that the client is using.
-  1: required ProtocolVersion client\_protocol = ProtocolVersion.HIVE\_SERVER2\_PROTOCOL\_V1
+  1: required ProtocolVersion client_protocol = ProtocolVersion.HIVE_SERVER2_PROTOCOL_V1
   
   // Username and password for authentication.
   // Depending on the authentication scheme being used,
@@ -497,10 +497,10 @@ struct TOpenSessionResp {
   1: required TStatus status
 
   // The protocol version that the server is using.
-  2: ProtocolVersion server\_protocol = ProtocolVersion.HIVE\_SERVER2\_PROTOCOL\_V1
+  2: ProtocolVersion server_protocol = ProtocolVersion.HIVE_SERVER2_PROTOCOL_V1
 
   // Session Handle
-  3: TSessionHandle session\_handle
+  3: TSessionHandle session_handle
 
   // The configuration settings for this session.
   4: map&lt;string, string&gt; configuration
@@ -512,7 +512,7 @@ struct TOpenSessionResp {
 // currently allocated to that session. Any open
 // operations in that session will be canceled.
 struct TCloseSessionReq {
-  1: required TSessionHandle session\_handle
+  1: required TSessionHandle session_handle
 }
 
 struct TCloseSessionResp {
@@ -526,12 +526,12 @@ struct TCloseSessionResp {
 // using the same keys as ODBC.
 struct TGetInfoReq {
   // The sesssion to run this request against
-  1: required TSessionHandle session\_handle
+  1: required TSessionHandle session_handle
 
   // List of keys for which info is requested. If unset or empty,
   // the response message will contain the values of all Info
   // properties.
-  2: optional list&lt;string&gt; info\_keys
+  2: optional list&lt;string&gt; info_keys
 }
 
 struct TGetInfoResp {
@@ -558,12 +558,12 @@ struct TExecuteStatementReq {
   // the existing session configuration before this statement
   // is executed. These properties apply to this statement
   // only and will not affect the subsequent state of the Session.
-  3: map&lt;string, string&gt; conf\_overlay
+  3: map&lt;string, string&gt; conf_overlay
 }
 
 struct TExecuteStatementResp {
   1: required TStatus status
-  2: TOperationHandle op\_handle
+  2: TOperationHandle op_handle
 }
 
 // GetTypeInfo()
@@ -581,7 +581,7 @@ struct TGetTypeInfoReq {
 
 struct TGetTypeInfoResp {
   1: required TStatus status
-  2: TOperationHandle op\_handle
+  2: TOperationHandle op_handle
 }  
 
 // GetTables()
@@ -594,22 +594,22 @@ struct TGetTypeInfoResp {
 // Result Set Columns:
 //
 // col1
-// name: TABLE\_CAT
+// name: TABLE_CAT
 // type: STRING
 // desc: Catalog name. NULL if not applicable.
 //
 // col2
-// name: TABLE\_SCHEM
+// name: TABLE_SCHEM
 // type: STRING
 // desc: Schema name.
 //
 // col3
-// name: TABLE\_NAME
+// name: TABLE_NAME
 // type: STRING
 // desc: Table name.
 //
 // col4
-// name: TABLE\_TYPE
+// name: TABLE_TYPE
 // type: STRING
 // desc: The table type, e.g. &quot;TABLE&quot;, &quot;VIEW&quot;, etc.
 //
@@ -623,23 +623,23 @@ struct TGetTablesReq {
   1: required TSessionHandle session
 
   // Name of the catalog or a search pattern.
-  2: optional TPatternOrIdentifier catalog\_name
+  2: optional TPatternOrIdentifier catalog_name
 
   // Name of the schema or a search pattern.
-  3: required TPatternOrIdentifier schema\_name
+  3: required TPatternOrIdentifier schema_name
 
   // Name of the table or a search pattern.
-  4: required TPatternOrIdentifier table\_name
+  4: required TPatternOrIdentifier table_name
 
   // List of table types to match
   // e.g. &quot;TABLE&quot;, &quot;VIEW&quot;, &quot;SYSTEM TABLE&quot;, &quot;GLOBAL TEMPORARY&quot;,
   // &quot;LOCAL TEMPORARY&quot;, &quot;ALIAS&quot;, &quot;SYNONYM&quot;, etc.
-  5: list&lt;string&gt; table\_types
+  5: list&lt;string&gt; table_types
 }
 
 struct TGetTablesResp {
   1: required TStatus status
-  2: TOperationHandle op\_handle
+  2: TOperationHandle op_handle
 }
 
 // GetColumns()
@@ -656,21 +656,21 @@ struct TGetColumnsReq {
   1: required TSessionHandle session
 
   // Name of the catalog. Must not contain a search pattern.
-  2: optional TIdentifier catalog\_name
+  2: optional TIdentifier catalog_name
 
   // Schema name or search pattern
-  3: required TPatternOrIdentifier schema\_name
+  3: required TPatternOrIdentifier schema_name
 
   // Table name or search pattern
-  4: required TPatternOrIdentifier table\_name
+  4: required TPatternOrIdentifier table_name
 
   // Column name or search pattern
-  5: required TPatternOrIdentifier column\_name
+  5: required TPatternOrIdentifier column_name
 }
 
 struct TGetColumnsResp {
   1: required TStatus status
-  2: optional TOperationHandle op\_handle
+  2: optional TOperationHandle op_handle
 }
 
 // GetFunctions()
@@ -680,7 +680,7 @@ struct TGetColumnsResp {
 // Result Set Columns:
 //
 // col1
-// name: FUNCTION\_NAME
+// name: FUNCTION_NAME
 // type: STRING
 // desc: The name of the function.
 //
@@ -690,12 +690,12 @@ struct TGetColumnsResp {
 // desc: A description of the function.
 //
 // col3
-// name: FUNCTION\_TYPE
+// name: FUNCTION_TYPE
 // type: STRING
 // desc: The function type: &quot;UDF&quot;, &quot;UDAF&quot;, or &quot;UDTF&quot;.
 //
 // col4
-// name: FUNCTION\_CLASS
+// name: FUNCTION_CLASS
 // type: STRING
 // desc: The fully qualified name of the class
 //       that implements the specified function.
@@ -707,7 +707,7 @@ struct TGetFunctionsReq {
 
 struct TGetFunctionsResp {
   1: required TStatus status
-  2: optional TOperationHandle op\_handle
+  2: optional TOperationHandle op_handle
 }
   
 
@@ -716,12 +716,12 @@ struct TGetFunctionsResp {
 // Get the status of an operation running on the server.
 struct TGetOperationStatusReq {
   // Session to run this request against
-  1: required TOperationHandle op\_handle
+  1: required TOperationHandle op_handle
 }
 
 struct TGetOperationStatusResp {
   1: required TStatus status
-  2: TOperationState op\_state
+  2: TOperationState op_state
 }
 
 // CancelOperation()
@@ -730,7 +730,7 @@ struct TGetOperationStatusResp {
 // frees any resources which were allocated.
 struct TCancelOperationReq {
   // Operation to cancel
-  1: required TOperationHandle op\_handle
+  1: required TOperationHandle op_handle
 }
 
 struct TCancelOperationResp {
@@ -743,12 +743,12 @@ struct TCancelOperationResp {
 // request, this function returns the queryplan for that
 // statement annotated with counter information.
 struct TGetQueryPlanReq {
-  1: required TOperationHandle op\_handle
+  1: required TOperationHandle op_handle
 }
 
 struct TGetQueryPlanResp {
   1: required TStatus status
-  2: optional queryplan.QueryPlan query\_plan
+  2: optional queryplan.QueryPlan query_plan
 }
 
 // CloseOperation()
@@ -758,7 +758,7 @@ struct TGetQueryPlanResp {
 // all of the resources which were allocated on
 // the server to service the operation.
 struct TCloseOperationReq {
-  1: required TOperationHandle op\_handle
+  1: required TOperationHandle op_handle
 }
 
 struct TCloseOperationResp {
@@ -770,7 +770,7 @@ struct TCloseOperationResp {
 // Retrieves schema information for the specified operation
 struct TGetResultSetMetadataReq {
   // Operation for which to fetch result set schema information
-  1: required TOperationHandle op\_handle
+  1: required TOperationHandle op_handle
 }
 
 struct TGetResultSetMetadataResp {
@@ -780,27 +780,27 @@ struct TGetResultSetMetadataResp {
 
 enum TFetchOrientation {
   // Get the next rowset. The fetch offset is ignored.
-  FETCH\_NEXT,
+  FETCH_NEXT,
 
   // Get the previous rowset. The fetch offset is ignored.
   // NOT SUPPORTED
-  FETCH\_PRIOR,
+  FETCH_PRIOR,
 
   // Return the rowset at the given fetch offset relative
   // to the curren rowset.
   // NOT SUPPORTED
-  FETCH\_RELATIVE,
+  FETCH_RELATIVE,
 
   // Return the rowset at the specified fetch offset.
   // NOT SUPPORTED
-  FETCH\_ABSOLUTE,
+  FETCH_ABSOLUTE,
 
   // Get the first rowset in the result set.
-  FETCH\_FIRST,
+  FETCH_FIRST,
 
   // Get the last rowset in the result set.
   // NOT SUPPORTED
-  FETCH\_LAST
+  FETCH_LAST
 }
 
 // FetchResults()
@@ -809,22 +809,22 @@ enum TFetchOrientation {
 // a particular OperationHandle.
 struct TFetchResultsReq {
   // Operation from which to fetch results.
-  1: required TOperationHandle op\_handle
+  1: required TOperationHandle op_handle
 
   // The fetch orientation. For V1 this must be either
-  // FETCH\_NEXT or FETCH\_FIRST. Defaults to FETCH\_NEXT.
-  2: TFetchOrientation orientation = TFetchOrientation.FETCH\_NEXT
+  // FETCH_NEXT or FETCH_FIRST. Defaults to FETCH_NEXT.
+  2: TFetchOrientation orientation = TFetchOrientation.FETCH_NEXT
   
   // Max number of rows that should be returned in
   // the rowset.
-  3: i64 max\_rows
+  3: i64 max_rows
 }
 
 struct TFetchResultsResp {
   1: required TStatus status
 
   // TRUE if there are more rows left to fetch from the server.
-  2: bool has\_more\_rows
+  2: bool has_more_rows
 
   // The rowset. This is optional so that we have the
   // option in the future of adding alternate formats for
diff --git a/docs/latest/hiveserver_27362111/index.html b/docs/latest/hiveserver_27362111/index.html
index 833763a..c3e6a1e 100644
--- a/docs/latest/hiveserver_27362111/index.html
+++ b/docs/latest/hiveserver_27362111/index.html
@@ -140,8 +140,8 @@ $ bin/hive --service hiveserver
 
 </code></pre><p><strong>0.7 and Earlier</strong></p>
 <pre tabindex=0><code>$ build/dist/bin/hive --service hiveserver --help
-usage HIVE\_PORT=xxxx ./hive --service hiveserver
-  HIVE\_PORT : Specify the server port
+usage HIVE_PORT=xxxx ./hive --service hiveserver
+  HIVE_PORT : Specify the server port
 
 $ bin/hive --service hiveserver
 
diff --git a/docs/latest/hivewebinterface_27362110/index.html b/docs/latest/hivewebinterface_27362110/index.html
index 7ace6de..9eb3d74 100644
--- a/docs/latest/hivewebinterface_27362110/index.html
+++ b/docs/latest/hivewebinterface_27362110/index.html
@@ -191,7 +191,7 @@ ASF
 
 &lt;property&gt;
   &lt;name&gt;hive.hwi.war.file&lt;/name&gt;
-  &lt;value&gt;${HIVE\_HOME}/lib/hive-hwi-&lt;version&gt;.war&lt;/value&gt;
+  &lt;value&gt;${HIVE_HOME}/lib/hive-hwi-&lt;version&gt;.war&lt;/value&gt;
   &lt;description&gt;This is the WAR file with the jsp content for Hive Web Interface&lt;/description&gt;
 &lt;/property&gt;
 
@@ -199,7 +199,7 @@ ASF
 <h3 id=start-up>Start Up</h3>
 <p>When initializing <code>hive</code> with no arguments, the CLI is invoked. Hive has an extension architecture used to start other <code>hive</code> demons.<br>
 Jetty requires <a href=http://ant.apache.org/>Apache Ant</a> to start HWI. You should define ANT_LIB as an environment variable or add that to the <code>hive</code> invocation.</p>
-<pre tabindex=0><code>export ANT\_LIB=/opt/ant/lib
+<pre tabindex=0><code>export ANT_LIB=/opt/ant/lib
 bin/hive --service hwi
 
 </code></pre><p>Java has no direct way of demonizing. In a production environment you should create a wrapper script.</p>
diff --git a/docs/latest/how-to-edit-the-website_33294834/index.html b/docs/latest/how-to-edit-the-website_33294834/index.html
index a7f14ef..440e811 100644
--- a/docs/latest/how-to-edit-the-website_33294834/index.html
+++ b/docs/latest/how-to-edit-the-website_33294834/index.html
@@ -127,7 +127,7 @@ ASF
 <ol>
 <li>Commit a change to the website&rsquo;s source <a href=http://daringfireball.net/projects/markdown/syntax>Markdown</a> files located in <a href=https://svn.apache.org/repos/asf/hive/cms/trunk>https://svn.apache.org/repos/asf/hive/cms/trunk</a>. Before committing test that the site still builds locally by installing the <a href=http://apache.org/dev/cmsref.html#local-build>CMS build scripts</a> and running:</li>
 </ol>
-<pre tabindex=0><code>buildsite/build\_site.pl --source-base hive-site --target-base hive-website
+<pre tabindex=0><code>buildsite/build_site.pl --source-base hive-site --target-base hive-website
 
 </code></pre><p>If deleting a file or changing the name of a file make a trivial edit to lib/path.pm or lib/view.pm to force a full site rebuild. If making a simple edit it is easier to just use the Apache bookmarklet.
 2. Wait a few minutes to get the email on the commits list that buildbot has rebuilt the <a href=http://hive.staging.apache.org/>staging website</a>.
diff --git a/docs/latest/howtocontribute_27362107/index.html b/docs/latest/howtocontribute_27362107/index.html
index 9a4fe5a..2e5a827 100644
--- a/docs/latest/howtocontribute_27362107/index.html
+++ b/docs/latest/howtocontribute_27362107/index.html
@@ -315,7 +315,7 @@ The default value is <code>false</code>.</li>
 git clone --origin apache https://github.com/apache/hive
 cd hive
 # add your own fork as a remote
-git remote add GITHUB\_USER git@github.com:GITHUB\_USER/hive
+git remote add GITHUB_USER git@github.com:GITHUB_USER/hive
 </code></pre><p>You will need a separate branch to make your changes; you need to this for every PR you are doing.</p>
 <pre tabindex=0><code># fetch all changes - so you will create your feature branch on top of the current master
 git fetch --all
@@ -323,7 +323,7 @@ git fetch --all
 git branch HIVE-9999-something apache/master
 git checkout HIVE-9999-something
 # push your feature branch to your github fork - and set that branch as upstream to this branch
-git push GITHUB\_USER -u HEAD
+git push GITHUB_USER -u HEAD
 </code></pre><p>Make your change</p>
 <pre tabindex=0><code># make your changes; you should include the ticketid + message in the first commit message
 git commit -m 'HIVE-9999: Something' -a
@@ -412,7 +412,7 @@ brew install automake
 
 ./bootstrap.sh
 
-sudo ./configure --with-openssl=/usr/local/Cellar/openssl@1.1/1.1.1j --without-erlang --without-nodejs --without-python --without-py3 --without-perl --without-php --without-php\_extension --without-ruby --without-haskell --without-go --without-swift --without-dotnetcore --without-qt5
+sudo ./configure --with-openssl=/usr/local/Cellar/openssl@1.1/1.1.1j --without-erlang --without-nodejs --without-python --without-py3 --without-perl --without-php --without-php_extension --without-ruby --without-haskell --without-go --without-swift --without-dotnetcore --without-qt5
 
 brew install openssl
 
@@ -430,7 +430,7 @@ curl -o /usr/local/share/fb303/if/fb303.thrift https://raw.githubusercontent.com
 </code></pre><p>``
 3. For Linux:</p>
 <pre tabindex=0><code>cd /path/to/thrift-0.14.1
-/configure -without-erlang --without-nodejs --without-python --without-py3 --without-perl --without-php --without-php\_extension --without-ruby --without-haskell --without-go --without-swift --without-dotnetcore --without-qt5
+/configure -without-erlang --without-nodejs --without-python --without-py3 --without-perl --without-php --without-php_extension --without-ruby --without-haskell --without-go --without-swift --without-dotnetcore --without-qt5
 sudo make
 sudo make install 
 sudo mkdir -p /usr/local/share/fb303/if
diff --git a/docs/latest/howtorelease_27362106/index.html b/docs/latest/howtorelease_27362106/index.html
index 4c1b839..9c5956a 100644
--- a/docs/latest/howtorelease_27362106/index.html
+++ b/docs/latest/howtorelease_27362106/index.html
@@ -224,7 +224,7 @@ gpg: Good signature from &quot;Your Name &lt;YOUR-APACHE-ID@apache.org&gt;&quot;
 </ol>
 <pre tabindex=0><code>% sftp YOUR-APACHE-ID@home.apache.org
 
-sftp&gt; cd public\_html
+sftp&gt; cd public_html
 sftp&gt; mkdir hive-storage-X.Y.Z
 sftp&gt; cd hive-storage-X.Y.Z
 sftp&gt; put hive-storage-X.Y.Z-rcR.tar.gz*
@@ -306,8 +306,8 @@ git push -u origin branch-X.Y
 <ol>
 <li>Check out the release branch with:</li>
 </ol>
-<pre tabindex=0><code>git clone https://git-wip-us.apache.org/repos/asf/hive.git/ &lt;hive\_src\_dir&gt;
-cd &lt;hive\_src\_dir&gt;
+<pre tabindex=0><code>git clone https://git-wip-us.apache.org/repos/asf/hive.git/ &lt;hive_src_dir&gt;
+cd &lt;hive_src_dir&gt;
 git checkout branch-X.Y
 </code></pre><ol start=2>
 <li>Update the <code>version</code> property value in all pom.xml files. You should remove the <code>SNAPSHOT</code> suffix and set <code>version</code> equal to <code>hive-X.Y.Z</code> where Z is the point release number in this release series (0 for the first one, in which case this step is a no-op since you already did this above when creating the branch). Use <a href=http://mojo.codehaus.org/versions-maven-plugin/set-mojo.html>Maven&rsquo;s Versions plugin</a> to do this as follows:</li>
@@ -353,7 +353,7 @@ apache-hive-X.Y.Z-src.tar.gz: OK
 </li>
 </ol>
 <pre tabindex=0><code>% gpg --full-generate-key
-% gpg --keyserver hkp://keyserver.ubuntu.com --send-keys &lt;PUB\_KEY&gt;
+% gpg --keyserver hkp://keyserver.ubuntu.com --send-keys &lt;PUB_KEY&gt;
 % svn co --depth files https://dist.apache.org/repos/dist/release/hive
 % cd hive
 % (gpg --list-sigs &lt;NAME&gt; &amp;&amp; gpg --armor --export &lt;NAME&gt;) &gt;&gt; KEYS
@@ -464,9 +464,9 @@ git push origin :release-X.Y.Z-rcR
 </code></pre><ol start=6>
 <li>Copy the generated javadocs from the source repository to the javadocs repository, add and commit:</li>
 </ol>
-<pre tabindex=0><code>mkdir &lt;hive\_javadocs\_repo\_dir&gt;/rX.Y.Z/
-cd &lt;hive\_javadocs\_repo\_dir&gt;
-cp -r &lt;hive\_source\_dir&gt;/target/site/apidocs ./rX.Y.Z/api
+<pre tabindex=0><code>mkdir &lt;hive_javadocs_repo_dir&gt;/rX.Y.Z/
+cd &lt;hive_javadocs_repo_dir&gt;
+cp -r &lt;hive_source_dir&gt;/target/site/apidocs ./rX.Y.Z/api
 svn add rX.Y.Z
 svn commit
 </code></pre><p>If this is a bugfix release, svn rm the obsoleted version. (For eg., when committing javadocs for r0.13.1, r0.13.0 would have been removed)
@@ -476,8 +476,8 @@ svn commit
 <li>Edit files content/downloads.mdtext and javadoc.mdtext to appropriately add entries for the new release in the appropriate location. For example, for 1.2.0, the entries made were as follows:</li>
 </ol>
 <pre tabindex=0><code>./downloads.md:### 18 May 2015 : release 1.2.0 available
-./downloads.md:You can look at the complete [JIRA change log for this release][HIVE\_1\_2\_0\_CL].
-./downloads.md:[HIVE\_1\_2\_0\_CL]: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329345&amp;styleName=Text&amp;projectId=12310843
+./downloads.md:You can look at the complete [JIRA change log for this release][HIVE_1_2_0_CL].
+./downloads.md:[HIVE_1_2_0_CL]: https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329345&amp;styleName=Text&amp;projectId=12310843
 ./javadoc.md:  * [Hive 1.2.0 Javadocs][r1.2.0]
 ./javadoc.md:[r1.2.0]: /javadocs/r1.2.0/api/index.html
 </code></pre><p>As you can see, you will need a release note link for this release as created previously for this section.
@@ -534,8 +534,8 @@ The Apache Hive Team
 <ol>
 <li>Check out the release branch with:</li>
 </ol>
-<pre tabindex=0><code>git clone https://git-wip-us.apache.org/repos/asf/hive.git/ &lt;hive\_src\_dir&gt;
-cd &lt;hive\_src\_dir&gt;
+<pre tabindex=0><code>git clone https://git-wip-us.apache.org/repos/asf/hive.git/ &lt;hive_src_dir&gt;
+cd &lt;hive_src_dir&gt;
 git checkout branch-X.Y
 </code></pre><ol start=2>
 <li>Increment the <code>version</code> property value in all pom.xml files and add the <code>SNAPSHOT</code> suffix. For example, if the released version was <code>0.7.0</code>, the new value should be <code>0.7.1-SNAPSHOT</code>. Please note that the <code>SNAPSHOT</code> suffix is required in order to indicate that this is an unreleased development branch. Use <a href=http://mojo.codehaus.org/versions-maven-plugin/set-mojo.html>Maven&rsquo;s Versions plugin</a> to do this as follows:</li>
diff --git a/docs/latest/index.xml b/docs/latest/index.xml
index c048312..0e44067 100644
--- a/docs/latest/index.xml
+++ b/docs/latest/index.xml
@@ -128,10 +128,10 @@ set hive.execution.engine=spark; Hive on Spark was added in HIVE-7292.</descript
 Location The infrastructure master is at ec2-174-129-184-35.</description></item><item><title>Apache Hive : Hive remote databases/tables</title><link>https://hive.apache.org/docs/latest/80452092/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/80452092/</guid><description>Apache Hive : Hive remote databases/tables Abstract At the 2018 DataWorks conference in Berlin, Hotels.com presented Waggle Dance, a tool for federating multiple Hive cl [...]
 We believe that this type of functionality will be of increasing importance as Hadoop and Hive workloads migrate to the cloud.</description></item><item><title>Apache Hive : Hive Schema Tool</title><link>https://hive.apache.org/docs/latest/hive-schema-tool_34835119/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/hive-schema-tool_34835119/</guid><description>Apache Hive : Hive Schema Tool Metastore Schema Verification The Hive Schema Tool [...]
 Introduced in Hive 0.12.0. See HIVE-3764.
-Hive now records the schema version in the metastore database and verifies that the metastore schema version is compatible with Hive binaries that are going to accesss the metastore. Note that the Hive properties to implicitly create or alter the existing schema are disabled by default.</description></item><item><title>Apache Hive : Hive Transactions</title><link>https://hive.apache.org/docs/latest/hive-transactions_40509723/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid> [...]
+Hive now records the schema version in the metastore database and verifies that the metastore schema version is compatible with Hive binaries that are going to accesss the metastore. Note that the Hive properties to implicitly create or alter the existing schema are disabled by default.</description></item><item><title>Apache Hive : Hive Transactions</title><link>https://hive.apache.org/docs/latest/hive-transactions_40509723/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid> [...]
 Creating an Iceberg Table
-An iceberg table can be created using STORED BY ICEBERGkeywords while creating a table.
-Creating an Iceberg table using normal create command CREATE TABLE TBL\_ICE (ID INT) STORED BY ICEBERG; The above creates an iceberg table named &amp;lsquo;TBL_ICE&amp;rsquo;</description></item><item><title>Apache Hive : Hive-Tez Compatibility</title><link>https://hive.apache.org/docs/latest/hive-tez-compatibility_59689974/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/hive-tez-compatibility_59689974/</guid><description>Apache Hive : H [...]
+An iceberg table can be created using STORED BY ICEBERG keywords while creating a table.
+Creating an Iceberg table using normal create command CREATE TABLE TBL_ICE (ID INT) STORED BY ICEBERG; The above creates an iceberg table named &amp;lsquo;TBL_ICE&amp;rsquo;</description></item><item><title>Apache Hive : Hive-Tez Compatibility</title><link>https://hive.apache.org/docs/latest/hive-tez-compatibility_59689974/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/hive-tez-compatibility_59689974/</guid><description>Apache Hive : Hi [...]
 Hive (Works with) Tez 0.13 0.4.0-incubating 0.14 0.5.2+, (through 0.7.0) 1.0 0.5.2, (through 0.7.0) 1.1 0.5.2, (through 0.7.0) 1.2* 0.5.3, (through 0.7.0) 2.0 0.8.2 *Hive-1.2 is the latest release of Hive as of 07/2015.</description></item><item><title>Apache Hive : HiveAmazonElasticMapReduce</title><link>https://hive.apache.org/docs/latest/hiveamazonelasticmapreduce_27825646/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/hiveamazonelas [...]
 Background This document explores the different ways of leveraging Hive on Amazon Web Services - namely S3, EC2 and Elastic Map-Reduce.
 Hadoop already has a long tradition of being run on EC2 and S3. These are well documented in the links below which are a must read:
@@ -164,7 +164,7 @@ values, such as gender.
 Approach We want to develop a bitmap index that can reuse as much of the existing Compact Index code as possible.</description></item><item><title>Apache Hive : Introduction to Apache Hive</title><link>https://hive.apache.org/docs/latest/introduction-to-apache-hive_283118337/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/introduction-to-apache-hive_283118337/</guid><description>Apache Hive : Introduction to Apache Hive The Apache Hive™  [...]
 Built on top of Apache Hadoop™, Hive provides the following features:
 Tools to enable easy access to data via SQL, thus enabling data warehousing tasks such as extract/transform/load (ETL), reporting, and data analysis. A mechanism to impose structure on a variety of data formats Access to files stored either directly in Apache HDFS™ or in other data storage systems such as Apache HBase™ Query execution via Apache Tez™ or MapReduce Procedural language with HPL-SQL Sub-second query retrieval via Hive LLAP, Apache YARN and Apache Slider.</description></item> [...]
-env set -e set -x . ${HOME}/toolchain/toolchain.sh export PATH=$JAVA\_HOME/bin:$MAVEN\_HOME/bin:$PATH ROOT=$PWD BRANCH=trunk export JIRA\_NAME=&amp;quot;HIVE-${ISSUE\_NUM}&amp;quot; echo $JIRA\_NAME export JIRA\_ROOT\_URL=&amp;quot;https://issues.apache.org&amp;quot; test -d hive/build/ || mkdir -p hive/build/ cd hive/build/ rm -rf ptest2 svn co http://svn.apache.org/repos/asf/hive/trunk/testutils/ptest2/ ptest2 cd ptest2 # process the jira JIRA\_TEXT=$(mktemp) trap &amp;quot;rm -f $JIRA [...]
+env set -e set -x . ${HOME}/toolchain/toolchain.sh export PATH=$JAVA_HOME/bin:$MAVEN_HOME/bin:$PATH ROOT=$PWD BRANCH=trunk export JIRA_NAME=&amp;quot;HIVE-${ISSUE_NUM}&amp;quot; echo $JIRA_NAME export JIRA_ROOT_URL=&amp;quot;https://issues.apache.org&amp;quot; test -d hive/build/ || mkdir -p hive/build/ cd hive/build/ rm -rf ptest2 svn co http://svn.apache.org/repos/asf/hive/trunk/testutils/ptest2/ ptest2 cd ptest2 # process the jira JIRA_TEXT=$(mktemp) trap &amp;quot;rm -f $JIRA_TEXT&am [...]
 Commands and CLIs
 Commands Hive CLI (old) Beeline CLI (new) Variable Substitution HCatalog CLI File Formats
 Avro Files ORC Files Parquet Compressed Data Storage LZO Compression Data Types
@@ -186,10 +186,10 @@ Overview The EXPORT command exports the data of a table or partition, along with
 Materialized views with automatic rewriting can result in very similar results. Hive 2.3.0 adds support for materialzed views. Using columnar file formats (Parquet, ORC) – they can do selective scanning; they may even skip entire files/blocks.</description></item><item><title>Apache Hive : LanguageManual JoinOptimization</title><link>https://hive.apache.org/docs/latest/languagemanual-joinoptimization_33293167/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apa [...]
 Current and Future Optimizations Optimize Auto Join Conversion
 - [Current Optimization](#current-optimization)+ [Auto Conversion to SMB Map Join](#auto-conversion-to-smb-map-join) - [SMB Join across Tables with Different Keys](#smb-join-across-tables-with-different-keys) Generate Hash Tables on the Task Side</description></item><item><title>Apache Hive : LanguageManual Joins</title><link>https://hive.apache.org/docs/latest/languagemanual-joins_27362039/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest [...]
-join\_table: table\_reference [INNER] JOIN table\_factor [join\_condition] | table\_reference {LEFT|RIGHT|FULL} [OUTER] JOIN table\_reference join\_condition | table\_reference LEFT SEMI JOIN table\_reference join\_condition | table\_reference CROSS JOIN table\_reference [join\_condition] (as of Hive 0.</description></item><item><title>Apache Hive : LanguageManual LateralView</title><link>https://hive.apache.org/docs/latest/languagemanual-lateralview_27362040/</link><pubDate>Thu, 12 Dec  [...]
+join_table: table_reference [INNER] JOIN table_factor [join_condition] | table_reference {LEFT|RIGHT|FULL} [OUTER] JOIN table_reference join_condition | table_reference LEFT SEMI JOIN table_reference join_condition | table_reference CROSS JOIN table_reference [join_condition] (as of Hive 0.</description></item><item><title>Apache Hive : LanguageManual LateralView</title><link>https://hive.apache.org/docs/latest/languagemanual-lateralview_27362040/</link><pubDate>Thu, 12 Dec 2024 00:00:00 [...]
 Introduced in Hive version 0.11.0.
-The Optimized Row Columnar (ORC) file format provides a highly efficient way to store Hive data.</description></item><item><title>Apache Hive : LanguageManual Sampling</title><link>https://hive.apache.org/docs/latest/languagemanual-sampling_27362042/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/languagemanual-sampling_27362042/</guid><description>Apache Hive : LanguageManual Sampling Sampling Syntax Sampling Bucketized Table Block Samp [...]
-Select Syntax [WITH CommonTableExpression (, CommonTableExpression)*] (Note: Only available starting with Hive 0.</description></item><item><title>Apache Hive : LanguageManual SortBy</title><link>https://hive.apache.org/docs/latest/languagemanual-sortby_27362045/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/languagemanual-sortby_27362045/</guid><description>Apache Hive : LanguageManual SortBy Order, Sort, Cluster, and Distribute By Syn [...]
+The Optimized Row Columnar (ORC) file format provides a highly efficient way to store Hive data.</description></item><item><title>Apache Hive : LanguageManual Sampling</title><link>https://hive.apache.org/docs/latest/languagemanual-sampling_27362042/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/languagemanual-sampling_27362042/</guid><description>Apache Hive : LanguageManual Sampling Sampling Syntax Sampling Bucketized Table Block Samp [...]
+Select Syntax [WITH CommonTableExpression (, CommonTableExpression)*] (Note: Only available starting with Hive 0.</description></item><item><title>Apache Hive : LanguageManual SortBy</title><link>https://hive.apache.org/docs/latest/languagemanual-sortby_27362045/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/languagemanual-sortby_27362045/</guid><description>Apache Hive : LanguageManual SortBy Order, Sort, Cluster, and Distribute By Syn [...]
 Hive versions prior to 1.</description></item><item><title>Apache Hive : LanguageManual VariableSubstitution</title><link>https://hive.apache.org/docs/latest/languagemanual-variablesubstitution_30754722/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/languagemanual-variablesubstitution_30754722/</guid><description>Apache Hive : LanguageManual VariableSubstitution Introduction Using Variables Substitution During Query Construction Disabli [...]
 The Hive variable substitution mechanism was designed to avoid some of the code that was getting baked into the scripting language on top of Hive.
 Examples such as the following shell commands may (inefficiently) be used to set variables within a script:</description></item><item><title>Apache Hive : LanguageManual VirtualColumns</title><link>https://hive.apache.org/docs/latest/languagemanual-virtualcolumns_27362048/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/languagemanual-virtualcolumns_27362048/</guid><description>Apache Hive : LanguageManual VirtualColumns Virtual Columns S [...]
@@ -239,7 +239,7 @@ Hive query compilation takes the query string and produces a QueryPlan.</descrip
 RCFile stores table data in a flat file consisting of binary key/value pairs. It first partitions rows horizontally into row splits, and then it vertically partitions each row split in a columnar way. RCFile stores the metadata of a row split as the key part of a record, and all the data of a row split as the value part.</description></item><item><title>Apache Hive : RCFileCat</title><link>https://hive.apache.org/docs/latest/rcfilecat_30748712/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0 [...]
 Data Prints out the rows stored in an RCFile, columns are tab separated and rows are newline separated.
 Usage:
-hive --rcfilecat [--start=start\_offset] [--length=len] [--verbose] fileName --start=start\_offset Start offset to begin reading in the file --length=len Length of data to read from the file --verbose Prints periodic stats about the data read, how many records, how many bytes, scan rate Metadata New in 0.</description></item><item><title>Apache Hive : Rebalance compaction</title><link>https://hive.apache.org/docs/latest/rebalance-compaction_240884502/</link><pubDate>Thu, 12 Dec 2024 00:0 [...]
+hive --rcfilecat [--start=start_offset] [--length=len] [--verbose] fileName --start=start_offset Start offset to begin reading in the file --length=len Length of data to read from the file --verbose Prints periodic stats about the data read, how many records, how many bytes, scan rate Metadata New in 0.</description></item><item><title>Apache Hive : Rebalance compaction</title><link>https://hive.apache.org/docs/latest/rebalance-compaction_240884502/</link><pubDate>Thu, 12 Dec 2024 00:00: [...]
 Apache Hivemall (incubating) Apache Hivemall is a scalable machine learning library for Apache Hive, Apache Spark, and Apache Pig.
 Apache Sentry (incubating) Sentry is a role-based authorization system for Apache Hive.</description></item><item><title>Apache Hive : Replacing the Implementation of Hive CLI Using Beeline</title><link>https://hive.apache.org/docs/latest/replacing-the-implementation-of-hive-cli-using-beeline_61311909/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/replacing-the-implementation-of-hive-cli-using-beeline_61311909/</guid><description>Apache [...]
 Features to be added Major Recent Changes Table Statistics Archiving Indexing First Cut Concurrency Conversion to Map-Join at Runtime Support for Multiple Distincts Remove Partition Filtering Conditions INSERT INTO statement Block-level merge HAVING clause support Cross-database queries Bitmap Index Use Filter Pushdown for Automatically Accessing Indexes Remove Duplicate Filters Authentication Authorization Current Projects Bloom Filters TIMESTAMP data type Up For Grabs Priorities are de [...]
@@ -256,7 +256,7 @@ Hive****SP: we integrate Hadoop-GIS with Hive, to support both structured querie
 Statistics and Data Mining in Hive ngrams() and context_ngrams(): N-gram frequency estimation Use Cases Usage Example histogram_numeric(): Estimating frequency distributions Use Cases Usage Example ngrams() and context_ngrams(): N-gram frequency estimation N-grams are subsequences of length N drawn from a longer sequence.</description></item><item><title>Apache Hive : StatsDev</title><link>https://hive.apache.org/docs/latest/statsdev_27362062/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +00 [...]
 Motivation Statistics such as the number of rows of a table or partition and the histograms of a particular interesting column are important in many ways.</description></item><item><title>Apache Hive : Storage API Release Proposal</title><link>https://hive.apache.org/docs/latest/storage-api-release-proposal_67635447/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/storage-api-release-proposal_67635447/</guid><description>Apache Hive : Sto [...]
 Besides HBase, a storage handler implementation is also available for Hypertable, and others are being developed for Cassandra, Azure Table, JDBC (MySQL and others), MongoDB, ElasticSearch, Phoenix HBase, VoltDB and Google Spreadsheets.</description></item><item><title>Apache Hive : Streaming Data Ingest</title><link>https://hive.apache.org/docs/latest/streaming-data-ingest_40509746/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/streami [...]
-SELECT customer.customer\_num, (SELECT SUM(ship\_charge) FROM orders WHERE customer.customer\_num = orders.customer\_num ) AS total\_ship\_chg FROM customer Recently a lot of work has been done to extend support for subqueries (HIVE-15456). But this work primarily targeted extending subquery support in WHERE and HAVING clauses. We plan to continue the work done in HIVE-15456 to support subqueries in a select list (see HIVE-16091).</description></item><item><title>Apache Hive : Suggestion [...]
+SELECT customer.customer_num, (SELECT SUM(ship_charge) FROM orders WHERE customer.customer_num = orders.customer_num ) AS total_ship_chg FROM customer Recently a lot of work has been done to extend support for subqueries (HIVE-15456). But this work primarily targeted extending subquery support in WHERE and HAVING clauses. We plan to continue the work done in HIVE-15456 to support subqueries in a select list (see HIVE-16091).</description></item><item><title>Apache Hive : Suggestion for D [...]
 Feature ID Feature Name Implemented Mandatory Comments E011 Numeric data types Yes Mandatory E011-01 INTEGER and SMALLINT data types (including all spellings) Yes Mandatory E011-02 REAL, DOUBLE PRECISON, and FLOAT data types Yes Mandatory E011-03 DECIMAL and NUMERIC data types Yes Mandatory E011-04 Arithmetic operators Yes Mandatory E011-05 Numeric comparison Yes Mandatory E011-06 Implicit casting among the numeric data types Yes Mandatory E021 Character string types Yes Mandatory E021-0 [...]
 The problem we try to solve here is the cache consistency issue.</description></item><item><title>Apache Hive : TeradataBinarySerde</title><link>https://hive.apache.org/docs/latest/teradatabinaryserde_89068127/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/teradatabinaryserde_89068127/</guid><description>Apache Hive : TeradataBinarySerde Availability Overview How to export Using TPT FastExport Using BTEQ How to import Using BTEQ Using T [...]
 The TeradataBinarySerDe is available in Hive 2.4 or greater.
@@ -277,7 +277,7 @@ Installation Python modules Global installation Local installation SSH keys Conf
 The view refers to exactly one base table or updatable view in the FROM clause without a WHERE clause. Each column in the view is a column in the underlying table/updatable view with no underlying columns duplicated. Views must have the same partition columns as the underlying table/updatable view. When inserting into a view:
 If a view does not specify all underlying columns, NULL will be inserted for each column not specified.</description></item><item><title>Apache Hive : User and Group Filter Support with LDAP Atn Provider in HiveServer2</title><link>https://hive.apache.org/docs/latest/user-and-group-filter-support-with-ldap-atn-provider-in-hiveserver2_58852417/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/user-and-group-filter-support-with-ldap-atn-prov [...]
 User Guide The query language specification is available at LanguageManual. Also see, GettingStarted for setup instructions.
-Supported Features Usage Examples Creating tables MovieLens User Ratings CREATE TABLE u\_data ( userid INT, movieid INT, rating INT, unixtime STRING) ROW FORMAT DELIMITED FIELDS TERMINATED BY '\t' STORED AS TEXTFILE; Apache Access Log Tables add jar ../build/contrib/hive\_contrib.jar; CREATE TABLE apachelog ( host STRING, identity STRING, user STRING, time STRING, request STRING, status STRING, size STRING, referer STRING, agent STRING) ROW FORMAT SERDE 'org.</description></item><item><t [...]
+Supported Features Usage Examples Creating tables MovieLens User Ratings CREATE TABLE u_data ( userid INT, movieid INT, rating INT, unixtime STRING) ROW FORMAT DELIMITED FIELDS TERMINATED BY '\t' STORED AS TEXTFILE; Apache Access Log Tables add jar ../build/contrib/hive_contrib.jar; CREATE TABLE apachelog ( host STRING, identity STRING, user STRING, time STRING, request STRING, status STRING, size STRING, referer STRING, agent STRING) ROW FORMAT SERDE 'org.</description></item><item><tit [...]
  Navigation Links Next: Using WebHCat</description></item><item><title>Apache Hive : WebHCat Configure</title><link>https://hive.apache.org/docs/latest/webhcat-configure_34015738/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/webhcat-configure_34015738/</guid><description>Apache Hive : WebHCat Configure WebHCat Configuration WebHCat Configuration Configuration Files Configuration Variables Default Values Configuration Files The configur [...]
 The WebHCat-specific configuration is split into two layers:
 webhcat-default.xml – All the configuration variables that WebHCat needs.</description></item><item><title>Apache Hive : WebHCat InstallWebHCat</title><link>https://hive.apache.org/docs/latest/webhcat-installwebhcat_34015585/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://hive.apache.org/docs/latest/webhcat-installwebhcat_34015585/</guid><description>Apache Hive : WebHCat InstallWebHCat WebHCat Installation WebHCat Installation WebHCat Installed with Hive WebHCat I [...]
diff --git a/docs/latest/indexdev_27362104/index.html b/docs/latest/indexdev_27362104/index.html
index 29a8eb5..bf7a430 100644
--- a/docs/latest/indexdev_27362104/index.html
+++ b/docs/latest/indexdev_27362104/index.html
@@ -147,18 +147,18 @@ ASF
 <p>Only single-table indexes are supported. Others (such as join indexes) may be more appropriately expressed as materialized views once Hive has support for those.</p>
 <p>This document currently only covers index creation and maintenance. A follow-on will explain how indexes are used to optimize queries (building on <a href=https://hive.apache.org/docs/latest/filterpushdowndev_27362092/>FilterPushdownDev</a>).</p>
 <h2 id=create-index>CREATE INDEX</h2>
-<pre tabindex=0><code>CREATE INDEX index\_name
-ON TABLE base\_table\_name (col\_name, ...)
+<pre tabindex=0><code>CREATE INDEX index_name
+ON TABLE base_table_name (col_name, ...)
 AS 'index.handler.class.name'
 [WITH DEFERRED REBUILD]
-[IDXPROPERTIES (property\_name=property\_value, ...)]
-[IN TABLE index\_table\_name]
-[PARTITIONED BY (col\_name, ...)]
+[IDXPROPERTIES (property_name=property_value, ...)]
+[IN TABLE index_table_name]
+[PARTITIONED BY (col_name, ...)]
 [
    [ ROW FORMAT ...] STORED AS ...
    | STORED BY ...
 ]
-[LOCATION hdfs\_path]
+[LOCATION hdfs_path]
 [TBLPROPERTIES (...)]
 [COMMENT &quot;index comment&quot;]
 
@@ -190,7 +190,7 @@ AS 'org.apache.hadoop.hive.ql.index.compact.CompactIndexHandler';
 <p>To avoid the generated name, a user-specified name such as t_x can be supplied instead:</p>
 <pre tabindex=0><code>CREATE INDEX x ON TABLE t(j)
 AS 'org.apache.hadoop.hive.ql.index.compact.CompactIndexHandler'
-IN TABLE t\_x;
+IN TABLE t_x;
 
 </code></pre><p>Note that index names are qualified by the containing base table (like partitions), so the same index name can be used across two different tables. However, names of index tables are in the same namespace as all other tables and views, so they must be unique within the same database.</p>
 <p>An index has a storage descriptor which includes the subset of columns from the original table covered by the index. If the index representation is stored in a table, most of the other fields in the index&rsquo;s own storage descriptor (e.g. LOCATION) will be irrelevant.</p>
@@ -205,46 +205,46 @@ IN TABLE t\_x;
 <p>Here are the MySQL metastore upgrade statements.</p>
 <pre tabindex=0><code>DROP TABLE IF EXISTS {{IDXS}};
 CREATE TABLE {{IDXS}} (
-  {{INDEX\_ID}} bigint(20) NOT NULL,
-  {{CREATE\_TIME}} int(11) NOT NULL,
-  {{DEFERRED\_REBUILD}} bit(1) NOT NULL,
-  {{INDEX\_HANDLER\_CLASS}} varchar(256) DEFAULT NULL,
-  {{INDEX\_NAME}} varchar(128) DEFAULT NULL,
-  {{INDEX\_TBL\_ID}} bigint(20) DEFAULT NULL,
-  {{LAST\_ACCESS\_TIME}} int(11) NOT NULL,
-  {{ORIG\_TBL\_ID}} bigint(20) DEFAULT NULL,
-  {{SD\_ID}} bigint(20) DEFAULT NULL,
-  PRIMARY KEY ({{INDEX\_ID}}),
-  UNIQUE KEY {{UNIQUEINDEX}} ({{INDEX\_NAME}},{{ORIG\_TBL\_ID}}),
-  KEY {{IDXS\_FK1}} ({{SD\_ID}}),
-  KEY {{IDXS\_FK2}} ({{INDEX\_TBL\_ID}}),
-  KEY {{IDXS\_FK3}} ({{ORIG\_TBL\_ID}}),
-  CONSTRAINT {{IDXS\_FK3}} FOREIGN KEY ({{ORIG\_TBL\_ID}}) REFERENCES {{TBLS}} ({{TBL\_ID}}),
-  CONSTRAINT {{IDXS\_FK1}} FOREIGN KEY ({{SD\_ID}}) REFERENCES {{SDS}} ({{SD\_ID}}),
-  CONSTRAINT {{IDXS\_FK2}} FOREIGN KEY ({{INDEX\_TBL\_ID}}) REFERENCES {{TBLS}} ({{TBL\_ID}})
+  {{INDEX_ID}} bigint(20) NOT NULL,
+  {{CREATE_TIME}} int(11) NOT NULL,
+  {{DEFERRED_REBUILD}} bit(1) NOT NULL,
+  {{INDEX_HANDLER_CLASS}} varchar(256) DEFAULT NULL,
+  {{INDEX_NAME}} varchar(128) DEFAULT NULL,
+  {{INDEX_TBL_ID}} bigint(20) DEFAULT NULL,
+  {{LAST_ACCESS_TIME}} int(11) NOT NULL,
+  {{ORIG_TBL_ID}} bigint(20) DEFAULT NULL,
+  {{SD_ID}} bigint(20) DEFAULT NULL,
+  PRIMARY KEY ({{INDEX_ID}}),
+  UNIQUE KEY {{UNIQUEINDEX}} ({{INDEX_NAME}},{{ORIG_TBL_ID}}),
+  KEY {{IDXS_FK1}} ({{SD_ID}}),
+  KEY {{IDXS_FK2}} ({{INDEX_TBL_ID}}),
+  KEY {{IDXS_FK3}} ({{ORIG_TBL_ID}}),
+  CONSTRAINT {{IDXS_FK3}} FOREIGN KEY ({{ORIG_TBL_ID}}) REFERENCES {{TBLS}} ({{TBL_ID}}),
+  CONSTRAINT {{IDXS_FK1}} FOREIGN KEY ({{SD_ID}}) REFERENCES {{SDS}} ({{SD_ID}}),
+  CONSTRAINT {{IDXS_FK2}} FOREIGN KEY ({{INDEX_TBL_ID}}) REFERENCES {{TBLS}} ({{TBL_ID}})
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
 
 --
--- Table structure for table {{INDEX\_PARAMS}}
+-- Table structure for table {{INDEX_PARAMS}}
 --
 
-DROP TABLE IF EXISTS {{INDEX\_PARAMS}};
-CREATE TABLE {{INDEX\_PARAMS}} (
-  {{INDEX\_ID}} bigint(20) NOT NULL,
-  {{PARAM\_KEY}} varchar(256) NOT NULL,
-  {{PARAM\_VALUE}} varchar(767) DEFAULT NULL,
-  PRIMARY KEY ({{INDEX\_ID}},{{PARAM\_KEY}}),
-  CONSTRAINT {{INDEX\_PARAMS\_FK1}} FOREIGN KEY ({{INDEX\_ID}}) REFERENCES {{IDXS}} ({{INDEX\_ID}})
+DROP TABLE IF EXISTS {{INDEX_PARAMS}};
+CREATE TABLE {{INDEX_PARAMS}} (
+  {{INDEX_ID}} bigint(20) NOT NULL,
+  {{PARAM_KEY}} varchar(256) NOT NULL,
+  {{PARAM_VALUE}} varchar(767) DEFAULT NULL,
+  PRIMARY KEY ({{INDEX_ID}},{{PARAM_KEY}}),
+  CONSTRAINT {{INDEX_PARAMS_FK1}} FOREIGN KEY ({{INDEX_ID}}) REFERENCES {{IDXS}} ({{INDEX_ID}})
 ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
 
 </code></pre><h2 id=rebuild>REBUILD</h2>
-<pre tabindex=0><code>ALTER INDEX index\_name ON table\_name [PARTITION (...)] REBUILD
+<pre tabindex=0><code>ALTER INDEX index_name ON table_name [PARTITION (...)] REBUILD
 
-</code></pre><p>For the PARTITION clause syntax, see <a href=#languagemanual-ddl#add\_partitions>LanguageManual DDL#Add_Partitions</a>.</p>
+</code></pre><p>For the PARTITION clause syntax, see <a href=#languagemanual-ddl#add_partitions>LanguageManual DDL#Add_Partitions</a>.</p>
 <p>If WITH DEFERRED REBUILD is specified on CREATE INDEX, then the newly created index is initially empty (regardless of whether the table contains any data). The ALTER INDEX &mldr; REBUILD command can be used to build the index structure for all partitions or a single partition.</p>
 <p>If data in the base table changes, then the REBUILD command must be used to bring the index up to date. This is an atomic operation, so if the table was previously indexed, and a rebuild fails, then the stale index remains untouched.</p>
 <h2 id=drop-index>DROP INDEX</h2>
-<pre tabindex=0><code>DROP INDEX index\_name ON table\_name
+<pre tabindex=0><code>DROP INDEX index_name ON table_name
 
 </code></pre><p>An index can be dropped at any time with DROP INDEX. This will also cascade to the index table (if one exists).</p>
 <p>Attempting to drop an index table directly with DROP TABLE will fail.</p>
@@ -351,7 +351,7 @@ public abstract class AbstractIndexHandler implements HiveIndexHandler
 <p>The reference implementation creates what is referred to as a &ldquo;compact&rdquo; index. This means that rather than storing the HDFS location of each occurrence of a particular value, it only stores the addresses of HDFS blocks containing that value. This is optimized for point-lookups in the case where a value typically occurs more than once in nearby rows; the index size is kept small since there are many fewer blocks than rows. The tradeoff is that extra work is required during  [...]
 <p>The compact index is stored in an index table. The index table columns consist of the indexed columns from the base table followed by a _bucketname string column (indicating the name of the file containing the indexed block) followed by an _offsets array column (indicating the block offsets within the corresponding file). The index table is stored as sorted on the indexed columns (but not on the generated columns).</p>
 <p>The reference implementation can be plugged in with</p>
-<pre tabindex=0><code>ADD JAR /path/to/hive\_idx-compact.jar;
+<pre tabindex=0><code>ADD JAR /path/to/hive_idx-compact.jar;
 CREATE INDEX ...
 AS 'org.apache.hadoop.hive.ql.index.compact.CompactIndexHandler';
 
diff --git a/docs/latest/jdbc-storage-handler_95651916/index.html b/docs/latest/jdbc-storage-handler_95651916/index.html
index 9e21522..bed4a72 100644
--- a/docs/latest/jdbc-storage-handler_95651916/index.html
+++ b/docs/latest/jdbc-storage-handler_95651916/index.html
@@ -140,7 +140,7 @@ ASF
 </ul>
 <h1 id=syntax>Syntax</h1>
 <p>JdbcStorageHandler supports reading from jdbc data source in Hive. Currently writing to a jdbc data source is not supported. To use JdbcStorageHandler, you need to create an external table using JdbcStorageHandler. Here is a simple example:</p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE student\_jdbc
+<pre tabindex=0><code>CREATE EXTERNAL TABLE student_jdbc
 (
   name string,
   age int,
@@ -157,7 +157,7 @@ TBLPROPERTIES (
     &quot;hive.sql.dbcp.maxActive&quot; = &quot;1&quot;
 );
 </code></pre><p>You can also alter table properties of the jdbc external table using alter table statement, just like other non-native Hive table:</p>
-<pre tabindex=0><code>ALTER TABLE student\_jdbc SET TBLPROPERTIES (&quot;hive.sql.dbcp.password&quot; = &quot;passwd&quot;);
+<pre tabindex=0><code>ALTER TABLE student_jdbc SET TBLPROPERTIES (&quot;hive.sql.dbcp.password&quot; = &quot;passwd&quot;);
 </code></pre><h2 id=table-properties>Table Properties</h2>
 <p>In the create table statement, you are required to specify the following table properties:</p>
 <ul>
@@ -187,7 +187,7 @@ TBLPROPERTIES (
 <p>Note complex data type: struct, map, array are not supported</p>
 <h2 id=columntype-mapping>Column/Type Mapping</h2>
 <p>hive.sql.table / hive.sql.query defines a tabular data with a schema. The schema definition has to be the same as the table schema definition. For example, the following create table statement will fail:</p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE student\_jdbc
+<pre tabindex=0><code>CREATE EXTERNAL TABLE student_jdbc
 (
   name string,
   age int,
@@ -199,11 +199,11 @@ TBLPROPERTIES (
     &quot;hive.sql.query&quot; = &quot;SELECT name, age, gpa, gender FROM STUDENT&quot;,
 );
 </code></pre><p>However, column name and column type of hive.sql.table / hive.sql.query schema may be different than the table schema. In this case, database column maps to hive column by position. If data type is different, Hive will try to convert it according to Hive table schema. For example:</p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE student\_jdbc
+<pre tabindex=0><code>CREATE EXTERNAL TABLE student_jdbc
 (
   sname string,
   age int,
-  effective\_gpa decimal(4,3)
+  effective_gpa decimal(4,3)
 )
 STORED BY 'org.apache.hive.storage.jdbc.JdbcStorageHandler'
 TBLPROPERTIES (
@@ -218,7 +218,7 @@ TBLPROPERTIES (
 <pre tabindex=0><code>hadoop credential create host1.password -provider jceks://hdfs/user/foo/test.jceks -v passwd1
 hadoop credential create host2.password -provider jceks://hdfs/user/foo/test.jceks -v passwd2
 </code></pre><p>This will create a keystore file located on hdfs://user/foo/test.jceks which contains two keys: host1.password and host2.password. When creating table in Hive, you will need to specify “hive.sql.dbcp.password.keystore” and “hive.sql.dbcp.password.key” instead of “hive.sql.dbcp.password” in create table statement:</p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE student\_jdbc
+<pre tabindex=0><code>CREATE EXTERNAL TABLE student_jdbc
 (
   name string,
   age int,
@@ -267,7 +267,7 @@ jdbc.JdbcInputFormat: split:interval:ikey[90,)
 </code></pre><h1 id=computation-pushdown>Computation Pushdown</h1>
 <p>Hive will pushdown computation to jdbc table aggressively, so we can make best usage of the native capacity of jdbc data source.</p>
 <p>For example, if we have another table voter_jdbc:</p>
-<pre tabindex=0><code>EATE EXTERNAL TABLE voter\_jdbc
+<pre tabindex=0><code>EATE EXTERNAL TABLE voter_jdbc
 (
   name string,
   age int,
@@ -284,12 +284,12 @@ TBLPROPERTIES (
     &quot;hive.sql.table&quot; = &quot;VOTER&quot;
 );
 </code></pre><p>Then the following join operation will push down to mysql:</p>
-<pre tabindex=0><code>select * from student\_jdbc join voter\_jdbc on student\_jdbc.name=voter\_jdbc.name;
+<pre tabindex=0><code>select * from student_jdbc join voter_jdbc on student_jdbc.name=voter_jdbc.name;
 </code></pre><p>This can be manifest by explain:</p>
-<pre tabindex=0><code>explain select * from student\_jdbc join voter\_jdbc on student\_jdbc.name=voter\_jdbc.name;
+<pre tabindex=0><code>explain select * from student_jdbc join voter_jdbc on student_jdbc.name=voter_jdbc.name;
         . . . . . .
         TableScan
-          alias: student\_jdbc
+          alias: student_jdbc
           properties:
             hive.sql.query SELECT `t`.`name`, `t`.`age`, `t`.`gpa`, `t0`.`name` AS `name0`, `t0`.`age` AS `age0`, `t0`.`registration`, `t0`.`contribution`
 FROM (SELECT *
@@ -369,7 +369,7 @@ insert into alice.country
 values (7, 'Japan');
 </code></pre><p>Create a user and associate them with a default schema. For example:</p>
 <pre tabindex=0><code>CREATE LOGIN greg WITH PASSWORD = 'GregPass123!$';
-CREATE USER greg FOR LOGIN greg WITH DEFAULT\_SCHEMA=bob;
+CREATE USER greg FOR LOGIN greg WITH DEFAULT_SCHEMA=bob;
 </code></pre><p>Allow the user to connect to the database and run queries. For example:</p>
 <pre tabindex=0><code>GRANT CONNECT, SELECT TO greg;
 </code></pre><h2 id=oracle>Oracle</h2>
@@ -451,7 +451,7 @@ insert into alice.country
 values (7, 'Japan');
 </code></pre><p>Create a user and associate them with a default schema &lt;=> search_path. For example:</p>
 <pre tabindex=0><code>CREATE ROLE greg WITH LOGIN PASSWORD 'GregPass123!$';
-ALTER ROLE greg SET search\_path TO bob;
+ALTER ROLE greg SET search_path TO bob;
 </code></pre><p>Grant the necessary permissions to access the schema. For example:</p>
 <pre tabindex=0><code>GRANT USAGE ON SCHEMA bob TO greg;
 GRANT SELECT ON ALL TABLES IN SCHEMA bob TO greg;
diff --git a/docs/latest/jenkins-script_33295285/index.html b/docs/latest/jenkins-script_33295285/index.html
index 3171ce6..28d6729 100644
--- a/docs/latest/jenkins-script_33295285/index.html
+++ b/docs/latest/jenkins-script_33295285/index.html
@@ -120,68 +120,68 @@ ASF
 set -e
 set -x
 . ${HOME}/toolchain/toolchain.sh
-export PATH=$JAVA\_HOME/bin:$MAVEN\_HOME/bin:$PATH
+export PATH=$JAVA_HOME/bin:$MAVEN_HOME/bin:$PATH
 ROOT=$PWD
 BRANCH=trunk
-export JIRA\_NAME=&quot;HIVE-${ISSUE\_NUM}&quot;
-echo $JIRA\_NAME
-export JIRA\_ROOT\_URL=&quot;https://issues.apache.org&quot;
+export JIRA_NAME=&quot;HIVE-${ISSUE_NUM}&quot;
+echo $JIRA_NAME
+export JIRA_ROOT_URL=&quot;https://issues.apache.org&quot;
 test -d hive/build/ || mkdir -p hive/build/
 cd hive/build/
 rm -rf ptest2
 svn co http://svn.apache.org/repos/asf/hive/trunk/testutils/ptest2/ ptest2
 cd ptest2
 # process the jira
-JIRA\_TEXT=$(mktemp)
-trap &quot;rm -f $JIRA\_TEXT&quot; EXIT
-curl -s -S --location --retry 3 &quot;${JIRA\_ROOT\_URL}/jira/browse/${JIRA\_NAME}&quot; &gt; $JIRA\_TEXT
-if grep -q &quot;NO PRECOMMIT TESTS&quot; $JIRA\_TEXT
+JIRA_TEXT=$(mktemp)
+trap &quot;rm -f $JIRA_TEXT&quot; EXIT
+curl -s -S --location --retry 3 &quot;${JIRA_ROOT_URL}/jira/browse/${JIRA_NAME}&quot; &gt; $JIRA_TEXT
+if grep -q &quot;NO PRECOMMIT TESTS&quot; $JIRA_TEXT
 then
-  echo &quot;Test $JIRA\_NAME has tag NO PRECOMMIT TESTS&quot;
+  echo &quot;Test $JIRA_NAME has tag NO PRECOMMIT TESTS&quot;
   exit 0
 fi
 # ensure the patch is actually in the correct state
-if ! grep -q 'Patch Available' $JIRA\_TEXT
+if ! grep -q 'Patch Available' $JIRA_TEXT
 then
-  echo &quot;$JIRA\_NAME is not \&quot;Patch Available\&quot;. Exiting.&quot;
+  echo &quot;$JIRA_NAME is not \&quot;Patch Available\&quot;. Exiting.&quot;
   exit 1
 fi
 # pull attachments from JIRA (hack stolen from hadoop since rest api doesn't show attachments)
-PATCH\_URL=$(grep -o '&quot;/jira/secure/attachment/[0-9]*/[^&quot;]*' $JIRA\_TEXT | \
+PATCH_URL=$(grep -o '&quot;/jira/secure/attachment/[0-9]*/[^&quot;]*' $JIRA_TEXT | \
   grep -v -e 'htm[l]*$' | sort | tail -1 | \
   grep -o '/jira/secure/attachment/[0-9]*/[^&quot;]*')
-if [[ -z &quot;$PATCH\_URL&quot; ]]
+if [[ -z &quot;$PATCH_URL&quot; ]]
 then
-  echo &quot;Unable to find attachment for $JIRA\_NAME&quot;
+  echo &quot;Unable to find attachment for $JIRA_NAME&quot;
   exit 1
 fi
 # ensure attachment has not already been tested
-ATTACHMENT\_ID=$(basename $(dirname $PATCH\_URL))
-if grep -q &quot;ATTACHMENT ID: $ATTACHMENT\_ID&quot; $JIRA\_TEXT
+ATTACHMENT_ID=$(basename $(dirname $PATCH_URL))
+if grep -q &quot;ATTACHMENT ID: $ATTACHMENT_ID&quot; $JIRA_TEXT
 then
-  echo &quot;Attachment $ATTACHMENT\_ID is already tested for $JIRA\_NAME&quot;
+  echo &quot;Attachment $ATTACHMENT_ID is already tested for $JIRA_NAME&quot;
   exit 1
 fi
 # validate the patch name, parse branch if needed
 shopt -s nocasematch
-PATCH\_NAME=$(basename $PATCH\_URL)
+PATCH_NAME=$(basename $PATCH_URL)
 # Test examples:
 # HIVE-123.patch HIVE-123.1.patch HIVE-123.D123.patch HIVE-123.D123.1.patch HIVE-123-tez.patch HIVE-123.1-tez.patch
 # HIVE-XXXX.patch, HIVE-XXXX.XX.patch  HIVE-XXXX.XX-branch.patch HIVE-XXXX-branch.patch
-if [[ $PATCH\_NAME =~ ^HIVE-[0-9]+(\.[0-9]+)?(-[a-z0-9-]+)?\.(patch|patch.\txt)$ ]]
+if [[ $PATCH_NAME =~ ^HIVE-[0-9]+(\.[0-9]+)?(-[a-z0-9-]+)?\.(patch|patch.\txt)$ ]]
 then
-  if [[ -n &quot;${BASH\_REMATCH[2]}&quot; ]]
+  if [[ -n &quot;${BASH_REMATCH[2]}&quot; ]]
   then
-    BRANCH=${BASH\_REMATCH[2]#*-}
+    BRANCH=${BASH_REMATCH[2]#*-}
   else
     echo &quot;Assuming branch $BRANCH&quot;
   fi
 # HIVE-XXXX.DXXXX.patch or HIVE-XXXX.DXXXX.XX.patch
-elif [[ $PATCH\_NAME =~ ^(HIVE-[0-9]+\.)?D[0-9]+(\.[0-9]+)?\.(patch|patch.\txt)$ ]]
+elif [[ $PATCH_NAME =~ ^(HIVE-[0-9]+\.)?D[0-9]+(\.[0-9]+)?\.(patch|patch.\txt)$ ]]
 then
   echo &quot;Assuming branch $BRANCH&quot;
 else
-  echo &quot;Patch $PATCH\_NAME does not appear to be a patch&quot;
+  echo &quot;Patch $PATCH_NAME does not appear to be a patch&quot;
   exit 1
 fi
 shopt -u nocasematch
@@ -201,15 +201,15 @@ case &quot;$profile&quot; in
   echo &quot;Unknown profile '$profile'&quot;
   exit 1
 esac
-TEST\_OPTS=&quot;&quot;
-if grep -q &quot;CLEAR LIBRARY CACHE&quot; $JIRA\_TEXT
+TEST_OPTS=&quot;&quot;
+if grep -q &quot;CLEAR LIBRARY CACHE&quot; $JIRA_TEXT
 then
   echo &quot;Clearing library cache before starting test&quot;
-  TEST\_OPTS=&quot;--clearLibraryCache&quot;
+  TEST_OPTS=&quot;--clearLibraryCache&quot;
 fi
 mvn clean package -DskipTests -Drat.numUnapprovedLicenses=1000 -Dmaven.repo.local=$WORKSPACE/.m2
 set +e
-java -cp &quot;target/hive-ptest-1.0-classes.jar:target/lib/*&quot; org.apache.hive.ptest.api.client.PTestClient --endpoint http://ec2-174-129-184-35.compute-1.amazonaws.com --command testStart --profile $profile --password xxx --outputDir target/ --testHandle &quot;${BUILD\_TAG##jenkins-}&quot; --patch &quot;${JIRA\_ROOT\_URL}${PATCH\_URL}&quot; --jira &quot;$JIRA\_NAME&quot; --clearLibraryCache
+java -cp &quot;target/hive-ptest-1.0-classes.jar:target/lib/*&quot; org.apache.hive.ptest.api.client.PTestClient --endpoint http://ec2-174-129-184-35.compute-1.amazonaws.com --command testStart --profile $profile --password xxx --outputDir target/ --testHandle &quot;${BUILD_TAG##jenkins-}&quot; --patch &quot;${JIRA_ROOT_URL}${PATCH_URL}&quot; --jira &quot;$JIRA_NAME&quot; --clearLibraryCache
 ret=$?
 cd target/
 if [[ -f test-results.tar.gz ]]
diff --git a/docs/latest/kudu-integration_133631955/index.html b/docs/latest/kudu-integration_133631955/index.html
index 0be0132..f4b2680 100644
--- a/docs/latest/kudu-integration_133631955/index.html
+++ b/docs/latest/kudu-integration_133631955/index.html
@@ -158,11 +158,11 @@ ASF
 <pre tabindex=0><code>hive -hiveconf hive.kudu.master.addresses.default=localhost:7051
 </code></pre><h2 id=table-creation>Table Creation</h2>
 <p>To access Kudu tables, a Hive table must be created using the <code>CREATE</code> command with the <code>STORED BY</code> clause. Until <a href=https://issues.apache.org/jira/browse/HIVE-22021>HIVE-22021</a> is completed, the <code>EXTERNAL</code> keyword is required and will create a Hive table that references an existing Kudu table. Dropping the external Hive table will not remove the underlying Kudu table.</p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE kudu\_table (foo INT, bar STRING, baz DOUBLE)
+<pre tabindex=0><code>CREATE EXTERNAL TABLE kudu_table (foo INT, bar STRING, baz DOUBLE)
 STORED BY 'org.apache.hadoop.hive.kudu.KuduStorageHandler'
 TBLPROPERTIES (
-  &quot;kudu.table\_name&quot;=&quot;default.kudu\_table&quot;, 
-  &quot;kudu.master\_addresses&quot;=&quot;localhost:7051&quot;
+  &quot;kudu.table_name&quot;=&quot;default.kudu_table&quot;, 
+  &quot;kudu.master_addresses&quot;=&quot;localhost:7051&quot;
 );
 </code></pre><p>In the above statement, normal Hive column name and type pairs are provided as is the case with normal create table statements. The full <code>KuduStorageHandler</code> class name is provided to inform Hive that Kudu will back this Hive table. A number of TBLPROPERTIES can be provided to configure the KuduStorageHandler. The most important property is <code>kudu.table_name</code> which tells hive which Kudu table it should reference. The other common property is <code>kud [...]
 <h2 id=impala-tables>Impala Tables</h2>
@@ -170,9 +170,9 @@ TBLPROPERTIES (
 <h2 id=data-ingest>Data Ingest</h2>
 <p>Though it is a common practice to ingest the data into Kudu tables via tools like <a href=https://nifi.apache.org/>Apache NiFi</a> or <a href=https://spark.apache.org/>Apache Spark</a> and query the data via Hive, data can also be inserted to the Kudu tables via <a href=https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DML#LanguageManualDML-InsertingdataintoHiveTablesfromqueries>Hive INSERT statements</a>. It is important to note that when data is inserted a Kudu UPSERT  [...]
 <h3 id=examples>Examples</h3>
-<pre tabindex=0><code>INSERT INTO kudu\_table SELECT * FROM other\_table;
+<pre tabindex=0><code>INSERT INTO kudu_table SELECT * FROM other_table;
 
-INSERT INTO TABLE kudu\_table
+INSERT INTO TABLE kudu_table
 VALUES (1, 'test 1', 1.1), (2, 'test 2', 2.2);
 </code></pre>
 </div>
diff --git a/docs/latest/languagemanual-archiving_27362031/index.html b/docs/latest/languagemanual-archiving_27362031/index.html
index 4521066..bc0f6a6 100644
--- a/docs/latest/languagemanual-archiving_27362031/index.html
+++ b/docs/latest/languagemanual-archiving_27362031/index.html
@@ -145,11 +145,11 @@ hive&gt; set har.partfile.size=1099511627776;
 
 </code></pre><p><code>hive.archive.enabled</code> controls whether archiving operations are enabled.</p>
 <p><code>hive.archive.har.parentdir.settable</code> informs Hive whether the parent directory can be set while creating the archive. In recent versions of Hadoop the <code>-p</code> option can specify the root directory of the archive. For example, if <code>/dir1/dir2/file</code> is archived with <code>/dir1</code> as the parent directory, then the resulting archive file will contain the directory structure <code>dir2/file</code>. In older versions of Hadoop (prior to 2011), this option  [...]
-<p><code>har.partfile.size</code> controls the size of the files that make up the archive. The archive will contain <code>*size\_of\_partition*``/``har.partfile.size</code> files, rounded up. Higher values mean fewer files, but will result in longer archiving times due to the reduced number of mappers.</p>
+<p><code>har.partfile.size</code> controls the size of the files that make up the archive. The archive will contain <code>*size_of_partition*``/``har.partfile.size</code> files, rounded up. Higher values mean fewer files, but will result in longer archiving times due to the reduced number of mappers.</p>
 <h2 id=usage>Usage</h2>
 <h3 id=archive>Archive</h3>
 <p>Once the configuration values are set, a partition can be archived with the command:</p>
-<pre tabindex=0><code>ALTER TABLE table\_name ARCHIVE PARTITION (partition\_col = partition\_col\_value, partition\_col = partiton\_col\_value, ...)
+<pre tabindex=0><code>ALTER TABLE table_name ARCHIVE PARTITION (partition_col = partition_col_value, partition_col = partiton_col_value, ...)
 
 </code></pre><p>For example:</p>
 <pre tabindex=0><code>ALTER TABLE srcpart ARCHIVE PARTITION(ds='2008-04-08', hr='12')
diff --git a/docs/latest/languagemanual-cli_27362033/index.html b/docs/latest/languagemanual-cli_27362033/index.html
index fe9c0fc..dd14616 100644
--- a/docs/latest/languagemanual-cli_27362033/index.html
+++ b/docs/latest/languagemanual-cli_27362033/index.html
@@ -171,34 +171,34 @@ Usage (as it is in Hive 0.9.0):</p>
 <ul>
 <li>Example of running a query from the command line</li>
 </ul>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive -e 'select a.col from tab1 a'
+<pre tabindex=0><code>$HIVE_HOME/bin/hive -e 'select a.col from tab1 a'
 </code></pre><ul>
 <li>Example of setting Hive configuration variables</li>
 </ul>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive -e 'select a.col from tab1 a' --hiveconf hive.exec.scratchdir=/home/my/hive\_scratch  --hiveconf mapred.reduce.tasks=32
+<pre tabindex=0><code>$HIVE_HOME/bin/hive -e 'select a.col from tab1 a' --hiveconf hive.exec.scratchdir=/home/my/hive_scratch  --hiveconf mapred.reduce.tasks=32
 </code></pre><ul>
 <li>Example of dumping data out from a query into a file using silent mode</li>
 </ul>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive -S -e 'select a.col from tab1 a' &gt; a.txt
+<pre tabindex=0><code>$HIVE_HOME/bin/hive -S -e 'select a.col from tab1 a' &gt; a.txt
 </code></pre><ul>
 <li>Example of running a script non-interactively from local disk</li>
 </ul>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive -f /home/my/hive-script.sql
+<pre tabindex=0><code>$HIVE_HOME/bin/hive -f /home/my/hive-script.sql
 </code></pre><ul>
 <li>Example of running a script non-interactively from a Hadoop supported filesystem (starting in <a href=https://issues.apache.org/jira/browse/HIVE-7136>Hive 0.14</a>)</li>
 </ul>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive -f hdfs://&lt;namenode&gt;:&lt;port&gt;/hive-script.sql
-$HIVE\_HOME/bin/hive -f s3://mys3bucket/s3-script.sql 
+<pre tabindex=0><code>$HIVE_HOME/bin/hive -f hdfs://&lt;namenode&gt;:&lt;port&gt;/hive-script.sql
+$HIVE_HOME/bin/hive -f s3://mys3bucket/s3-script.sql 
 </code></pre><ul>
 <li>Example of running an initialization script before entering interactive mode</li>
 </ul>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive -i /home/my/hive-init.sql
+<pre tabindex=0><code>$HIVE_HOME/bin/hive -i /home/my/hive-init.sql
 </code></pre><h3 id=the-hiverc-file>The hiverc File</h3>
 <p>The CLI when invoked without the <code>-i</code> option will attempt to load $HIVE_HOME/bin/.hiverc and $HOME/.hiverc as initialization files.</p>
 <h3 id=logging>Logging</h3>
 <p>Hive uses log4j for logging. These logs are not emitted to the standard output by default but are instead captured to a log file specified by Hive&rsquo;s log4j properties file. By default Hive will use <code>hive-log4j.default</code> in the <code>conf/</code> directory of the Hive installation which writes out logs to <code>/tmp/&lt;userid>/hive.log</code> and uses the <code>WARN</code> level.</p>
 <p>It is often desirable to emit the logs to the standard output and/or change the logging level for debugging purposes. These can be done from the command line as follows:</p>
-<pre tabindex=0><code> $HIVE\_HOME/bin/hive --hiveconf hive.root.logger=INFO,console
+<pre tabindex=0><code> $HIVE_HOME/bin/hive --hiveconf hive.root.logger=INFO,console
 
 </code></pre><p><code>hive.root.logger</code> specifies the logging level as well as the log destination. Specifying <code>console</code> as the target sends the logs to the standard error (instead of the log file).</p>
 <p>See <a href=#hive-logging-in-getting-started>Hive Logging in Getting Started</a> for more information.</p>
diff --git a/docs/latest/languagemanual-ddl-bucketedtables_27362035/index.html b/docs/latest/languagemanual-ddl-bucketedtables_27362035/index.html
index e093f43..0419d90 100644
--- a/docs/latest/languagemanual-ddl-bucketedtables_27362035/index.html
+++ b/docs/latest/languagemanual-ddl-bucketedtables_27362035/index.html
@@ -118,16 +118,16 @@ ASF
 <p>This is a brief example on creating and populating bucketed tables. (For another example, see <a href=#bucketed-sorted-tables>Bucketed Sorted Tables</a>.)</p>
 <p>Bucketed tables are fantastic in that they allow much more efficient <a href=https://hive.apache.org/docs/latest/languagemanual-sampling_27362042/>sampling</a> than do non-bucketed tables, and they may later allow for time saving operations such as mapside joins. However, the bucketing specified at table creation is not enforced when the table is written to, and so it is possible for the table&rsquo;s metadata to advertise properties which are not upheld by the table&rsquo;s actual la [...]
 <p>First, <a href=#table-creation>table creation</a>:</p>
-<pre tabindex=0><code>CREATE TABLE user\_info\_bucketed(user\_id BIGINT, firstname STRING, lastname STRING)
-COMMENT 'A bucketed copy of user\_info'
+<pre tabindex=0><code>CREATE TABLE user_info_bucketed(user_id BIGINT, firstname STRING, lastname STRING)
+COMMENT 'A bucketed copy of user_info'
 PARTITIONED BY(ds STRING)
-CLUSTERED BY(user\_id) INTO 256 BUCKETS;
+CLUSTERED BY(user_id) INTO 256 BUCKETS;
 
 </code></pre><p>Note that we specify a column (user_id) to base the bucketing.</p>
 <p>Then we populate the table</p>
 <pre tabindex=0><code>set hive.enforce.bucketing = true;  -- (Note: Not needed in Hive 2.x onward)
-FROM user\_id
-INSERT OVERWRITE TABLE user\_info\_bucketed
+FROM user_id
+INSERT OVERWRITE TABLE user_info_bucketed
 PARTITION (ds='2009-02-25')
 SELECT userid, firstname, lastname WHERE ds='2009-02-25';
 
diff --git a/docs/latest/languagemanual-ddl_27362034/index.html b/docs/latest/languagemanual-ddl_27362034/index.html
index ec65385..0fe815e 100644
--- a/docs/latest/languagemanual-ddl_27362034/index.html
+++ b/docs/latest/languagemanual-ddl_27362034/index.html
@@ -208,44 +208,44 @@ ASF
 <p>Reserved keywords are permitted as identifiers if you quote them as described in <a href=https://issues.apache.org/jira/secure/attachment/12618321/QuotedIdentifier.html>Supporting Quoted Identifiers in Column Names</a> (version 0.13.0 and later, see <a href=https://issues.apache.org/jira/browse/HIVE-6013>HIVE-6013</a>). Most of the keywords are reserved through <a href=https://issues.apache.org/jira/browse/HIVE-6617>HIVE-6617</a> in order to reduce the ambiguity in grammar (version 1. [...]
 <h2 id=createdropalteruse-database>Create/Drop/Alter/Use Database</h2>
 <h3 id=create-database>Create Database</h3>
-<pre tabindex=0><code>CREATE [REMOTE] (DATABASE|SCHEMA) [IF NOT EXISTS] database\_name
-  [COMMENT database\_comment]
-  [LOCATION hdfs\_path]
-  [MANAGEDLOCATION hdfs\_path]
-  [WITH DBPROPERTIES (property\_name=property\_value, ...)];
+<pre tabindex=0><code>CREATE [REMOTE] (DATABASE|SCHEMA) [IF NOT EXISTS] database_name
+  [COMMENT database_comment]
+  [LOCATION hdfs_path]
+  [MANAGEDLOCATION hdfs_path]
+  [WITH DBPROPERTIES (property_name=property_value, ...)];
 
 </code></pre><p>The uses of SCHEMA and DATABASE are interchangeable – they mean the same thing. CREATE DATABASE was added in Hive 0.6 (<a href=https://issues.apache.org/jira/browse/HIVE-675>HIVE-675</a>).  The WITH DBPROPERTIES clause was added in Hive 0.7 (<a href=https://issues.apache.org/jira/browse/HIVE-1836>HIVE-1836</a>).</p>
 <p>MANAGEDLOCATION was added to database in Hive 4.0.0 (<a href=https://issues.apache.org/jira/browse/HIVE-22995>HIVE-22995</a>). LOCATION now refers to the default directory for external tables and MANAGEDLOCATION refers to the default directory for managed tables. Its recommended that MANAGEDLOCATION be within metastore.warehouse.dir so all managed tables have a common root where common governance policies. It can be used with metastore.warehouse.tenant.colocation to have it point to a [...]
 <p>REMOTE databases were added in Hive 4.0.0 (<a href=https://issues.apache.org/jira/browse/HIVE-24396>HIVE-24396</a>) for support for Data connectors. See documentation for <a href=https://cwiki.apache.org/confluence/display/Hive/Data+Connectors+in+Hive>Data connectors</a>. </p>
 <h3 id=drop-database>Drop Database</h3>
-<pre tabindex=0><code>DROP (DATABASE|SCHEMA) [IF EXISTS] database\_name [RESTRICT|CASCADE];
+<pre tabindex=0><code>DROP (DATABASE|SCHEMA) [IF EXISTS] database_name [RESTRICT|CASCADE];
 
 </code></pre><p>The uses of SCHEMA and DATABASE are interchangeable – they mean the same thing. DROP DATABASE was added in Hive 0.6 (<a href=https://issues.apache.org/jira/browse/HIVE-675>HIVE-675</a>). The default behavior is RESTRICT, where DROP DATABASE will fail if the database is not empty. To drop the tables in the database as well, use DROP DATABASE &mldr; CASCADE. Support for RESTRICT and CASCADE was added in Hive 0.8 (<a href=https://issues.apache.org/jira/browse/HIVE-2090>HIVE- [...]
 <h3 id=alter-database>Alter Database</h3>
-<pre tabindex=0><code>ALTER (DATABASE|SCHEMA) database\_name SET DBPROPERTIES (property\_name=property\_value, ...);   -- (Note: SCHEMA added in Hive 0.14.0)
+<pre tabindex=0><code>ALTER (DATABASE|SCHEMA) database_name SET DBPROPERTIES (property_name=property_value, ...);   -- (Note: SCHEMA added in Hive 0.14.0)
 
-ALTER (DATABASE|SCHEMA) database\_name SET OWNER [USER|ROLE] user\_or\_role;   -- (Note: Hive 0.13.0 and later; SCHEMA added in Hive 0.14.0)
+ALTER (DATABASE|SCHEMA) database_name SET OWNER [USER|ROLE] user_or_role;   -- (Note: Hive 0.13.0 and later; SCHEMA added in Hive 0.14.0)
  
-ALTER (DATABASE|SCHEMA) database\_name SET LOCATION hdfs\_path; -- (Note: Hive 2.2.1, 2.4.0 and later)
+ALTER (DATABASE|SCHEMA) database_name SET LOCATION hdfs_path; -- (Note: Hive 2.2.1, 2.4.0 and later)
 
-ALTER (DATABASE|SCHEMA) database\_name SET MANAGEDLOCATION hdfs\_path; -- (Note: Hive 4.0.0 and later)
+ALTER (DATABASE|SCHEMA) database_name SET MANAGEDLOCATION hdfs_path; -- (Note: Hive 4.0.0 and later)
 
 </code></pre><p>The uses of SCHEMA and DATABASE are interchangeable – they mean the same thing. ALTER SCHEMA was added in Hive 0.14 (<a href=https://issues.apache.org/jira/browse/HIVE-6601>HIVE-6601</a>).</p>
 <p>The ALTER DATABASE &mldr; SET LOCATION statement does not move the contents of the database&rsquo;s current directory to the newly specified location. It does not change the locations associated with any tables/partitions under the specified database. It only changes the default parent-directory where new tables will be added for this database. This behaviour is analogous to how changing a table-directory does not move existing partitions to a different location.</p>
 <p>The ALTER DATABASE &mldr; SET MANAGEDLOCATION statement does not move the contents of the database&rsquo;s managed tables directories to the newly specified location. It does not change the locations associated with any tables/partitions under the specified database. It only changes the default parent-directory where new tables will be added for this database. This behaviour is analogous to how changing a table-directory does not move existing partitions to a different location.</p>
 <p>No other metadata about a database can be changed. </p>
 <h3 id=use-database>Use Database</h3>
-<pre tabindex=0><code>USE database\_name;
+<pre tabindex=0><code>USE database_name;
 USE DEFAULT;
-</code></pre><p>USE sets the current database for all subsequent HiveQL statements. To revert to the default database, use the keyword &ldquo;<code>default</code>&rdquo; instead of a database name. To check which database is currently being used: <code>SELECT [current\_database()](#current\_database--)</code> (as of <a href=https://issues.apache.org/jira/browse/HIVE-4144>Hive 0.13.0</a>).</p>
+</code></pre><p>USE sets the current database for all subsequent HiveQL statements. To revert to the default database, use the keyword &ldquo;<code>default</code>&rdquo; instead of a database name. To check which database is currently being used: <code>SELECT [current_database()](#current_database--)</code> (as of <a href=https://issues.apache.org/jira/browse/HIVE-4144>Hive 0.13.0</a>).</p>
 <p><code>USE database_name</code> was added in Hive 0.6 (<a href=https://issues.apache.org/jira/browse/HIVE-675>HIVE-675</a>).</p>
 <h2 id=createdropalter-connector>Create/Drop/Alter Connector</h2>
 <h3 id=create-connector>Create Connector</h3>
-<pre tabindex=0><code>CREATE CONNECTOR [IF NOT EXISTS] connector\_name
-  [TYPE datasource\_type]
-  [URL datasource\_url]
-  [COMMENT connector\_comment]
-  [WITH DCPROPERTIES (property\_name=property\_value, ...)];
+<pre tabindex=0><code>CREATE CONNECTOR [IF NOT EXISTS] connector_name
+  [TYPE datasource_type]
+  [URL datasource_url]
+  [COMMENT connector_comment]
+  [WITH DCPROPERTIES (property_name=property_value, ...)];
 
 </code></pre><p>Since Hive 4.0.0 via <a href=https://issues.apache.org/jira/browse/HIVE-24396>HIVE-24396</a> Support for Data connectors was added in hive 4.0.0. Initial commit includes connector implementations for JDBC based datasource like MYSQL, POSTGRES, DERBY. Additional connector implementations will be added via followup commits. </p>
 <p>TYPE - Type of the remote datasource this connector connects to. for example MYSQL. The type determines the Driver class and any other params specific to this datasource.</p>
@@ -253,15 +253,15 @@ USE DEFAULT;
 <p>COMMENT - A short description for this connector.</p>
 <p>DCPROPERTIES: Contains a set of name/value pairs that are set for the connector. The credentials for the remote datasource are specified as part of the DCPROPERTIES as documented in the <a href=https://cwiki.apache.org/confluence/display/Hive/JDBC+Storage+Handler>JDBC Storage Handler</a> docs. All properties that start with a prefix of &ldquo;hive.sql&rdquo; are added to the tables mapped by this connector.</p>
 <h3 id=drop-connector>Drop Connector</h3>
-<pre tabindex=0><code>DROP CONNECTOR [IF EXISTS] connector\_name;
+<pre tabindex=0><code>DROP CONNECTOR [IF EXISTS] connector_name;
 
 </code></pre><p>Since Hive 4.0.0 via <a href=https://issues.apache.org/jira/browse/HIVE-24396>HIVE-24396</a>. If there are databases that are mapped by this connector, drop still succeeds. Users will see errors when running DDLs like &ldquo;show tables&rdquo; in the mapped databases.</p>
 <h3 id=alter-connector>Alter Connector</h3>
-<pre tabindex=0><code>ALTER CONNECTOR connector\_name SET DCPROPERTIES (property\_name=property\_value, ...);
+<pre tabindex=0><code>ALTER CONNECTOR connector_name SET DCPROPERTIES (property_name=property_value, ...);
 
-ALTER CONNECTOR connector\_name SET URL new\_url;
+ALTER CONNECTOR connector_name SET URL new_url;
  
-ALTER CONNECTOR connector\_name SET OWNER [USER|ROLE] user\_or\_role;
+ALTER CONNECTOR connector_name SET OWNER [USER|ROLE] user_or_role;
 
 </code></pre><p>Since Hive 4.0.0 via <a href=https://issues.apache.org/jira/browse/HIVE-24396>HIVE-24396</a></p>
 <p>The ALTER CONNECTOR &mldr; SET DCPROPERTIES replaces the existing properties with the new set of properties specified in the ALTER DDL.</p>
@@ -289,35 +289,35 @@ ALTER CONNECTOR connector\_name SET OWNER [USER|ROLE] user\_or\_role;
 <li><a href=#truncate-table>Truncate Table</a></li>
 </ul>
 <h3 id=create-table>Create Table</h3>
-<pre tabindex=0><code>CREATE [TEMPORARY] [EXTERNAL] TABLE [IF NOT EXISTS] [db\_name.]table\_name    -- (Note: TEMPORARY available in Hive 0.14.0 and later)
-  [(col\_name data\_type [column\_constraint\_specification] [COMMENT col\_comment], ... [constraint\_specification])]
-  [COMMENT table\_comment]
-  [PARTITIONED BY (col\_name data\_type [COMMENT col\_comment], ...)]
-  [CLUSTERED BY (col\_name, col\_name, ...) [SORTED BY (col\_name [ASC|DESC], ...)] INTO num\_buckets BUCKETS]
-  [SKEWED BY (col\_name, col\_name, ...)                  -- (Note: Available in Hive 0.10.0 and later)]
-     ON ((col\_value, col\_value, ...), (col\_value, col\_value, ...), ...)
+<pre tabindex=0><code>CREATE [TEMPORARY] [EXTERNAL] TABLE [IF NOT EXISTS] [db_name.]table_name    -- (Note: TEMPORARY available in Hive 0.14.0 and later)
+  [(col_name data_type [column_constraint_specification] [COMMENT col_comment], ... [constraint_specification])]
+  [COMMENT table_comment]
+  [PARTITIONED BY (col_name data_type [COMMENT col_comment], ...)]
+  [CLUSTERED BY (col_name, col_name, ...) [SORTED BY (col_name [ASC|DESC], ...)] INTO num_buckets BUCKETS]
+  [SKEWED BY (col_name, col_name, ...)                  -- (Note: Available in Hive 0.10.0 and later)]
+     ON ((col_value, col_value, ...), (col_value, col_value, ...), ...)
      [STORED AS DIRECTORIES]
   [
-   [ROW FORMAT row\_format] 
-   [STORED AS file\_format]
+   [ROW FORMAT row_format] 
+   [STORED AS file_format]
      | STORED BY 'storage.handler.class.name' [WITH SERDEPROPERTIES (...)]  -- (Note: Available in Hive 0.6.0 and later)
   ]
-  [LOCATION hdfs\_path]
-  [TBLPROPERTIES (property\_name=property\_value, ...)]   -- (Note: Available in Hive 0.6.0 and later)
-  [AS select\_statement];   -- (Note: Available in Hive 0.5.0 and later; not supported for external tables)
-
-CREATE [TEMPORARY] [EXTERNAL] TABLE [IF NOT EXISTS] [db\_name.]table\_name
-  LIKE existing\_table\_or\_view\_name
-  [LOCATION hdfs\_path];
-
-data\_type
-  : primitive\_type
-  | array\_type
-  | map\_type
-  | struct\_type
-  | union\_type  -- (Note: Available in Hive 0.7.0 and later)
-
-primitive\_type
+  [LOCATION hdfs_path]
+  [TBLPROPERTIES (property_name=property_value, ...)]   -- (Note: Available in Hive 0.6.0 and later)
+  [AS select_statement];   -- (Note: Available in Hive 0.5.0 and later; not supported for external tables)
+
+CREATE [TEMPORARY] [EXTERNAL] TABLE [IF NOT EXISTS] [db_name.]table_name
+  LIKE existing_table_or_view_name
+  [LOCATION hdfs_path];
+
+data_type
+  : primitive_type
+  | array_type
+  | map_type
+  | struct_type
+  | union_type  -- (Note: Available in Hive 0.7.0 and later)
+
+primitive_type
   : TINYINT
   | SMALLINT
   | INT
@@ -335,25 +335,25 @@ primitive\_type
   | VARCHAR     -- (Note: Available in Hive 0.12.0 and later)
   | CHAR        -- (Note: Available in Hive 0.13.0 and later)
 
-array\_type
-  : ARRAY &lt; data\_type &gt;
+array_type
+  : ARRAY &lt; data_type &gt;
 
-map\_type
-  : MAP &lt; primitive\_type, data\_type &gt;
+map_type
+  : MAP &lt; primitive_type, data_type &gt;
 
-struct\_type
-  : STRUCT &lt; col\_name : data\_type [COMMENT col\_comment], ...&gt;
+struct_type
+  : STRUCT &lt; col_name : data_type [COMMENT col_comment], ...&gt;
 
-union\_type
-   : UNIONTYPE &lt; data\_type, data\_type, ... &gt;  -- (Note: Available in Hive 0.7.0 and later)
+union_type
+   : UNIONTYPE &lt; data_type, data_type, ... &gt;  -- (Note: Available in Hive 0.7.0 and later)
 
-row\_format
+row_format
   : DELIMITED [FIELDS TERMINATED BY char [ESCAPED BY char]] [COLLECTION ITEMS TERMINATED BY char]
         [MAP KEYS TERMINATED BY char] [LINES TERMINATED BY char]
         [NULL DEFINED AS char]   -- (Note: Available in Hive 0.13 and later)
-  | SERDE serde\_name [WITH SERDEPROPERTIES (property\_name=property\_value, property\_name=property\_value, ...)]
+  | SERDE serde_name [WITH SERDEPROPERTIES (property_name=property_value, property_name=property_value, ...)]
 
-file\_format:
+file_format:
   : SEQUENCEFILE
   | TEXTFILE    -- (Default, depending on hive.default.fileformat configuration)
   | RCFILE      -- (Note: Available in Hive 0.6.0 and later)
@@ -361,20 +361,20 @@ file\_format:
   | PARQUET     -- (Note: Available in Hive 0.13.0 and later)
   | AVRO        -- (Note: Available in Hive 0.14.0 and later)
   | JSONFILE    -- (Note: Available in Hive 4.0.0 and later)
-  | INPUTFORMAT input\_format\_classname OUTPUTFORMAT output\_format\_classname
+  | INPUTFORMAT input_format_classname OUTPUTFORMAT output_format_classname
 
-column\_constraint\_specification:
-  : [ PRIMARY KEY|UNIQUE|NOT NULL|DEFAULT [default\_value]|CHECK  [check\_expression] ENABLE|DISABLE NOVALIDATE RELY/NORELY ]
+column_constraint_specification:
+  : [ PRIMARY KEY|UNIQUE|NOT NULL|DEFAULT [default_value]|CHECK  [check_expression] ENABLE|DISABLE NOVALIDATE RELY/NORELY ]
 
-default\_value:
-  : [ LITERAL|CURRENT\_USER()|CURRENT\_DATE()|CURRENT\_TIMESTAMP()|NULL ]  
+default_value:
+  : [ LITERAL|CURRENT_USER()|CURRENT_DATE()|CURRENT_TIMESTAMP()|NULL ]  
 
-constraint\_specification:
-  : [, PRIMARY KEY (col\_name, ...) DISABLE NOVALIDATE RELY/NORELY ]
-    [, PRIMARY KEY (col\_name, ...) DISABLE NOVALIDATE RELY/NORELY ]
-    [, CONSTRAINT constraint\_name FOREIGN KEY (col\_name, ...) REFERENCES table\_name(col\_name, ...) DISABLE NOVALIDATE 
-    [, CONSTRAINT constraint\_name UNIQUE (col\_name, ...) DISABLE NOVALIDATE RELY/NORELY ]
-    [, CONSTRAINT constraint\_name CHECK [check\_expression] ENABLE|DISABLE NOVALIDATE RELY/NORELY ]
+constraint_specification:
+  : [, PRIMARY KEY (col_name, ...) DISABLE NOVALIDATE RELY/NORELY ]
+    [, PRIMARY KEY (col_name, ...) DISABLE NOVALIDATE RELY/NORELY ]
+    [, CONSTRAINT constraint_name FOREIGN KEY (col_name, ...) REFERENCES table_name(col_name, ...) DISABLE NOVALIDATE 
+    [, CONSTRAINT constraint_name UNIQUE (col_name, ...) DISABLE NOVALIDATE RELY/NORELY ]
+    [, CONSTRAINT constraint_name CHECK [check_expression] ENABLE|DISABLE NOVALIDATE RELY/NORELY ]
 </code></pre><p>CREATE TABLE creates a table with the given name. An error is thrown if a table or view with the same name already exists. You can use IF NOT EXISTS to skip the error.</p>
 <ul>
 <li>Table names and column names are case insensitive but SerDe and property names are case sensitive.
@@ -385,7 +385,7 @@ constraint\_specification:
 </ul>
 </li>
 <li>Table and column comments are string literals (single-quoted).</li>
-<li>A table created without the <a href=#external-clause>EXTERNAL clause</a> is called a <em><a href=#managed-table>managed table</a></em> because Hive manages its data. To find out if a table is managed or external, look for tableType in the output of <a href=#describe-extended-table\_name>DESCRIBE EXTENDED table_name</a>.</li>
+<li>A table created without the <a href=#external-clause>EXTERNAL clause</a> is called a <em><a href=#managed-table>managed table</a></em> because Hive manages its data. To find out if a table is managed or external, look for tableType in the output of <a href=#describe-extended-table_name>DESCRIBE EXTENDED table_name</a>.</li>
 <li>The TBLPROPERTIES clause allows you to tag the table definition with your own metadata key/value pairs. Some predefined table properties also exist, such as last_modified_user and last_modified_time which are automatically added and managed by Hive. Other predefined table properties include:
 <ul>
 <li>TBLPROPERTIES (&ldquo;comment&rdquo;="<em>table_comment</em>")</li>
@@ -406,7 +406,7 @@ constraint\_specification:
 <li>TBLPROPERTIES (&ldquo;external.table.purge&rdquo;=&ldquo;true&rdquo;) in release 4.0.0+ (<a href=https://issues.apache.org/jira/browse/HIVE-19981>HIVE-19981</a>) when set on external table would delete the data as well.</li>
 </ul>
 </li>
-<li>To specify a database for the table, either issue the <a href=#use-database\_name>USE database_name</a> statement prior to the CREATE TABLE statement (in <a href=https://issues.apache.org/jira/browse/HIVE-675>Hive 0.6</a> and later) or qualify the table name with a database name ("<code>database_name.table.name</code>" in <a href=https://issues.apache.org/jira/browse/HIVE-1517>Hive 0.7</a> and later).<br>
+<li>To specify a database for the table, either issue the <a href=#use-database_name>USE database_name</a> statement prior to the CREATE TABLE statement (in <a href=https://issues.apache.org/jira/browse/HIVE-675>Hive 0.6</a> and later) or qualify the table name with a database name ("<code>database_name.table.name</code>" in <a href=https://issues.apache.org/jira/browse/HIVE-1517>Hive 0.7</a> and later).<br>
 The keyword &ldquo;<code>default</code>&rdquo; can be used for the default database.</li>
 </ul>
 <p>See <a href=https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-AlterTable>Alter Table</a> below for more information about table comments, table properties, and SerDe properties.</p>
@@ -508,7 +508,7 @@ name   varchar
 
 </code></pre><p>Now you want to partition on date. Your Hive definition could use &ldquo;dtDontQuery&rdquo; as a column name so that &ldquo;date&rdquo; can be used for partitioning (and querying).</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>create table table\_name (
+<pre tabindex=0><code>create table table_name (
   id                int,
   dtDontQuery       string,
   name              string
@@ -518,8 +518,8 @@ partitioned by (date string)
 </code></pre><p>Now your users will still query on &ldquo;<code>where date = '...'</code>&rdquo; but the second column dtDontQuery will hold the original values.</p>
 <p>Here&rsquo;s an example statement to create a partitioned table:</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE TABLE page\_view(viewTime INT, userid BIGINT,
-     page\_url STRING, referrer\_url STRING,
+<pre tabindex=0><code>CREATE TABLE page_view(viewTime INT, userid BIGINT,
+     page_url STRING, referrer_url STRING,
      ip STRING COMMENT 'IP Address of the User')
  COMMENT 'This is the page view table'
  PARTITIONED BY(dt STRING, country STRING)
@@ -527,8 +527,8 @@ partitioned by (date string)
 
 </code></pre><p>The statement above creates the page_view table with viewTime, userid, page_url, referrer_url, and ip columns (including comments). The table is also partitioned and data is stored in sequence files. The data format in the files is assumed to be field-delimited by ctrl-A and row-delimited by newline.</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE TABLE page\_view(viewTime INT, userid BIGINT,
-     page\_url STRING, referrer\_url STRING,
+<pre tabindex=0><code>CREATE TABLE page_view(viewTime INT, userid BIGINT,
+     page_url STRING, referrer_url STRING,
      ip STRING COMMENT 'IP Address of the User')
  COMMENT 'This is the page view table'
  PARTITIONED BY(dt STRING, country STRING)
@@ -546,14 +546,14 @@ Closed</p>
 <p> ) setting table property external.table.purge=true, will also delete the data.</p>
 <p>An EXTERNAL table points to any HDFS location for its storage, rather than being stored in a folder specified by the configuration property <code>[hive.metastore.warehouse.dir](#hive-metastore-warehouse-dir)</code>.</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE EXTERNAL TABLE page\_view(viewTime INT, userid BIGINT,
-     page\_url STRING, referrer\_url STRING,
+<pre tabindex=0><code>CREATE EXTERNAL TABLE page_view(viewTime INT, userid BIGINT,
+     page_url STRING, referrer_url STRING,
      ip STRING COMMENT 'IP Address of the User',
      country STRING COMMENT 'country of origination')
  COMMENT 'This is the staging page view table'
  ROW FORMAT DELIMITED FIELDS TERMINATED BY '\054'
  STORED AS TEXTFILE
- LOCATION '&lt;hdfs\_location&gt;';
+ LOCATION '&lt;hdfs_location&gt;';
 
 </code></pre><p>You can use the above statement to create a page_view table which points to any HDFS location for its storage. But you still have to make sure that the data is delimited as specified in the CREATE statement above.</p>
 <p>For another example of creating an external table, see <a href=#loading-data>Loading Data</a> in the Tutorial.</p>
@@ -567,27 +567,27 @@ Closed</p>
 <li>The target table cannot be a list bucketing table.</li>
 </ul>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE TABLE new\_key\_value\_store
+<pre tabindex=0><code>CREATE TABLE new_key_value_store
    ROW FORMAT SERDE &quot;org.apache.hadoop.hive.serde2.columnar.ColumnarSerDe&quot;
    STORED AS RCFile
    AS
-SELECT (key % 1024) new\_key, concat(key, value) key\_value\_pair
-FROM key\_value\_store
-SORT BY new\_key, key\_value\_pair;
+SELECT (key % 1024) new_key, concat(key, value) key_value_pair
+FROM key_value_store
+SORT BY new_key, key_value_pair;
 
 </code></pre><p>The above CTAS statement creates the target table new_key_value_store with the schema (new_key DOUBLE, key_value_pair STRING) derived from the results of the SELECT statement. If the SELECT statement does not specify column aliases, the column names will be automatically assigned to _col0, _col1, and _col2 etc. In addition, the new target table is created using a specific SerDe and a storage format independent of the source tables in the SELECT statement.</p>
 <p>Starting with <a href=https://issues.apache.org/jira/browse/HIVE-1180>Hive 0.13.0</a>, the SELECT statement can include one or more common table expressions (CTEs), as shown in the <a href=#select-syntax>SELECT syntax</a>. For an example, see <a href=#common-table-expression>Common Table Expression</a>.</p>
 <p>Being able to select data from one table to another is one of the most powerful features of Hive. Hive handles the conversion of the data from the source format to the destination format as the query is being executed.</p>
 <h4 id=create-table-like>Create Table Like</h4>
 <p>The LIKE form of CREATE TABLE allows you to copy an existing table definition exactly (without copying its data). In contrast to CTAS, the statement below creates a new empty_key_value_store table whose definition exactly matches the existing key_value_store in all particulars other than table name. The new table contains no rows.</p>
-<pre tabindex=0><code>CREATE TABLE empty\_key\_value\_store
-LIKE key\_value\_store [TBLPROPERTIES (property\_name=property\_value, ...)];
+<pre tabindex=0><code>CREATE TABLE empty_key_value_store
+LIKE key_value_store [TBLPROPERTIES (property_name=property_value, ...)];
 
 </code></pre><p>Before Hive 0.8.0, CREATE TABLE LIKE view_name would make a copy of the view. In Hive 0.8.0 and later releases, CREATE TABLE LIKE view_name creates a table by adopting the schema of view_name (fields and partition columns) using defaults for SerDe and file formats.</p>
 <h4 id=bucketed-sorted-tables>Bucketed Sorted Tables</h4>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE TABLE page\_view(viewTime INT, userid BIGINT,
-     page\_url STRING, referrer\_url STRING,
+<pre tabindex=0><code>CREATE TABLE page_view(viewTime INT, userid BIGINT,
+     page_url STRING, referrer_url STRING,
      ip STRING COMMENT 'IP Address of the User')
  COMMENT 'This is the page view table'
  PARTITIONED BY(dt STRING, country STRING)
@@ -610,12 +610,12 @@ LIKE key\_value\_store [TBLPROPERTIES (property\_name=property\_value, ...)];
 <p>This can be specified on a per-table level during table creation.</p>
 <p>The following example shows one column with three skewed values, optionally with the STORED AS DIRECTORIES clause which specifies list bucketing.</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE TABLE list\_bucket\_single (key STRING, value STRING)
+<pre tabindex=0><code>CREATE TABLE list_bucket_single (key STRING, value STRING)
   SKEWED BY (key) ON (1,5,6) [STORED AS DIRECTORIES];
 
 </code></pre><p>And here is an example of a table with two skewed columns.</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE TABLE list\_bucket\_multiple (col1 STRING, col2 int, col3 STRING)
+<pre tabindex=0><code>CREATE TABLE list_bucket_multiple (col1 STRING, col2 int, col3 STRING)
   SKEWED BY (col1, col2) ON (('s1',1), ('s3',3), ('s13',13), ('s78',78)) [STORED AS DIRECTORIES];
 
 </code></pre><p>For corresponding ALTER TABLE statements, see <a href=#alter-table-skewed-or-stored-as-directories>Alter Table Skewed or Stored as Directories</a> below.</p>
@@ -631,14 +631,14 @@ LIKE key\_value\_store [TBLPROPERTIES (property\_name=property\_value, ...)];
 </ul>
 <p>Starting in <a href=https://issues.apache.org/jira/browse/HIVE-7313>Hive 1.1.0</a> the storage policy for temporary tables can be set to <code>memory</code>, <code>ssd</code>, or <code>default</code> with the <a href=#hive-exec-temporary-table-storage>hive.exec.temporary.table.storage</a> configuration parameter (see <a href=http://hadoop.apache.org/docs/r2.6.0/hadoop-project-dist/hadoop-hdfs/ArchivalStorage.html#Storage_Types_and_Storage_Policies>HDFS Storage Types and Storage Polici [...]
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE TEMPORARY TABLE list\_bucket\_multiple (col1 STRING, col2 int, col3 STRING);
+<pre tabindex=0><code>CREATE TEMPORARY TABLE list_bucket_multiple (col1 STRING, col2 int, col3 STRING);
 
 </code></pre><h4 id=transactional-tables>Transactional Tables</h4>
 <p>Version information</p>
 <p>As of Hive 4.0 (<a href=https://issues.apache.org/jira/browse/HIVE-18453>HIVE-18453</a>).</p>
 <p>A table that supports operations with ACID semantics. See <a href=https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions>this</a> for more details about transactional tables.</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE TRANSACTIONAL TABLE transactional\_table\_test(key string, value string) PARTITIONED BY(ds string) STORED AS ORC;
+<pre tabindex=0><code>CREATE TRANSACTIONAL TABLE transactional_table_test(key string, value string) PARTITIONED BY(ds string) STORED AS ORC;
 </code></pre><h4 id=constraints>Constraints</h4>
 <p>Version information</p>
 <p>As of Hive 2.1.0 (<a href=https://issues.apache.org/jira/browse/HIVE-13290>HIVE-13290</a>).</p>
@@ -655,17 +655,17 @@ create table fk(id1 integer, id2 integer,
 <p>Hive includes support for UNIQUE, NOT NULL, DEFAULT and CHECK constraints. Beside UNIQUE all three type of constraints are enforced.</p>
 <p><strong>Example:</strong></p>
 <pre tabindex=0><code>create table constraints1(id1 integer UNIQUE disable novalidate, id2 integer NOT NULL, 
-  usr string DEFAULT current\_user(), price double CHECK (price &gt; 0 AND price &lt;= 1000));
+  usr string DEFAULT current_user(), price double CHECK (price &gt; 0 AND price &lt;= 1000));
 
 create table constraints2(id1 integer, id2 integer,
-  constraint c1\_unique UNIQUE(id1) disable novalidate);
+  constraint c1_unique UNIQUE(id1) disable novalidate);
 
 create table constraints3(id1 integer, id2 integer,
-  constraint c1\_check CHECK(id1 + id2 &gt; 0));
+  constraint c1_check CHECK(id1 + id2 &gt; 0));
 
 </code></pre><p>DEFAULT on complex data types such as map, struct, array is not supported.</p>
 <h3 id=drop-table>Drop Table</h3>
-<pre tabindex=0><code>DROP TABLE [IF EXISTS] table\_name [PURGE];     -- (Note: PURGE available in Hive 0.14.0 and later)
+<pre tabindex=0><code>DROP TABLE [IF EXISTS] table_name [PURGE];     -- (Note: PURGE available in Hive 0.14.0 and later)
 
 </code></pre><p>DROP TABLE removes metadata and data for this table. The data is actually moved to the .Trash/Current directory if Trash is configured (and PURGE is not specified). The metadata is completely lost.</p>
 <p>When dropping an EXTERNAL table, data in the table will <em>NOT</em> be deleted from the file system. Starting Hive 4.0.0 (</p>
@@ -683,10 +683,10 @@ Closed</p>
 <h3 id=truncate-table>Truncate Table</h3>
 <p>Version information</p>
 <p>As of Hive 0.11.0 (<a href=https://issues.apache.org/jira/browse/HIVE-446>HIVE-446</a>).</p>
-<pre tabindex=0><code>TRUNCATE [TABLE] table\_name [PARTITION partition\_spec];
+<pre tabindex=0><code>TRUNCATE [TABLE] table_name [PARTITION partition_spec];
 
-partition\_spec:
-  : (partition\_column = partition\_col\_value, partition\_column = partition\_col\_value, ...)
+partition_spec:
+  : (partition_column = partition_col_value, partition_column = partition_col_value, ...)
 
 </code></pre><p>Removes all rows from a table or partition(s). The rows will be trashed if the filesystem Trash is enabled, otherwise they are deleted (as of Hive 2.2.0 with <a href=https://issues.apache.org/jira/browse/HIVE-14626>HIVE-14626</a>). Currently the target table should be native/managed table or an exception will be thrown. User can specify partial partition_spec for truncating multiple partitions at once and omitting partition_spec will truncate all partitions in the table.</p>
 <p>Starting with HIVE 2.3.0 (<a href=https://issues.apache.org/jira/browse/HIVE-15880>HIVE-15880</a>) if the table property &ldquo;auto.purge&rdquo; (see <a href=#tblproperties>TBLPROPERTIES</a> above) is set to &ldquo;true&rdquo; the data of the table is not moved to Trash when a TRUNCATE TABLE command is issued against it and cannot be retrieved in the event of a mistaken TRUNCATE. This is applicable only for managed tables (see <a href=#managed-tables>managed tables</a>). This behavio [...]
@@ -755,49 +755,49 @@ partition\_spec:
 <p>Alter table statements enable you to change the structure of an existing table. You can add columns/partitions, change SerDe, add table and SerDe properties, or rename the table itself. Similarly, alter table partition statements allow you change the properties of a specific partition in the named table.</p>
 <h3 id=alter-table>Alter Table</h3>
 <h4 id=rename-table>Rename Table</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name RENAME TO new\_table\_name;
+<pre tabindex=0><code>ALTER TABLE table_name RENAME TO new_table_name;
 
 </code></pre><p>This statement lets you change the name of a table to a different name.</p>
 <p>As of version 0.6, a rename on a <a href=#managed-table>managed table</a> moves its HDFS location. Rename has been changed as of version 2.2.0 (<a href=https://issues.apache.org/jira/browse/HIVE-14909>HIVE-14909</a>) so that a managed table&rsquo;s HDFS location is moved only if the table is created without a <a href=#location-clause>LOCATION clause</a> and under its database directory. Hive versions prior to 0.6 just renamed the table in the metastore without moving the HDFS location.</p>
 <h4 id=alter-table-properties>Alter Table Properties</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name SET TBLPROPERTIES table\_properties;
+<pre tabindex=0><code>ALTER TABLE table_name SET TBLPROPERTIES table_properties;
 
-table\_properties:
-  : (property\_name = property\_value, property\_name = property\_value, ... )
+table_properties:
+  : (property_name = property_value, property_name = property_value, ... )
 
 </code></pre><p>You can use this statement to add your own metadata to the tables. Currently last_modified_user, last_modified_time properties are automatically added and managed by Hive. Users can add their own properties to this list. You can do DESCRIBE EXTENDED TABLE to get this information.</p>
 <p>For more information, see the <a href=#tblproperties-clause>TBLPROPERTIES clause</a> in Create Table above.</p>
 <h5 id=alter-table-comment>Alter Table Comment</h5>
 <p>To change the comment of a table you have to change the <code>comment</code> property of the <code>TBLPROPERTIES</code>:</p>
-<pre tabindex=0><code>ALTER TABLE table\_name SET TBLPROPERTIES ('comment' = new\_comment);
+<pre tabindex=0><code>ALTER TABLE table_name SET TBLPROPERTIES ('comment' = new_comment);
 
 </code></pre><h4 id=add-serde-properties>Add SerDe Properties</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name [PARTITION partition\_spec] SET SERDE serde\_class\_name [WITH SERDEPROPERTIES serde\_properties];
+<pre tabindex=0><code>ALTER TABLE table_name [PARTITION partition_spec] SET SERDE serde_class_name [WITH SERDEPROPERTIES serde_properties];
 
-ALTER TABLE table\_name [PARTITION partition\_spec] SET SERDEPROPERTIES serde\_properties;
+ALTER TABLE table_name [PARTITION partition_spec] SET SERDEPROPERTIES serde_properties;
 
-serde\_properties:
-  : (property\_name = property\_value, property\_name = property\_value, ... )
+serde_properties:
+  : (property_name = property_value, property_name = property_value, ... )
 
 </code></pre><p>These statements enable you to change a table&rsquo;s SerDe or add user-defined metadata to the table&rsquo;s SerDe object.</p>
 <p>The SerDe properties are passed to the table&rsquo;s SerDe when it is being initialized by Hive to serialize and deserialize data. So users can store any information required for their custom SerDe here. Refer to the <a href=https://hive.apache.org/docs/latest/serde_27362059/>SerDe documentation</a> and <a href=#hive-serde>Hive SerDe</a> in the Developer Guide for more information, and see <a href=#row-format,-storage-format,-and-serde>Row Format, Storage Format, and SerDe</a> above f [...]
 <p>Note that both <code>property_name</code> and <code>property_value</code> must be quoted.</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>ALTER TABLE table\_name SET SERDEPROPERTIES ('field.delim' = ',');
+<pre tabindex=0><code>ALTER TABLE table_name SET SERDEPROPERTIES ('field.delim' = ',');
 
 </code></pre><h4 id=remove-serde-properties>Remove SerDe Properties</h4>
 <p>Version information</p>
 <p>Remove SerDe Properties is supported as of Hive 4.0.0 (<a href=https://issues.apache.org/jira/browse/HIVE-18842>HIVE-21952</a>).</p>
-<pre tabindex=0><code>ALTER TABLE table\_name [PARTITION partition\_spec] UNSET SERDEPROPERTIES (property\_name, ... );
+<pre tabindex=0><code>ALTER TABLE table_name [PARTITION partition_spec] UNSET SERDEPROPERTIES (property_name, ... );
 
 </code></pre><p>These statements enable you to remove user-defined metadata to the table&rsquo;s SerDe object.</p>
 <p>Note that <code>property_name</code> must be quoted.</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>ALTER TABLE table\_name UNSET SERDEPROPERTIES ('field.delim');
+<pre tabindex=0><code>ALTER TABLE table_name UNSET SERDEPROPERTIES ('field.delim');
 
 </code></pre><h4 id=alter-table-storage-properties>Alter Table Storage Properties</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name CLUSTERED BY (col\_name, col\_name, ...) [SORTED BY (col\_name, ...)]
-  INTO num\_buckets BUCKETS;
+<pre tabindex=0><code>ALTER TABLE table_name CLUSTERED BY (col_name, col_name, ...) [SORTED BY (col_name, ...)]
+  INTO num_buckets BUCKETS;
 
 </code></pre><p>These statements change the table&rsquo;s physical storage properties.</p>
 <p>NOTE: These commands will only modify Hive&rsquo;s metadata, and will <em>NOT</em> reorganize or reformat existing data. Users should make sure the actual data layout conforms with the metadata definition.</p>
@@ -806,31 +806,31 @@ serde\_properties:
 <p>As of Hive 0.10.0 (<a href=https://issues.apache.org/jira/browse/HIVE-3072>HIVE-3072</a> and <a href=https://issues.apache.org/jira/browse/HIVE-3649>HIVE-3649</a>). See <a href=https://issues.apache.org/jira/browse/HIVE-3026>HIVE-3026</a> for additional JIRA tickets that implemented list bucketing in Hive 0.10.0 and 0.11.0.</p>
 <p>A table&rsquo;s SKEWED and STORED AS DIRECTORIES options can be changed with ALTER TABLE statements. See <a href=#skewed-tables>Skewed Tables</a> above for the corresponding CREATE TABLE syntax.</p>
 <h5 id=alter-table-skewed>Alter Table Skewed</h5>
-<pre tabindex=0><code>ALTER TABLE table\_name SKEWED BY (col\_name1, col\_name2, ...)
-  ON ([(col\_name1\_value, col\_name2\_value, ...) [, (col\_name1\_value, col\_name2\_value), ...]
+<pre tabindex=0><code>ALTER TABLE table_name SKEWED BY (col_name1, col_name2, ...)
+  ON ([(col_name1_value, col_name2_value, ...) [, (col_name1_value, col_name2_value), ...]
   [STORED AS DIRECTORIES];
 </code></pre><p>The STORED AS DIRECTORIES option determines whether a <a href=https://hive.apache.org/docs/latest/skewed-join-optimization_27847852/>skewed</a> table uses the <a href=https://hive.apache.org/docs/latest/listbucketing_27846854/>list bucketing</a> feature, which creates subdirectories for skewed values.</p>
 <h5 id=alter-table-not-skewed>Alter Table Not Skewed</h5>
-<pre tabindex=0><code>ALTER TABLE table\_name NOT SKEWED;
+<pre tabindex=0><code>ALTER TABLE table_name NOT SKEWED;
 </code></pre><p>The NOT SKEWED option makes the table non-skewed and turns off the list bucketing feature (since a list-bucketing table is always skewed). This affects partitions created after the ALTER statement, but has no effect on partitions created before the ALTER statement.</p>
 <h5 id=alter-table-not-stored-as-directories>Alter Table Not Stored as Directories</h5>
-<pre tabindex=0><code>ALTER TABLE table\_name NOT STORED AS DIRECTORIES;
+<pre tabindex=0><code>ALTER TABLE table_name NOT STORED AS DIRECTORIES;
 </code></pre><p>This turns off the list bucketing feature, although the table remains skewed.</p>
 <h5 id=alter-table-set-skewed-location>Alter Table Set Skewed Location</h5>
-<pre tabindex=0><code>ALTER TABLE table\_name SET SKEWED LOCATION (col\_name1=&quot;location1&quot; [, col\_name2=&quot;location2&quot;, ...] );
+<pre tabindex=0><code>ALTER TABLE table_name SET SKEWED LOCATION (col_name1=&quot;location1&quot; [, col_name2=&quot;location2&quot;, ...] );
 </code></pre><p>This changes the location map for list bucketing.</p>
 <h4 id=alter-table-constraints>Alter Table Constraints</h4>
 <p>Version information</p>
 <p>As of Hive release <a href=https://issues.apache.org/jira/browse/HIVE-13290>2.1.0</a>.</p>
 <p> Table constraints can be added or removed via ALTER TABLE statements.</p>
-<pre tabindex=0><code>ALTER TABLE table\_name ADD CONSTRAINT constraint\_name PRIMARY KEY (column, ...) DISABLE NOVALIDATE;
-ALTER TABLE table\_name ADD CONSTRAINT constraint\_name FOREIGN KEY (column, ...) REFERENCES table\_name(column, ...) DISABLE NOVALIDATE RELY;
-ALTER TABLE table\_name ADD CONSTRAINT constraint\_name UNIQUE (column, ...) DISABLE NOVALIDATE;
-ALTER TABLE table\_name CHANGE COLUMN column\_name column\_name data\_type CONSTRAINT constraint\_name NOT NULL ENABLE;
-ALTER TABLE table\_name CHANGE COLUMN column\_name column\_name data\_type CONSTRAINT constraint\_name DEFAULT default\_value ENABLE;
-ALTER TABLE table\_name CHANGE COLUMN column\_name column\_name data\_type CONSTRAINT constraint\_name CHECK check\_expression ENABLE;
-
-ALTER TABLE table\_name DROP CONSTRAINT constraint\_name;
+<pre tabindex=0><code>ALTER TABLE table_name ADD CONSTRAINT constraint_name PRIMARY KEY (column, ...) DISABLE NOVALIDATE;
+ALTER TABLE table_name ADD CONSTRAINT constraint_name FOREIGN KEY (column, ...) REFERENCES table_name(column, ...) DISABLE NOVALIDATE RELY;
+ALTER TABLE table_name ADD CONSTRAINT constraint_name UNIQUE (column, ...) DISABLE NOVALIDATE;
+ALTER TABLE table_name CHANGE COLUMN column_name column_name data_type CONSTRAINT constraint_name NOT NULL ENABLE;
+ALTER TABLE table_name CHANGE COLUMN column_name column_name data_type CONSTRAINT constraint_name DEFAULT default_value ENABLE;
+ALTER TABLE table_name CHANGE COLUMN column_name column_name data_type CONSTRAINT constraint_name CHECK check_expression ENABLE;
+
+ALTER TABLE table_name DROP CONSTRAINT constraint_name;
 </code></pre><h4 id=additional-alter-table-statements>Additional Alter Table Statements</h4>
 <p>See <a href=#alter-either-table-or-partition>Alter Either Table or Partition</a> below for more DDL statements that alter tables.</p>
 <h3 id=alter-partition>Alter Partition</h3>
@@ -838,25 +838,25 @@ ALTER TABLE table\_name DROP CONSTRAINT constraint\_name;
 <p>Version 1.2+</p>
 <p>As of Hive 1.2 (<a href=https://issues.apache.org/jira/browse/HIVE-10307>HIVE-10307</a>), the partition values specified in partition specification are type checked, converted, and normalized to conform to their column types if the property <a href=#hive-typecheck-on-insert>hive.typecheck.on.insert</a> is set to true (default). The values can be number literals.</p>
 <h4 id=add-partitions>Add Partitions</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name ADD [IF NOT EXISTS] PARTITION partition\_spec [LOCATION 'location'][, PARTITION partition\_spec [LOCATION 'location'], ...];
+<pre tabindex=0><code>ALTER TABLE table_name ADD [IF NOT EXISTS] PARTITION partition_spec [LOCATION 'location'][, PARTITION partition_spec [LOCATION 'location'], ...];
 
-partition\_spec:
-  : (partition\_column = partition\_col\_value, partition\_column = partition\_col\_value, ...)
+partition_spec:
+  : (partition_column = partition_col_value, partition_column = partition_col_value, ...)
 
 </code></pre><p>You can use ALTER TABLE ADD PARTITION to add partitions to a table. Partition values should be quoted only if they are strings. The location must be a directory inside of which data files reside. (ADD PARTITION changes the table metadata, but does not load data. If the data does not exist in the partition&rsquo;s location, queries will not return any results.) An error is thrown if the partition_spec for the table already exists. You can use IF NOT EXISTS to skip the error.</p>
 <p>Version 0.7</p>
 <p>Although it is proper syntax to have multiple partition_spec in a single ALTER TABLE, if you do this in version 0.7 your partitioning scheme will fail. That is, every query specifying a partition will always use only the first partition.</p>
 <p>Specifically, the following example will FAIL silently and without error in Hive 0.7, and all queries will go only to dt=&lsquo;2008-08-08&rsquo; partition, no matter which partition you specify.</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>ALTER TABLE page\_view ADD PARTITION (dt='2008-08-08', country='us') location '/path/to/us/part080808'
+<pre tabindex=0><code>ALTER TABLE page_view ADD PARTITION (dt='2008-08-08', country='us') location '/path/to/us/part080808'
                           PARTITION (dt='2008-08-09', country='us') location '/path/to/us/part080809';
 
 </code></pre><p>In Hive 0.8 and later, you can add multiple partitions in a single ALTER TABLE statement as shown in the previous example.</p>
 <p>In Hive 0.7, if you want to add many partitions you should use the following form:</p>
-<pre tabindex=0><code>ALTER TABLE table\_name ADD PARTITION (partCol = 'value1') location 'loc1';
-ALTER TABLE table\_name ADD PARTITION (partCol = 'value2') location 'loc2';
+<pre tabindex=0><code>ALTER TABLE table_name ADD PARTITION (partCol = 'value1') location 'loc1';
+ALTER TABLE table_name ADD PARTITION (partCol = 'value2') location 'loc2';
 ...
-ALTER TABLE table\_name ADD PARTITION (partCol = 'valueN') location 'locN';
+ALTER TABLE table_name ADD PARTITION (partCol = 'valueN') location 'locN';
 </code></pre><h5 id=dynamic-partitions>Dynamic Partitions</h5>
 <p>Partitions can be added to a table dynamically, using a Hive INSERT statement (or a Pig STORE statement). See these documents for details and examples:</p>
 <ul>
@@ -873,17 +873,17 @@ ALTER TABLE table\_name ADD PARTITION (partCol = 'valueN') location 'locN';
 <h4 id=rename-partition>Rename Partition</h4>
 <p>Version information</p>
 <p>As of Hive 0.9.</p>
-<pre tabindex=0><code>ALTER TABLE table\_name PARTITION partition\_spec RENAME TO PARTITION partition\_spec;
+<pre tabindex=0><code>ALTER TABLE table_name PARTITION partition_spec RENAME TO PARTITION partition_spec;
 
 </code></pre><p>This statement lets you change the value of a partition column. One of use cases is that you can use this statement to normalize your legacy partition column value to conform to its type. In this case, the type conversion and normalization are not enabled for the column values in old <em>partition_spec</em> even with property <a href=#hive-typecheck-on-insert>hive.typecheck.on.insert</a> set to true (default) which allows you to specify any legacy data in form of string i [...]
 <h4 id=exchange-partition>Exchange Partition</h4>
 <p>Partitions can be exchanged (moved) between tables.</p>
 <p>Version information</p>
 <p>As of Hive 0.12 (<a href=https://issues.apache.org/jira/browse/HIVE-4095>HIVE-4095</a>). Multiple partitions supported in Hive versions <a href=https://issues.apache.org/jira/browse/HIVE-11745>1.2.2, 1.3.0, and 2.0.0+</a>.</p>
-<pre tabindex=0><code>-- Move partition from table\_name\_1 to table\_name\_2
-ALTER TABLE table\_name\_2 EXCHANGE PARTITION (partition\_spec) WITH TABLE table\_name\_1;
+<pre tabindex=0><code>-- Move partition from table_name_1 to table_name_2
+ALTER TABLE table_name_2 EXCHANGE PARTITION (partition_spec) WITH TABLE table_name_1;
 -- multiple partitions
-ALTER TABLE table\_name\_2 EXCHANGE PARTITION (partition\_spec, partition\_spec2, ...) WITH TABLE table\_name\_1;
+ALTER TABLE table_name_2 EXCHANGE PARTITION (partition_spec, partition_spec2, ...) WITH TABLE table_name_1;
 </code></pre><p>This statement lets you move the data in a partition from a table to another table that has the same schema and does not already have that partition.<br>
 For further details on this feature, see <a href=https://hive.apache.org/docs/latest/exchange-partition_30755801/>Exchange Partition</a> and <a href=https://issues.apache.org/jira/browse/HIVE-4095>HIVE-4095</a>.</p>
 <h4 id=discover-partitions>Discover Partitions</h4>
@@ -898,47 +898,47 @@ For further details on this feature, see <a href=https://hive.apache.org/docs/la
 <h4 id=recover-partitions-msck-repair-table>Recover Partitions (MSCK REPAIR TABLE)</h4>
 <p>Hive stores a list of partitions for each table in its metastore. If, however, new partitions are directly added to HDFS (say by using <code>hadoop fs -put</code> command) or removed from HDFS, the metastore (and hence Hive) will not be aware of these changes to partition information unless the user runs <code>ALTER TABLE table_name ADD/DROP PARTITION</code> commands on each of the newly added or removed partitions, respectively.</p>
 <p>However, users can run a metastore check command with the repair table option:</p>
-<pre tabindex=0><code>MSCK [REPAIR] TABLE table\_name [ADD/DROP/SYNC PARTITIONS];
+<pre tabindex=0><code>MSCK [REPAIR] TABLE table_name [ADD/DROP/SYNC PARTITIONS];
 
 </code></pre><p>which will update metadata about partitions to the Hive metastore for partitions for which such metadata doesn&rsquo;t already exist. The default option for MSC command is ADD PARTITIONS. With this option, it will add any partitions that exist on HDFS but not in metastore to the metastore. The DROP PARTITIONS option will remove the partition information from metastore, that is already removed from HDFS. The SYNC PARTITIONS option is equivalent to calling both ADD and DROP [...]
 <p>The equivalent command on Amazon Elastic MapReduce (EMR)&rsquo;s version of Hive is:</p>
-<pre tabindex=0><code>ALTER TABLE table\_name RECOVER PARTITIONS;
+<pre tabindex=0><code>ALTER TABLE table_name RECOVER PARTITIONS;
 
 </code></pre><p>Starting with Hive 1.3, MSCK will throw exceptions if directories with disallowed characters in partition values are found on HDFS. Use <strong>hive.msck.path.validation</strong> setting on the client to alter this behavior; &ldquo;skip&rdquo; will simply skip the directories. &ldquo;ignore&rdquo; will try to create partitions anyway (old behavior). This may or may not work.</p>
 <h4 id=drop-partitions>Drop Partitions</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name DROP [IF EXISTS] PARTITION partition\_spec[, PARTITION partition\_spec, ...]
+<pre tabindex=0><code>ALTER TABLE table_name DROP [IF EXISTS] PARTITION partition_spec[, PARTITION partition_spec, ...]
   [IGNORE PROTECTION] [PURGE];            -- (Note: PURGE available in Hive 1.2.0 and later, IGNORE PROTECTION not available 2.0.0 and later)
 
 </code></pre><p>You can use ALTER TABLE DROP PARTITION to drop a partition for a table. This removes the data and metadata for this partition. The data is actually moved to the .Trash/Current directory if Trash is configured, unless PURGE is specified, but the metadata is completely lost (see <a href=#drop-table>Drop Table</a> above).</p>
 <p>Version Information: PROTECTION</p>
 <p>IGNORE PROTECTION is no longer available in versions 2.0.0 and later. This functionality is replaced by using one of the several security options available with Hive (see <a href=https://hive.apache.org/docs/latest/sql-standard-based-hive-authorization_40509928/>SQL Standard Based Hive Authorization</a>). See <a href=https://issues.apache.org/jira/browse/HIVE-11145>HIVE-11145</a> for details.</p>
-<p>For tables that are protected by <a href=#no\_drop-cascade>NO_DROP CASCADE</a>, you can use the predicate IGNORE PROTECTION to drop a specified partition or set of partitions (for example, when splitting a table between two Hadoop clusters):</p>
-<pre tabindex=0><code>ALTER TABLE table\_name DROP [IF EXISTS] PARTITION partition\_spec IGNORE PROTECTION;
+<p>For tables that are protected by <a href=#no_drop-cascade>NO_DROP CASCADE</a>, you can use the predicate IGNORE PROTECTION to drop a specified partition or set of partitions (for example, when splitting a table between two Hadoop clusters):</p>
+<pre tabindex=0><code>ALTER TABLE table_name DROP [IF EXISTS] PARTITION partition_spec IGNORE PROTECTION;
 
 </code></pre><p>The above command will drop that partition regardless of protection stats.</p>
 <p>Version information: PURGE</p>
 <p>The PURGE option is added to ALTER TABLE in version 1.2.1 by <a href=https://issues.apache.org/jira/browse/HIVE-10934>HIVE-10934</a>.</p>
 <p>If PURGE is specified, the partition data does not go to the .Trash/Current directory and so cannot be retrieved in the event of a mistaken DROP:</p>
-<pre tabindex=0><code>ALTER TABLE table\_name DROP [IF EXISTS] PARTITION partition\_spec PURGE;     -- (Note: Hive 1.2.0 and later)
+<pre tabindex=0><code>ALTER TABLE table_name DROP [IF EXISTS] PARTITION partition_spec PURGE;     -- (Note: Hive 1.2.0 and later)
 </code></pre><p>The purge option can also be specified with the table property auto.purge (see <a href=#tblproperties>TBLPROPERTIES</a> above).</p>
 <p>In Hive 0.7.0 or later, DROP returns an error if the partition doesn&rsquo;t exist, unless IF EXISTS is specified or the configuration variable <a href=#hive-exec-drop-ignorenonexistent>hive.exec.drop.ignorenonexistent</a> is set to true.</p>
-<pre tabindex=0><code>ALTER TABLE page\_view DROP PARTITION (dt='2008-08-08', country='us');
+<pre tabindex=0><code>ALTER TABLE page_view DROP PARTITION (dt='2008-08-08', country='us');
 
 </code></pre><h4 id=unarchive-partition>(Un)Archive Partition</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name ARCHIVE PARTITION partition\_spec;
-ALTER TABLE table\_name UNARCHIVE PARTITION partition\_spec;
+<pre tabindex=0><code>ALTER TABLE table_name ARCHIVE PARTITION partition_spec;
+ALTER TABLE table_name UNARCHIVE PARTITION partition_spec;
 
 </code></pre><p>Archiving is a feature to moves a partition&rsquo;s files into a Hadoop Archive (HAR). Note that only the file count will be reduced; HAR does not provide any compression. See <a href=https://hive.apache.org/docs/latest/languagemanual-archiving_27362031/>LanguageManual Archiving</a> for more information</p>
 <h3 id=alter-either-table-or-partition>Alter Either Table or Partition</h3>
 <h4 id=alter-tablepartition-file-format>Alter Table/Partition File Format</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name [PARTITION partition\_spec] SET FILEFORMAT file\_format;
+<pre tabindex=0><code>ALTER TABLE table_name [PARTITION partition_spec] SET FILEFORMAT file_format;
 
 </code></pre><p>This statement changes the table&rsquo;s (or partition&rsquo;s) file format. For available file_format options, see the section above on <a href=#create-table>CREATE TABLE</a>. The operation only changes the table metadata. Any conversion of existing data must be done outside of Hive.</p>
 <h4 id=alter-tablepartition-location>Alter Table/Partition Location</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name [PARTITION partition\_spec] SET LOCATION &quot;new location&quot;;
+<pre tabindex=0><code>ALTER TABLE table_name [PARTITION partition_spec] SET LOCATION &quot;new location&quot;;
 
 </code></pre><h4 id=alter-tablepartition-touch>Alter Table/Partition Touch</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name TOUCH [PARTITION partition\_spec];
+<pre tabindex=0><code>ALTER TABLE table_name TOUCH [PARTITION partition_spec];
 
 </code></pre><p>TOUCH reads the metadata, and writes it back. This has the effect of causing the pre/post execute hooks to fire. An example use case is if you have a hook that logs all the tables/partitions that were modified, along with an external script that alters the files on HDFS directly. Since the script modifies files outside of hive, the modification wouldn&rsquo;t be logged by the hook. The external script could call TOUCH to fire the hook and mark the said table or partition  [...]
 <p>Also, it may be useful later if we incorporate reliable last modified times. Then touch would update that time as well.</p>
@@ -947,9 +947,9 @@ ALTER TABLE table\_name UNARCHIVE PARTITION partition\_spec;
 <p>Version information</p>
 <p>As of Hive 0.7.0 (<a href=https://issues.apache.org/jira/browse/HIVE-1413>HIVE-1413</a>). The CASCADE clause for NO_DROP was added in HIVE 0.8.0 (<a href=https://issues.apache.org/jira/browse/HIVE-2605>HIVE-2605</a>).</p>
 <p>This functionality was removed in Hive 2.0.0. This functionality is replaced by using one of the several security options available with Hive (see <a href=https://hive.apache.org/docs/latest/sql-standard-based-hive-authorization_40509928/>SQL Standard Based Hive Authorization</a>). See <a href=https://issues.apache.org/jira/browse/HIVE-11145>HIVE-11145</a> for details.</p>
-<pre tabindex=0><code>ALTER TABLE table\_name [PARTITION partition\_spec] ENABLE|DISABLE NO\_DROP [CASCADE];
+<pre tabindex=0><code>ALTER TABLE table_name [PARTITION partition_spec] ENABLE|DISABLE NO_DROP [CASCADE];
  
-ALTER TABLE table\_name [PARTITION partition\_spec] ENABLE|DISABLE OFFLINE;
+ALTER TABLE table_name [PARTITION partition_spec] ENABLE|DISABLE OFFLINE;
 
 </code></pre><p>Protection on data can be set at either the table or partition level. Enabling NO_DROP prevents a table from being <a href=#dropped>dropped</a>. Enabling OFFLINE prevents the data in a table or partition from being queried, but the metadata can still be accessed.</p>
 <p>If any partition in a table has NO_DROP enabled, the table cannot be dropped either. Conversely, if a table has NO_DROP enabled then partitions may be dropped, but with NO_DROP CASCADE partitions cannot be dropped either unless the <a href=#drop-partition-command>drop partition command</a> specifies IGNORE PROTECTION.</p>
@@ -959,11 +959,11 @@ ALTER TABLE table\_name [PARTITION partition\_spec] ENABLE|DISABLE OFFLINE;
 As of Hive release <a href=https://issues.apache.org/jira/browse/HIVE-13354>1.3.0 and 2.1.0</a> when <a href=https://hive.apache.org/docs/latest/hive-transactions_40509723/>transactions</a> are being used, the ALTER TABLE &mldr; COMPACT statement can include a <a href=https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions#HiveTransactions-TableProperties>TBLPROPERTIES</a> clause that is either to change compaction MapReduce job properties or to overwrite any other Hive table  [...]
 As of Hive release <a href="https://issues.apache.org/jira/browse/HIVE-27056?jql=project%20%3D%20HIVE%20AND%20fixVersion%20%3D%204.0.0-alpha-2">4.0.0-alpha-2</a> <a href=https://hive.apache.org/docs/latest/compaction-pooling_240884493/>compaction pooling</a> is available.<br>
 As of Hive release <a href="https://issues.apache.org/jira/browse/HIVE-27094?jql=project%20%3D%20HIVE%20AND%20fixVersion%20%3D%204.0.0">4.0.0</a> <a href=https://hive.apache.org/docs/latest/rebalance-compaction_240884502/>rebalance compaction</a> is available.</p>
-<pre tabindex=0><code>ALTER TABLE table\_name [PARTITION (partition\_key = 'partition\_value' [, ...])]
-  COMPACT 'compaction\_type'[AND WAIT]
+<pre tabindex=0><code>ALTER TABLE table_name [PARTITION (partition_key = 'partition_value' [, ...])]
+  COMPACT 'compaction_type'[AND WAIT]
    [CLUSTERED INTO n BUCKETS]
-   [ORDER BY col\_list]
-   [POOL 'pool\_name']
+   [ORDER BY col_list]
+   [POOL 'pool_name']
    [WITH OVERWRITE TBLPROPERTIES (&quot;property&quot;=&quot;value&quot; [, ...])];
 </code></pre><p>In general you do not need to request compactions when <a href=https://hive.apache.org/docs/latest/hive-transactions_40509723/>Hive transactions</a> are being used, because the system will detect the need for them and initiate the compaction. However, if compaction is turned off for a table or you want to compact the table at a time the system would not choose to, ALTER TABLE can initiate the compaction. By default the statement will enqueue a request for compaction and r [...]
 <p>The compaction_type can be MAJOR, MINOR or REBALANCE. See the Basic Design section in <a href=#hive-transactions>Hive Transactions</a> for more information.</p>
@@ -973,12 +973,12 @@ As of Hive release <a href="https://issues.apache.org/jira/browse/HIVE-27094?jql
 <h4 id=alter-tablepartition-concatenate>Alter Table/Partition Concatenate</h4>
 <p>Version information</p>
 <p>In Hive release <a href=https://issues.apache.org/jira/browse/HIVE-1950>0.8.0</a> RCFile added support for fast block level merging of small RCFiles using concatenate command. In Hive release <a href=https://issues.apache.org/jira/browse/HIVE-7509>0.14.0</a> ORC files added support fast stripe level merging of small ORC files using concatenate command.</p>
-<pre tabindex=0><code>ALTER TABLE table\_name [PARTITION (partition\_key = 'partition\_value' [, ...])] CONCATENATE;
+<pre tabindex=0><code>ALTER TABLE table_name [PARTITION (partition_key = 'partition_value' [, ...])] CONCATENATE;
 </code></pre><p>If the table or partition contains many small RCFiles or ORC files, then the above command will merge them into larger files. In case of RCFile the merge happens at block level whereas for ORC files the merge happens at stripe level thereby avoiding the overhead of decompressing and decoding the data.</p>
 <h4 id=alter-tablepartition-update-columns>Alter Table/Partition Update columns</h4>
 <p>Version information</p>
 <p>In Hive release <a href=https://issues.apache.org/jira/browse/HIVE-15995>3.0.0</a> this command was added to let the user sync serde stored schema information to metastore.</p>
-<pre tabindex=0><code>ALTER TABLE table\_name [PARTITION (partition\_key = 'partition\_value' [, ...])] UPDATE COLUMNS;
+<pre tabindex=0><code>ALTER TABLE table_name [PARTITION (partition_key = 'partition_value' [, ...])] UPDATE COLUMNS;
 </code></pre><p>Tables that have serdes which self-describe the table schema may have different schemas in reality and the ones stored in Hive Metastore. For example when a user creates an Avro stored table using a schema url or schema literal, the schema will be inserted into HMS and then will never be changed in HMS regardless of url or literal changes within the serde. This can lead to problems especially when integrating with other Apache components.</p>
 <p>The update columns feature provides a way for the user to let any schema changes made in the serde to be synced into HMS. It works on both the table and the partitions levels, and obviously only for tables whose schema is not tracked by HMS (see metastore.serdes.using.metastore.for.schema). Using the command on these latter serde types will result in error.</p>
 <h3 id=alter-column>Alter Column</h3>
@@ -989,33 +989,33 @@ As of Hive release <a href="https://issues.apache.org/jira/browse/HIVE-27094?jql
 <p>In Hive release 0.13.0 and later, by default column names can be specified within backticks (```) and contain any <a href=http://en.wikipedia.org/wiki/List_of_Unicode_characters>Unicode</a> character (<a href=https://issues.apache.org/jira/browse/HIVE-6013>HIVE-6013</a>), however, dot (<strong>.</strong>) and colon (<strong>:</strong>) yield errors on querying. Within a string delimited by backticks, all characters are treated literally except that double backticks (````) represent on [...]
 <p>Backtick quotation enables the use of reserved keywords for column names, as well as table names.</p>
 <h4 id=change-column-nametypepositioncomment>Change Column Name/Type/Position/Comment</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name [PARTITION partition\_spec] CHANGE [COLUMN] col\_old\_name col\_new\_name column\_type
-  [COMMENT col\_comment] [FIRST|AFTER column\_name] [CASCADE|RESTRICT];
+<pre tabindex=0><code>ALTER TABLE table_name [PARTITION partition_spec] CHANGE [COLUMN] col_old_name col_new_name column_type
+  [COMMENT col_comment] [FIRST|AFTER column_name] [CASCADE|RESTRICT];
 
 </code></pre><p>This command will allow users to change a column&rsquo;s name, <a href=https://hive.apache.org/docs/latest/languagemanual-types_27838462/>data type</a>, comment, or position, or an arbitrary combination of them. The PARTITION clause is available in <a href=https://issues.apache.org/jira/browse/HIVE-7971>Hive 0.14.0</a> and later; see <a href=#upgrading-pre-hive-0-13-0-decimal-columns>Upgrading Pre-Hive 0.13.0 Decimal Columns</a> for usage. A patch for Hive 0.13 is also av [...]
 <p>The CASCADE|RESTRICT clause is available in <a href=https://issues.apache.org/jira/browse/HIVE-8839>Hive 1.1.0</a>. ALTER TABLE CHANGE COLUMN with CASCADE command changes the columns of a table&rsquo;s metadata, and cascades the same change to all the partition metadata. RESTRICT is the default, limiting column change only to table metadata.</p>
 <p>ALTER TABLE CHANGE COLUMN CASCADE clause will override the table partition&rsquo;s column metadata regardless of the table or partition&rsquo;s <a href=#protection-mode>protection mode</a>. Use with discretion.</p>
 <p>The column change command will only modify Hive&rsquo;s metadata, and will not modify data. Users should make sure the actual data layout of the table/partition conforms with the metadata definition.</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE TABLE test\_change (a int, b int, c int);
+<pre tabindex=0><code>CREATE TABLE test_change (a int, b int, c int);
 
 // First change column a's name to a1.
-ALTER TABLE test\_change CHANGE a a1 INT;
+ALTER TABLE test_change CHANGE a a1 INT;
 
 // Next change column a1's name to a2, its data type to string, and put it after column b.
-ALTER TABLE test\_change CHANGE a1 a2 STRING AFTER b;
+ALTER TABLE test_change CHANGE a1 a2 STRING AFTER b;
 // The new table's structure is:  b int, a2 string, c int.
  
 // Then change column c's name to c1, and put it as the first column.
-ALTER TABLE test\_change CHANGE c c1 INT FIRST;
+ALTER TABLE test_change CHANGE c c1 INT FIRST;
 // The new table's structure is:  c1 int, b int, a2 string.
  
 // Add a comment to column a1
-ALTER TABLE test\_change CHANGE a1 a1 INT COMMENT 'this is column a1';
+ALTER TABLE test_change CHANGE a1 a1 INT COMMENT 'this is column a1';
 </code></pre><h4 id=addreplace-columns>Add/Replace Columns</h4>
-<pre tabindex=0><code>ALTER TABLE table\_name 
-  [PARTITION partition\_spec]                 -- (Note: Hive 0.14.0 and later)
-  ADD|REPLACE COLUMNS (col\_name data\_type [COMMENT col\_comment], ...)
+<pre tabindex=0><code>ALTER TABLE table_name 
+  [PARTITION partition_spec]                 -- (Note: Hive 0.14.0 and later)
+  ADD|REPLACE COLUMNS (col_name data_type [COMMENT col_comment], ...)
   [CASCADE|RESTRICT]                         -- (Note: Hive 1.1.0 and later)
 
 </code></pre><p>ADD COLUMNS lets you add new columns to the end of the existing columns but before the partition columns. This is supported for Avro backed tables as well, for <a href=https://issues.apache.org/jira/browse/HIVE-7446>Hive 0.14</a> and later.</p>
@@ -1025,8 +1025,8 @@ ALTER TABLE test\_change CHANGE a1 a1 INT COMMENT 'this is column a1';
 <p>ALTER TABLE ADD or REPLACE COLUMNS CASCADE will override the table partition&rsquo;s column metadata regardless of the table or partition&rsquo;s <a href=#protection-mode>protection mode</a>. Use with discretion.The column change command will only modify Hive&rsquo;s metadata, and will not modify data. Users should make sure the actual data layout of the table/partition conforms with the metadata definition.</p>
 <h4 id=partial-partition-specification>Partial Partition Specification</h4>
 <p>As of Hive 0.14 (<a href=https://issues.apache.org/jira/browse/HIVE-8411>HIVE-8411</a>), users are able to provide a partial partition spec for certain above alter column statements, similar to dynamic partitioning. So rather than having to issue an alter column statement for each partition that needs to be changed:</p>
-<pre tabindex=0><code>ALTER TABLE foo PARTITION (ds='2008-04-08', hr=11) CHANGE COLUMN dec\_column\_name dec\_column\_name DECIMAL(38,18);
-ALTER TABLE foo PARTITION (ds='2008-04-08', hr=12) CHANGE COLUMN dec\_column\_name dec\_column\_name DECIMAL(38,18);
+<pre tabindex=0><code>ALTER TABLE foo PARTITION (ds='2008-04-08', hr=11) CHANGE COLUMN dec_column_name dec_column_name DECIMAL(38,18);
+ALTER TABLE foo PARTITION (ds='2008-04-08', hr=12) CHANGE COLUMN dec_column_name dec_column_name DECIMAL(38,18);
 ...
 
 </code></pre><p>&mldr; you can change many existing partitions at once using a single ALTER statement with a partial partition specification:</p>
@@ -1034,10 +1034,10 @@ ALTER TABLE foo PARTITION (ds='2008-04-08', hr=12) CHANGE COLUMN dec\_column\_na
 SET hive.exec.dynamic.partition = true;
  
 // This will alter all existing partitions in the table with ds='2008-04-08' -- be sure you know what you are doing!
-ALTER TABLE foo PARTITION (ds='2008-04-08', hr) CHANGE COLUMN dec\_column\_name dec\_column\_name DECIMAL(38,18);
+ALTER TABLE foo PARTITION (ds='2008-04-08', hr) CHANGE COLUMN dec_column_name dec_column_name DECIMAL(38,18);
 
 // This will alter all existing partitions in the table -- be sure you know what you are doing!
-ALTER TABLE foo PARTITION (ds, hr) CHANGE COLUMN dec\_column\_name dec\_column\_name DECIMAL(38,18);
+ALTER TABLE foo PARTITION (ds, hr) CHANGE COLUMN dec_column_name dec_column_name DECIMAL(38,18);
 </code></pre><p>Similar to dynamic partitioning, <a href=#hive-exec-dynamic-partition>hive.exec.dynamic.partition</a> must be set to true to enable use of partial partition specs during ALTER PARTITION. This is supported for the following operations:</p>
 <ul>
 <li>Change column</li>
@@ -1056,9 +1056,9 @@ ALTER TABLE foo PARTITION (ds, hr) CHANGE COLUMN dec\_column\_name dec\_column\_
 <p>Version information</p>
 <p>View support is only available in Hive 0.6 and later.</p>
 <h3 id=create-view>Create View</h3>
-<pre tabindex=0><code>CREATE VIEW [IF NOT EXISTS] [db\_name.]view\_name [(column\_name [COMMENT column\_comment], ...) ]
-  [COMMENT view\_comment]
-  [TBLPROPERTIES (property\_name = property\_value, ...)]
+<pre tabindex=0><code>CREATE VIEW [IF NOT EXISTS] [db_name.]view_name [(column_name [COMMENT column_comment], ...) ]
+  [COMMENT view_comment]
+  [TBLPROPERTIES (property_name = property_value, ...)]
   AS SELECT ...;
 
 </code></pre><p>CREATE VIEW creates a view with the given name. An error is thrown if a table or view with the same name already exists. You can use IF NOT EXISTS to skip the error.</p>
@@ -1070,36 +1070,36 @@ ALTER TABLE foo PARTITION (ds, hr) CHANGE COLUMN dec\_column\_name dec\_column\_
 <p>A view may contain ORDER BY and LIMIT clauses. If a referencing query also contains these clauses, the query-level clauses are evaluated <strong>after</strong> the view clauses (and after any other operations in the query). For example, if a view specifies LIMIT 5, and a referencing query is executed as (select * from v LIMIT 10), then at most 5 rows will be returned.</p>
 <p>Starting with <a href=https://issues.apache.org/jira/browse/HIVE-1180>Hive 0.13.0</a>, the view&rsquo;s select statement can include one or more common table expressions (CTEs) as shown in the <a href=https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Select#LanguageManualSelect-SelectSyntax>SELECT syntax</a>. For examples of CTEs in CREATE VIEW statements, see <a href=https://cwiki.apache.org/confluence/display/Hive/Common+Table+Expression#CommonTableExpression-CTEinView [...]
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE VIEW onion\_referrers(url COMMENT 'URL of Referring page')
+<pre tabindex=0><code>CREATE VIEW onion_referrers(url COMMENT 'URL of Referring page')
   COMMENT 'Referrers to The Onion website'
   AS
-  SELECT DISTINCT referrer\_url
-  FROM page\_view
-  WHERE page\_url='http://www.theonion.com';
+  SELECT DISTINCT referrer_url
+  FROM page_view
+  WHERE page_url='http://www.theonion.com';
 
 </code></pre><p>Use <a href=#show-create-table>SHOW CREATE TABLE</a> to display the CREATE VIEW statement that created a view. As of Hive 2.2.0, <a href=#show-views>SHOW VIEWS</a> displays a list of views in a database.</p>
 <p>Version Information</p>
 <p>Originally, the file format for views was hard coded as SequenceFile. Hive 2.1.0 (<a href=https://issues.apache.org/jira/browse/HIVE-13736>HIVE-13736</a>) made views follow the same defaults as tables and indexes using the <a href=#hive-default-fileformat>hive.default.fileformat</a>and <a href=#hive-default-fileformat-managed>hive.default.fileformat.managed</a> properties.</p>
 <h3 id=drop-view>Drop View</h3>
-<pre tabindex=0><code>DROP VIEW [IF EXISTS] [db\_name.]view\_name;
+<pre tabindex=0><code>DROP VIEW [IF EXISTS] [db_name.]view_name;
 
 </code></pre><p>DROP VIEW removes metadata for the specified view. (It is illegal to use DROP TABLE on a view.)</p>
 <p>When dropping a view referenced by other views, no warning is given (the dependent views are left dangling as invalid and must be dropped or recreated by the user).</p>
 <p>In Hive 0.7.0 or later, DROP returns an error if the view doesn&rsquo;t exist, unless IF EXISTS is specified or the configuration variable <a href=#hive-exec-drop-ignorenonexistent>hive.exec.drop.ignorenonexistent</a> is set to true.</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>DROP VIEW onion\_referrers;
+<pre tabindex=0><code>DROP VIEW onion_referrers;
 
 </code></pre><h3 id=alter-view-properties>Alter View Properties</h3>
-<pre tabindex=0><code>ALTER VIEW [db\_name.]view\_name SET TBLPROPERTIES table\_properties;
+<pre tabindex=0><code>ALTER VIEW [db_name.]view_name SET TBLPROPERTIES table_properties;
 
-table\_properties:
-  : (property\_name = property\_value, property\_name = property\_value, ...)
+table_properties:
+  : (property_name = property_value, property_name = property_value, ...)
 
 </code></pre><p>As with ALTER TABLE, you can use this statement to add your own metadata to a view.</p>
 <h3 id=alter-view-as-select>Alter View As Select</h3>
 <p>Version information</p>
 <p>As of <a href=https://issues.apache.org/jira/browse/HIVE-3834>Hive 0.11</a>.</p>
-<pre tabindex=0><code>ALTER VIEW [db\_name.]view\_name AS select\_statement;
+<pre tabindex=0><code>ALTER VIEW [db_name.]view_name AS select_statement;
 
 </code></pre><p>Alter View As Select changes the definition of a view, which must exist. The syntax is similar to that for CREATE VIEW and the effect is the same as for CREATE OR REPLACE VIEW.</p>
 <p>Note: The view must already exist, and if the view has partitions, it could not be replaced by Alter View As Select.</p>
@@ -1113,18 +1113,18 @@ table\_properties:
 <p>Materialized view support is only available in Hive 3.0 and later.</p>
 <p>This section provides an introduction to Hive materialized views syntax. More information about materialized view support and usage in Hive can be found <a href=https://hive.apache.org/docs/latest/materialized-views_80447331/>here</a>.</p>
 <h3 id=create-materialized-view>Create Materialized View</h3>
-<pre tabindex=0><code>CREATE MATERIALIZED VIEW [IF NOT EXISTS] [db\_name.]materialized\_view\_name
+<pre tabindex=0><code>CREATE MATERIALIZED VIEW [IF NOT EXISTS] [db_name.]materialized_view_name
   [DISABLE REWRITE]
-  [COMMENT materialized\_view\_comment]
-  [PARTITIONED ON (col\_name, ...)]
-  [CLUSTERED ON (col\_name, ...) | DISTRIBUTED ON (col\_name, ...) SORTED ON (col\_name, ...)]
+  [COMMENT materialized_view_comment]
+  [PARTITIONED ON (col_name, ...)]
+  [CLUSTERED ON (col_name, ...) | DISTRIBUTED ON (col_name, ...) SORTED ON (col_name, ...)]
   [
-    [ROW FORMAT row\_format]
-    [STORED AS file\_format]
+    [ROW FORMAT row_format]
+    [STORED AS file_format]
       | STORED BY 'storage.handler.class.name' [WITH SERDEPROPERTIES (...)]
   ]
-  [LOCATION hdfs\_path]
-  [TBLPROPERTIES (property\_name=property\_value, ...)]
+  [LOCATION hdfs_path]
+  [TBLPROPERTIES (property_name=property_value, ...)]
 AS SELECT ...;
 
 </code></pre><p>CREATE MATERIALIZED VIEW creates a view with the given name. An error is thrown if a table, view or materialized view with the same name already exists. You can use IF NOT EXISTS to skip the error.</p>
@@ -1136,13 +1136,13 @@ AS SELECT ...;
 <p>Version information</p>
 <p>CLUSTERED/DISTRIBUTED/SORTED ON is supported as of Hive 4.0.0 (<a href=https://issues.apache.org/jira/browse/HIVE-18842>HIVE-18842</a>).</p>
 <h3 id=drop-materialized-view>Drop Materialized View</h3>
-<pre tabindex=0><code>DROP MATERIALIZED VIEW [db\_name.]materialized\_view\_name;
+<pre tabindex=0><code>DROP MATERIALIZED VIEW [db_name.]materialized_view_name;
 
 </code></pre><p>DROP MATERIALIZED VIEW removes metadata and data for this materialized view.</p>
 <h3 id=alter-materialized-view>Alter Materialized View</h3>
 <p>Once a materialized view has been created, the optimizer will be able to exploit its definition semantics to automatically rewrite incoming queries using materialized views, and hence, accelerate query execution. </p>
 <p>Users can selectively enable/disable materialized views for rewriting. Recall that, by default, materialized views are enabled for rewriting at creation time. To alter that behavior, the following statement can be used:</p>
-<pre tabindex=0><code>ALTER MATERIALIZED VIEW [db\_name.]materialized\_view\_name ENABLE|DISABLE REWRITE;
+<pre tabindex=0><code>ALTER MATERIALIZED VIEW [db_name.]materialized_view_name ENABLE|DISABLE REWRITE;
 
 </code></pre><h2 id=createdropalterindex>Create/Drop/Alter Index</h2>
 <p>Version information</p>
@@ -1155,28 +1155,28 @@ AS SELECT ...;
 </ul>
 <p>In Hive 0.12.0 and earlier releases, the index name is case-sensitive for CREATE INDEX and DROP INDEX statements. However, ALTER INDEX requires an index name that was created with lowercase letters (see <a href=https://issues.apache.org/jira/browse/HIVE-2752>HIVE-2752</a>). This bug is fixed in <a href=https://issues.apache.org/jira/browse/HIVE-2752>Hive 0.13.0</a> by making index names case-insensitive for all HiveQL statements. For releases prior to 0.13.0, the best practice is to u [...]
 <h3 id=create-index>Create Index</h3>
-<pre tabindex=0><code>CREATE INDEX index\_name
-  ON TABLE base\_table\_name (col\_name, ...)
-  AS index\_type
+<pre tabindex=0><code>CREATE INDEX index_name
+  ON TABLE base_table_name (col_name, ...)
+  AS index_type
   [WITH DEFERRED REBUILD]
-  [IDXPROPERTIES (property\_name=property\_value, ...)]
-  [IN TABLE index\_table\_name]
+  [IDXPROPERTIES (property_name=property_value, ...)]
+  [IN TABLE index_table_name]
   [
      [ ROW FORMAT ...] STORED AS ...
      | STORED BY ...
   ]
-  [LOCATION hdfs\_path]
+  [LOCATION hdfs_path]
   [TBLPROPERTIES (...)]
   [COMMENT &quot;index comment&quot;];
 
 </code></pre><p>CREATE INDEX creates an index on a table using the given list of columns as keys. See CREATE INDEX in the <a href=#indexes>Indexes</a> design document.</p>
 <h3 id=drop-index>Drop Index</h3>
-<pre tabindex=0><code>DROP INDEX [IF EXISTS] index\_name ON table\_name;
+<pre tabindex=0><code>DROP INDEX [IF EXISTS] index_name ON table_name;
 
 </code></pre><p>DROP INDEX drops the index, as well as deleting the index table.</p>
 <p>In Hive 0.7.0 or later, DROP returns an error if the index doesn&rsquo;t exist, unless IF EXISTS is specified or the configuration variable <a href=#hive-exec-drop-ignorenonexistent>hive.exec.drop.ignorenonexistent</a> is set to true.</p>
 <h3 id=alter-index>Alter Index</h3>
-<pre tabindex=0><code>ALTER INDEX index\_name ON table\_name [PARTITION partition\_spec] REBUILD;
+<pre tabindex=0><code>ALTER INDEX index_name ON table_name [PARTITION partition_spec] REBUILD;
 
 </code></pre><p>ALTER INDEX &mldr; REBUILD builds an index that was created using the WITH DEFERRED REBUILD clause, or rebuilds a previously built index. If PARTITION is specified, only that partition is rebuilt.</p>
 <h2 id=createdrop-macro>Create/Drop Macro</h2>
@@ -1190,27 +1190,27 @@ AS SELECT ...;
 Hive 0.12.0 introduced macros to HiveQL, prior to which they could only be created in Java.</li>
 </ul>
 <h3 id=create-temporary-macro>Create Temporary Macro</h3>
-<pre tabindex=0><code>CREATE TEMPORARY MACRO macro\_name([col\_name col\_type, ...]) expression;
+<pre tabindex=0><code>CREATE TEMPORARY MACRO macro_name([col_name col_type, ...]) expression;
 
 </code></pre><p>CREATE TEMPORARY MACRO creates a macro using the given optional list of columns as inputs to the expression. Macros exist for the duration of the current session.</p>
 <p><strong>Examples:</strong></p>
-<pre tabindex=0><code>CREATE TEMPORARY MACRO fixed\_number() 42;
-CREATE TEMPORARY MACRO string\_len\_plus\_two(x string) length(x) + 2;
-CREATE TEMPORARY MACRO simple\_add (x int, y int) x + y;
+<pre tabindex=0><code>CREATE TEMPORARY MACRO fixed_number() 42;
+CREATE TEMPORARY MACRO string_len_plus_two(x string) length(x) + 2;
+CREATE TEMPORARY MACRO simple_add (x int, y int) x + y;
 </code></pre><h3 id=drop-temporary-macro>Drop Temporary Macro</h3>
-<pre tabindex=0><code>DROP TEMPORARY MACRO [IF EXISTS] macro\_name;
+<pre tabindex=0><code>DROP TEMPORARY MACRO [IF EXISTS] macro_name;
 
 </code></pre><p>DROP TEMPORARY MACRO returns an error if the function doesn&rsquo;t exist, unless IF EXISTS is specified.</p>
 <h2 id=createdropreload-function>Create/Drop/Reload Function</h2>
 <h3 id=temporary-functions>Temporary Functions</h3>
 <h4 id=create-temporary-function>Create Temporary Function</h4>
-<pre tabindex=0><code>CREATE TEMPORARY FUNCTION function\_name AS class\_name;
+<pre tabindex=0><code>CREATE TEMPORARY FUNCTION function_name AS class_name;
 
 </code></pre><p>This statement lets you create a function that is implemented by the class_name. You can use this function in Hive queries as long as the session lasts. You can use any class that is in the class path of Hive. You can add jars to class path by executing &lsquo;ADD JAR&rsquo; statements. Please refer to the CLI section <a href=#hive-interactive-shell-commands>Hive Interactive Shell Commands</a>, including <a href=#hive-resources>Hive Resources</a>, for more information on  [...]
 <p>Also see <a href=https://hive.apache.org/docs/latest/hiveplugins_27362098/>Hive Plugins</a> for general information about creating custom UDFs.</p>
 <h4 id=drop-temporary-function>Drop Temporary Function</h4>
 <p>You can unregister a UDF as follows:</p>
-<pre tabindex=0><code>DROP TEMPORARY FUNCTION [IF EXISTS] function\_name;
+<pre tabindex=0><code>DROP TEMPORARY FUNCTION [IF EXISTS] function_name;
 
 </code></pre><p>In Hive 0.7.0 or later, DROP returns an error if the function doesn&rsquo;t exist, unless IF EXISTS is specified or the configuration variable <a href=#hive-exec-drop-ignorenonexistent>hive.exec.drop.ignorenonexistent</a> is set to true.</p>
 <h3 id=permanent-functions>Permanent Functions</h3>
@@ -1218,14 +1218,14 @@ CREATE TEMPORARY MACRO simple\_add (x int, y int) x + y;
 <h4 id=create-function>Create Function</h4>
 <p>Version information</p>
 <p>As of Hive 0.13.0 (<a href=https://issues.apache.org/jira/browse/HIVE-6047>HIVE-6047</a>).</p>
-<pre tabindex=0><code>CREATE FUNCTION [db\_name.]function\_name AS class\_name
-  [USING JAR|FILE|ARCHIVE 'file\_uri' [, JAR|FILE|ARCHIVE 'file\_uri'] ];
+<pre tabindex=0><code>CREATE FUNCTION [db_name.]function_name AS class_name
+  [USING JAR|FILE|ARCHIVE 'file_uri' [, JAR|FILE|ARCHIVE 'file_uri'] ];
 </code></pre><p>This statement lets you create a function that is implemented by the class_name. Jars, files, or archives which need to be added to the environment can be specified with the USING clause; when the function is referenced for the first time by a Hive session, these resources will be added to the environment as if <a href=#add-jar/file>ADD JAR/FILE</a> had been issued. If Hive is not in local mode, then the resource location must be a non-local URI such as an HDFS location.</p>
 <p>The function will be added to the database specified, or to the current database at the time that the function was created. The function can be referenced by fully qualifying the function name (db_name.function_name), or can be referenced without qualification if the function is in the current database.</p>
 <h4 id=drop-function>Drop Function</h4>
 <p>Version information</p>
 <p>As of Hive 0.13.0 (<a href=https://issues.apache.org/jira/browse/HIVE-6047>HIVE-6047</a>).</p>
-<pre tabindex=0><code>DROP FUNCTION [IF EXISTS] function\_name;
+<pre tabindex=0><code>DROP FUNCTION [IF EXISTS] function_name;
 </code></pre><p>DROP returns an error if the function doesn&rsquo;t exist, unless IF EXISTS is specified or the configuration variable <a href=#hive-exec-drop-ignorenonexistent>hive.exec.drop.ignorenonexistent</a> is set to true.</p>
 <h4 id=reload-function>Reload Function</h4>
 <p>Version information</p>
@@ -1238,8 +1238,8 @@ CREATE TEMPORARY MACRO simple\_add (x int, y int) x + y;
 <li><a href=#create-role>CREATE ROLE</a></li>
 <li><a href=#grant-role>GRANT ROLE</a></li>
 <li><a href=#revoke-role>REVOKE ROLE</a></li>
-<li><a href=#grant-privilege\_type>GRANT privilege_type</a></li>
-<li><a href=#revoke-privilege\_type>REVOKE privilege_type</a></li>
+<li><a href=#grant-privilege_type>GRANT privilege_type</a></li>
+<li><a href=#revoke-privilege_type>REVOKE privilege_type</a></li>
 <li><a href=#drop-role>DROP ROLE</a></li>
 <li><a href=#show-role-grant>SHOW ROLE GRANT</a></li>
 <li><a href=#show-grant>SHOW GRANT</a></li>
@@ -1261,8 +1261,8 @@ CREATE TEMPORARY MACRO simple\_add (x int, y int) x + y;
 </li>
 <li>Object Privilege Commands
 <ul>
-<li><a href=#grant-privilege\_type>GRANT privilege_type</a></li>
-<li><a href=#revoke-privilege\_type>REVOKE privilege_type</a></li>
+<li><a href=#grant-privilege_type>GRANT privilege_type</a></li>
+<li><a href=#revoke-privilege_type>REVOKE privilege_type</a></li>
 <li><a href=#show-grant>SHOW GRANT</a></li>
 </ul>
 </li>
@@ -1293,7 +1293,7 @@ CREATE TEMPORARY MACRO simple\_add (x int, y int) x + y;
 </ul>
 <p>These statements provide a way to query the Hive metastore for existing data and metadata accessible to this Hive system.</p>
 <h3 id=show-databases>Show Databases</h3>
-<pre tabindex=0><code>SHOW (DATABASES|SCHEMAS) [LIKE 'identifier\_with\_wildcards'];
+<pre tabindex=0><code>SHOW (DATABASES|SCHEMAS) [LIKE 'identifier_with_wildcards'];
 
 </code></pre><p>SHOW DATABASES or SHOW SCHEMAS lists all of the databases defined in the metastore. The uses of SCHEMAS and DATABASES are interchangeable – they mean the same thing.</p>
 <p>The optional LIKE clause allows the list of databases to be filtered using a regular expression. Wildcards in the regular expression can only be &lsquo;<em>&rsquo; for any character(s) or &lsquo;|&rsquo; for a choice. Examples are &lsquo;employees&rsquo;, &lsquo;emp</em>&rsquo;, &lsquo;emp*|*ees&rsquo;, all of which will match the database named &lsquo;employees&rsquo;.</p>
@@ -1306,47 +1306,47 @@ CREATE TEMPORARY MACRO simple\_add (x int, y int) x + y;
 <p>SHOW CONNECTORS lists all of the connectors defined in the metastore (depending on the user&rsquo;s access).</p>
 <h3 id=show-tablesviewsmaterialized-viewspartitionsindexes>Show Tables/Views/Materialized Views/Partitions/Indexes</h3>
 <h4 id=show-tables>Show Tables</h4>
-<pre tabindex=0><code>SHOW TABLES [IN database\_name] ['identifier\_with\_wildcards'];
+<pre tabindex=0><code>SHOW TABLES [IN database_name] ['identifier_with_wildcards'];
 
 </code></pre><p><code>SHOW TABLES</code> lists all the base tables and views in the current database (or the one explicitly named using the <code>IN</code> clause) with names matching the optional regular expression. Wildcards in the regular expression can only be &lsquo;<em>&rsquo; for any character(s) or &lsquo;|&rsquo; for a choice. Examples are &lsquo;page_view&rsquo;, &lsquo;page_v</em>&rsquo;, &lsquo;<em>view|page</em>&rsquo;, all which will match the &lsquo;page_view&rsquo; table. [...]
 <h4 id=show-views>Show Views</h4>
 <p>Version information</p>
 <p>Introduced in Hive 2.2.0 via <a href=https://issues.apache.org/jira/browse/HIVE-14558>HIVE-14558</a>.</p>
-<pre tabindex=0><code>SHOW VIEWS [IN/FROM database\_name] [LIKE 'pattern\_with\_wildcards'];
+<pre tabindex=0><code>SHOW VIEWS [IN/FROM database_name] [LIKE 'pattern_with_wildcards'];
 </code></pre><p><code>SHOW VIEWS</code> lists all the views in the current database (or the one explicitly named using the <code>IN</code> or <code>FROM</code> clause) with names matching the optional regular expression. Wildcards in the regular expression can only be &lsquo;<em>&rsquo; for any character(s) or &lsquo;|&rsquo; for a choice. Examples are &lsquo;page_view&rsquo;, &lsquo;page_v</em>&rsquo;, &lsquo;<em>view|page</em>&rsquo;, all which will match the &lsquo;page_view&rsquo; vi [...]
 <p><strong>Examples</strong></p>
 <pre tabindex=0><code>SHOW VIEWS;                                -- show all views in the current database
-SHOW VIEWS 'test\_*';                       -- show all views that start with &quot;test\_&quot;
+SHOW VIEWS 'test_*';                       -- show all views that start with &quot;test_&quot;
 SHOW VIEWS '*view2';                       -- show all views that end in &quot;view2&quot;
-SHOW VIEWS LIKE 'test\_view1|test\_view2';   -- show views named either &quot;test\_view1&quot; or &quot;test\_view2&quot;
+SHOW VIEWS LIKE 'test_view1|test_view2';   -- show views named either &quot;test_view1&quot; or &quot;test_view2&quot;
 SHOW VIEWS FROM test1;                     -- show views from database test1
 SHOW VIEWS IN test1;                       -- show views from database test1 (FROM and IN are same) 
-SHOW VIEWS IN test1 &quot;test\_*&quot;;              -- show views from database test2 that start with &quot;test\_&quot;
+SHOW VIEWS IN test1 &quot;test_*&quot;;              -- show views from database test2 that start with &quot;test_&quot;
 </code></pre><h4 id=show-materialized-views>Show Materialized Views</h4>
-<pre tabindex=0><code>SHOW MATERIALIZED VIEWS [IN/FROM database\_name] [LIKE 'pattern\_with\_wildcards’];
+<pre tabindex=0><code>SHOW MATERIALIZED VIEWS [IN/FROM database_name] [LIKE 'pattern_with_wildcards’];
 </code></pre><p><code>SHOW MATERIALIZED VIEWS</code> lists all the views in the current database (or the one explicitly named using the <code>IN</code> or <code>FROM</code> clause) with names matching the optional regular expression. It also shows additional information about the materialized view, e.g., whether rewriting is enabled, and the refresh mode for the materialized view. Wildcards in the regular expression can only be &lsquo;*&rsquo; for any character(s) or &lsquo;|&rsquo; for  [...]
 <h4 id=show-partitions>Show Partitions</h4>
-<pre tabindex=0><code>SHOW PARTITIONS table\_name;
+<pre tabindex=0><code>SHOW PARTITIONS table_name;
 
 </code></pre><p>SHOW PARTITIONS lists all the existing partitions for a given base table. Partitions are listed in alphabetical order.</p>
 <p>Version information</p>
 <p>As of Hive 0.6, SHOW PARTITIONS can filter the list of partitions as shown below.</p>
 <p>It is also possible to specify parts of a partition specification to filter the resulting list.</p>
 <p><strong>Examples:</strong></p>
-<pre tabindex=0><code>SHOW PARTITIONS table\_name PARTITION(ds='2010-03-03');            -- (Note: Hive 0.6 and later)
-SHOW PARTITIONS table\_name PARTITION(hr='12');                    -- (Note: Hive 0.6 and later)
-SHOW PARTITIONS table\_name PARTITION(ds='2010-03-03', hr='12');   -- (Note: Hive 0.6 and later)
+<pre tabindex=0><code>SHOW PARTITIONS table_name PARTITION(ds='2010-03-03');            -- (Note: Hive 0.6 and later)
+SHOW PARTITIONS table_name PARTITION(hr='12');                    -- (Note: Hive 0.6 and later)
+SHOW PARTITIONS table_name PARTITION(ds='2010-03-03', hr='12');   -- (Note: Hive 0.6 and later)
 
 </code></pre><p>Version information</p>
 <p>Starting with Hive 0.13.0, SHOW PARTITIONS can specify a database (<a href=https://issues.apache.org/jira/browse/HIVE-5912>HIVE-5912</a>).</p>
-<pre tabindex=0><code>SHOW PARTITIONS [db\_name.]table\_name [PARTITION(partition\_spec)];   -- (Note: Hive 0.13.0 and later)
+<pre tabindex=0><code>SHOW PARTITIONS [db_name.]table_name [PARTITION(partition_spec)];   -- (Note: Hive 0.13.0 and later)
 
 </code></pre><p><strong>Example:</strong></p>
 <pre tabindex=0><code>SHOW PARTITIONS databaseFoo.tableBar PARTITION(ds='2010-03-03', hr='12');   -- (Note: Hive 0.13.0 and later)
 
 </code></pre><p>Version information</p>
 <p>Starting with Hive 4.0.0, SHOW PARTITIONS can optionally use the WHERE/ORDER BY/LIMIT clause to filter/order/limit the resulting list (<a href=https://issues.apache.org/jira/browse/HIVE-22458>HIVE-22458</a>). These clauses work in a similar way as  they do in a SELECT statement.</p>
-<pre tabindex=0><code>SHOW PARTITIONS [db\_name.]table\_name [PARTITION(partition\_spec)] [WHERE where\_condition] [ORDER BY col\_list] [LIMIT rows];   -- (Note: Hive 4.0.0 and later)
+<pre tabindex=0><code>SHOW PARTITIONS [db_name.]table_name [PARTITION(partition_spec)] [WHERE where_condition] [ORDER BY col_list] [LIMIT rows];   -- (Note: Hive 4.0.0 and later)
 
 </code></pre><p><strong>Example:</strong></p>
 <pre tabindex=0><code>SHOW PARTITIONS databaseFoo.tableBar LIMIT 10;                                                               -- (Note: Hive 4.0.0 and later)
@@ -1356,20 +1356,20 @@ SHOW PARTITIONS databaseFoo.tableBar PARTITION(ds='2010-03-03') WHERE hr &gt;= 1
 SHOW PARTITIONS databaseFoo.tableBar WHERE hr &gt;= 10 AND ds='2010-03-03' ORDER BY hr DESC LIMIT 10;           -- (Note: Hive 4.0.0 and later)
 </code></pre><p>Note: Please use <em>hr >= 10</em>  instead of <em>hr - 10 >= 0</em>   to filter the results, as Metastore would not push the latter predicate down into the underlying storage.</p>
 <h4 id=show-tablepartition-extended>Show Table/Partition Extended</h4>
-<pre tabindex=0><code>SHOW TABLE EXTENDED [IN|FROM database\_name] LIKE 'identifier\_with\_wildcards' [PARTITION(partition\_spec)];
+<pre tabindex=0><code>SHOW TABLE EXTENDED [IN|FROM database_name] LIKE 'identifier_with_wildcards' [PARTITION(partition_spec)];
 
 </code></pre><p>SHOW TABLE EXTENDED will list information for all tables matching the given regular expression. Users cannot use regular expression for table name if a partition specification is present. This command&rsquo;s output includes basic table information and file system information like totalNumberFiles, totalFileSize, maxFileSize, minFileSize,lastAccessTime, and lastUpdateTime. If partition is present, it will output the given partition&rsquo;s file system information instead  [...]
 <p><strong>Example</strong></p>
-<pre tabindex=0><code>hive&gt; show table extended like part\_table;
+<pre tabindex=0><code>hive&gt; show table extended like part_table;
 OK
-tableName:part\_table
+tableName:part_table
 owner:thejas
-location:file:/tmp/warehouse/part\_table
+location:file:/tmp/warehouse/part_table
 inputformat:org.apache.hadoop.mapred.TextInputFormat
 outputformat:org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat
 columns:struct columns { i32 i}
 partitioned:true
-partitionColumns:struct partition\_columns { string d}
+partitionColumns:struct partition_columns { string d}
 totalNumberFiles:1
 totalFileSize:2
 maxFileSize:2
@@ -1388,30 +1388,30 @@ SHOW TBLPROPERTIES tblname(&quot;foo&quot;);
 <h4 id=show-create-table>Show Create Table</h4>
 <p>Version information</p>
 <p>As of <a href=https://issues.apache.org/jira/browse/HIVE-967>Hive 0.10</a>.</p>
-<pre tabindex=0><code>SHOW CREATE TABLE ([db\_name.]table\_name|view\_name);
+<pre tabindex=0><code>SHOW CREATE TABLE ([db_name.]table_name|view_name);
 
 </code></pre><p>SHOW CREATE TABLE shows the CREATE TABLE statement that creates a given table, or the CREATE VIEW statement that creates a given view.</p>
 <h4 id=show-indexes>Show Indexes</h4>
 <p>Version information</p>
 <p>As of Hive 0.7.</p>
 <p>Indexing Is Removed since 3.0! See <a href=https://hive.apache.org/docs/latest/indexdev_27362104/>Indexes design document</a></p>
-<pre tabindex=0><code>SHOW [FORMATTED] (INDEX|INDEXES) ON table\_with\_index [(FROM|IN) db\_name];
+<pre tabindex=0><code>SHOW [FORMATTED] (INDEX|INDEXES) ON table_with_index [(FROM|IN) db_name];
 
 </code></pre><p>SHOW INDEXES shows all of the indexes on a certain column, as well as information about them: index name, table name, names of the columns used as keys, index table name, index type, and comment. If the FORMATTED keyword is used, then column titles are printed for each column.</p>
 <h3 id=show-columns>Show Columns</h3>
 <p>Version information</p>
 <p>As of <a href=https://issues.apache.org/jira/browse/HIVE-2909>Hive 0.10</a>.</p>
-<pre tabindex=0><code>SHOW COLUMNS (FROM|IN) table\_name [(FROM|IN) db\_name];
+<pre tabindex=0><code>SHOW COLUMNS (FROM|IN) table_name [(FROM|IN) db_name];
 
 </code></pre><p>SHOW COLUMNS shows all the columns in a table including partition columns.</p>
 <p>Version information</p>
-<pre tabindex=0><code>SHOW COLUMNS (FROM|IN) table\_name [(FROM|IN) db\_name]  [ LIKE 'pattern_with_wildcards'];
+<pre tabindex=0><code>SHOW COLUMNS (FROM|IN) table_name [(FROM|IN) db_name]  [ LIKE 'pattern_with_wildcards'];
 </code></pre><p>Added in Hive 3.0 by <a href=https://issues.apache.org/jira/browse/HIVE-18373>HIVE-18373</a>.</p>
 <p><code>SHOW COLUMNS</code> lists all the columns in the table with names matching the optional regular expression. Wildcards in the regular expression can only be &lsquo;<em>&rsquo; for any character(s) or &lsquo;|&rsquo; for a choice. Examples are &lsquo;cola&rsquo;, &lsquo;col</em>&rsquo;, &lsquo;<em>a|col</em>&rsquo;, all which will match the &lsquo;cola&rsquo; column. Matching columns are listed in alphabetical order. It is not an error if no matching columns are found in table. If [...]
 <p><strong>Examples</strong></p>
 <pre tabindex=0><code>-- SHOW COLUMNS
-CREATE DATABASE test\_db;
-USE test\_db;
+CREATE DATABASE test_db;
+USE test_db;
 CREATE TABLE foo(col1 INT, col2 INT, col3 INT, cola INT, colb INT, colc INT, a INT, b INT, c INT);
  
 -- SHOW COLUMNS basic syntax
@@ -1420,8 +1420,8 @@ SHOW COLUMNS FROM foo &quot;*&quot;;                        -- show all column i
 SHOW COLUMNS IN foo &quot;col*&quot;;                       -- show columns in foo starting with &quot;col&quot;                 OUTPUT col1,col2,col3,cola,colb,colc
 SHOW COLUMNS FROM foo '*c';                       -- show columns in foo ending with &quot;c&quot;                     OUTPUT c,colc
 SHOW COLUMNS FROM foo LIKE &quot;col1|cola&quot;;           -- show columns in foo either col1 or cola                 OUTPUT col1,cola
-SHOW COLUMNS FROM foo FROM test\_db LIKE 'col*';   -- show columns in foo starting with &quot;col&quot;                 OUTPUT col1,col2,col3,cola,colb,colc
-SHOW COLUMNS IN foo IN test\_db LIKE 'col*';       -- show columns in foo starting with &quot;col&quot; (FROM/IN same)  OUTPUT col1,col2,col3,cola,colb,colc
+SHOW COLUMNS FROM foo FROM test_db LIKE 'col*';   -- show columns in foo starting with &quot;col&quot;                 OUTPUT col1,col2,col3,cola,colb,colc
+SHOW COLUMNS IN foo IN test_db LIKE 'col*';       -- show columns in foo starting with &quot;col&quot; (FROM/IN same)  OUTPUT col1,col2,col3,cola,colb,colc
  
 -- Non existing column pattern resulting in no match
 SHOW COLUMNS IN foo &quot;nomatch*&quot;;
@@ -1445,11 +1445,11 @@ SHOW COLUMNS IN foo &quot;nomatch&quot;;
 <li><a href=#show-principals>SHOW PRINCIPALS</a></li>
 </ul>
 <h3 id=show-locks>Show Locks</h3>
-<pre tabindex=0><code>SHOW LOCKS &lt;table\_name&gt;;
-SHOW LOCKS &lt;table\_name&gt; EXTENDED;
-SHOW LOCKS &lt;table\_name&gt; PARTITION (&lt;partition\_spec&gt;);
-SHOW LOCKS &lt;table\_name&gt; PARTITION (&lt;partition\_spec&gt;) EXTENDED;
-SHOW LOCKS (DATABASE|SCHEMA) database\_name;     -- (Note: Hive 0.13.0 and later; SCHEMA added in Hive 0.14.0)
+<pre tabindex=0><code>SHOW LOCKS &lt;table_name&gt;;
+SHOW LOCKS &lt;table_name&gt; EXTENDED;
+SHOW LOCKS &lt;table_name&gt; PARTITION (&lt;partition_spec&gt;);
+SHOW LOCKS &lt;table_name&gt; PARTITION (&lt;partition_spec&gt;) EXTENDED;
+SHOW LOCKS (DATABASE|SCHEMA) database_name;     -- (Note: Hive 0.13.0 and later; SCHEMA added in Hive 0.14.0)
 </code></pre><p>SHOW LOCKS displays the locks on a table or partition. See <a href=https://hive.apache.org/docs/latest/locking_27362050/>Hive Concurrency Model</a> for information about locks.</p>
 <p>SHOW LOCKS (DATABASE|SCHEMA) is supported from Hive 0.13 for DATABASE (see <a href=https://issues.apache.org/jira/browse/HIVE-2093>HIVE-2093</a>) and Hive 0.14 for SCHEMA (see <a href=https://issues.apache.org/jira/browse/HIVE-6601>HIVE-6601</a>). SCHEMA and DATABASE are interchangeable – they mean the same thing.</p>
 <p>When <a href=https://hive.apache.org/docs/latest/hive-transactions_40509723/>Hive transactions</a> are being used, SHOW LOCKS returns this information (see <a href=https://issues.apache.org/jira/browse/HIVE-6460>HIVE-6460</a>):</p>
@@ -1482,7 +1482,7 @@ SHOW LOCKS (DATABASE|SCHEMA) database\_name;     -- (Note: Hive 0.13.0 and later
 <h3 id=show-conf>Show Conf</h3>
 <p>Version information</p>
 <p>As of <a href=https://issues.apache.org/jira/browse/HIVE-6037>Hive 0.14.0</a>.</p>
-<pre tabindex=0><code>SHOW CONF &lt;configuration\_name&gt;;
+<pre tabindex=0><code>SHOW CONF &lt;configuration_name&gt;;
 </code></pre><p>SHOW CONF returns a description of the specified <a href=https://hive.apache.org/docs/latest/configuration-properties_27842758/>configuration property</a>.</p>
 <ul>
 <li>default value</li>
@@ -1506,7 +1506,7 @@ SHOW LOCKS (DATABASE|SCHEMA) database\_name;     -- (Note: Hive 0.13.0 and later
 <h3 id=show-compactions>Show Compactions</h3>
 <p>Version information</p>
 <p>As of <a href=https://issues.apache.org/jira/browse/HIVE-6460>Hive 0.13.0</a> (see <a href=#hive-transactions>Hive Transactions</a>).</p>
-<pre tabindex=0><code>SHOW COMPACTIONS [DATABASE.][TABLE] [PARTITION (&lt;partition\_spec&gt;)] [POOL\_NAME] [TYPE] [STATE] [ORDER BY `start` DESC] [LIMIT 10];
+<pre tabindex=0><code>SHOW COMPACTIONS [DATABASE.][TABLE] [PARTITION (&lt;partition_spec&gt;)] [POOL_NAME] [TYPE] [STATE] [ORDER BY `start` DESC] [LIMIT 10];
 </code></pre><p><a href=https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions#HiveTransactions-SHOWCOMPACTIONS>SHOW COMPACTIONS</a> returns a list of all compaction requests currently being <a href=#processed>processed</a> or scheduled, including this information:</p>
 <ul>
 <li>&ldquo;CompactionId&rdquo; - unique internal id (As of <a href=https://issues.apache.org/jira/browse/HIVE-16084>Hive 3.0</a>)</li>
@@ -1553,7 +1553,7 @@ SHOW COMPACTIONS tbl0
 SHOW COMPACTIONS compactionid =1
  — show all compactions with given compaction ID
 
-SHOW COMPACTIONS db1.tbl0 PARTITION (p=101,day='Monday') POOL 'pool0' TYPE 'minor' STATUS 'ready for clean' ORDER BY cq\_table DESC, cq\_state LIMIT 42
+SHOW COMPACTIONS db1.tbl0 PARTITION (p=101,day='Monday') POOL 'pool0' TYPE 'minor' STATUS 'ready for clean' ORDER BY cq_table DESC, cq_state LIMIT 42
  — show all compactions from specific database/table filtered based on pool name/type.state/status and ordered with given clause
 </code></pre><p>Compactions are initiated automatically, but can also be initiated manually with an <a href=#alter-table-compact-statement>ALTER TABLE COMPACT statement</a>.</p>
 <h2 id=describe>Describe</h2>
@@ -1571,12 +1571,12 @@ SHOW COMPACTIONS db1.tbl0 PARTITION (p=101,day='Monday') POOL 'pool0' TYPE 'mino
 <h3 id=describe-database>Describe Database</h3>
 <p>Version information</p>
 <p>As of Hive 0.7.</p>
-<pre tabindex=0><code>DESCRIBE DATABASE [EXTENDED] db\_name;
-DESCRIBE SCHEMA [EXTENDED] db\_name;     -- (Note: Hive 1.1.0 and later)
+<pre tabindex=0><code>DESCRIBE DATABASE [EXTENDED] db_name;
+DESCRIBE SCHEMA [EXTENDED] db_name;     -- (Note: Hive 1.1.0 and later)
 </code></pre><p>DESCRIBE DATABASE shows the name of the database, its comment (if one has been set), and its root location on the filesystem. The uses of SCHEMA and DATABASE are interchangeable – they mean the same thing. DESCRIBE SCHEMA is added in Hive 1.1.0 (<a href=https://issues.apache.org/jira/browse/HIVE-8803>HIVE-8803</a>).</p>
 <p>EXTENDED also shows the <a href=#database-properties>database properties</a>.</p>
 <h3 id=describe-dataconnector>Describe Dataconnector</h3>
-<pre tabindex=0><code>DESCRIBE CONNECTOR [EXTENDED] connector\_name;
+<pre tabindex=0><code>DESCRIBE CONNECTOR [EXTENDED] connector_name;
 </code></pre><p>Since Hive 4.0.0 via <a href=https://issues.apache.org/jira/browse/HIVE-24396>HIVE-24396</a></p>
 <p>DESCRIBE CONNECTOR shows the name of the connector, its comment (if one has been set), and its datasource URL and datasource type. </p>
 <p>EXTENDED also shows the dataconnector&rsquo;s properties. Any clear-text passwords set will be shown in clear text as well.</p>
@@ -1584,11 +1584,11 @@ DESCRIBE SCHEMA [EXTENDED] db\_name;     -- (Note: Hive 1.1.0 and later)
 <p>There are two formats for the describe table/view/materialized view/column syntax, depending on whether or not the database is specified.</p>
 <p>If the database is not specified, the optional column information is provided after a dot:</p>
 <pre tabindex=0><code>DESCRIBE [EXTENDED|FORMATTED]  
-  table\_name[.col\_name ( [.field\_name] | [.'$elem$'] | [.'$key$'] | [.'$value$'] )* ];
+  table_name[.col_name ( [.field_name] | [.'$elem$'] | [.'$key$'] | [.'$value$'] )* ];
                                         -- (Note: Hive 1.x.x and 0.x.x only. See &quot;Hive 2.0+: New Syntax&quot; below)
 </code></pre><p>If the database is specified, the optional column information is provided after a space:</p>
 <pre tabindex=0><code>DESCRIBE [EXTENDED|FORMATTED]  
-  [db\_name.]table\_name[ col\_name ( [.field\_name] | [.'$elem$'] | [.'$key$'] | [.'$value$'] )* ];
+  [db_name.]table_name[ col_name ( [.field_name] | [.'$elem$'] | [.'$key$'] | [.'$value$'] )* ];
                                         -- (Note: Hive 1.x.x and 0.x.x only. See &quot;Hive 2.0+: New Syntax&quot; below)
 </code></pre><p>DESCRIBE shows the list of columns including partition columns for the given table. If the EXTENDED keyword is specified then it will show all the metadata for the table in Thrift serialized form. This is generally only useful for debugging and not for general use. If the FORMATTED keyword is specified, then it will show the metadata in a tabular format.</p>
 <p>Note: DESCRIBE EXTENDED shows the number of rows only if statistics were gathered when the data was loaded (see <a href=#newly-created-tables>Newly Created Tables</a>), and if the Hive CLI is used instead of a Thrift client or Beeline. <a href=https://issues.apache.org/jira/browse/HIVE-6285>HIVE-6285</a> will address this issue. Although ANALYZE TABLE gathers statistics after the data has been loaded (see <a href=#existing-tables>Existing Tables</a>), it does not currently provide inf [...]
@@ -1606,63 +1606,63 @@ DESCRIBE SCHEMA [EXTENDED] db\_name;     -- (Note: Hive 1.1.0 and later)
 <p>Version information</p>
 <p>As of Hive 0.14.0; see <a href=https://issues.apache.org/jira/browse/HIVE-7050>HIVE-7050</a> and <a href=https://issues.apache.org/jira/browse/HIVE-7051>HIVE-7051</a>. (The FOR COLUMNS option of ANALYZE TABLE is available as of <a href=https://issues.apache.org/jira/browse/HIVE-1362>Hive 0.10.0</a>.)</p>
 <p>ANALYZE TABLE <em>table_name</em> COMPUTE STATISTICS FOR COLUMNS will compute column statistics for all columns in the specified table (and for all partitions if the table is partitioned). To view the gathered column statistics, the following statements can be used:</p>
-<pre tabindex=0><code>DESCRIBE FORMATTED [db\_name.]table\_name column\_name;                              -- (Note: Hive 0.14.0 and later)
-DESCRIBE FORMATTED [db\_name.]table\_name column\_name PARTITION (partition\_spec);   -- (Note: Hive 0.14.0 to 1.x.x)
+<pre tabindex=0><code>DESCRIBE FORMATTED [db_name.]table_name column_name;                              -- (Note: Hive 0.14.0 and later)
+DESCRIBE FORMATTED [db_name.]table_name column_name PARTITION (partition_spec);   -- (Note: Hive 0.14.0 to 1.x.x)
                                                                                   -- (see &quot;Hive 2.0+: New Syntax&quot; below)
 </code></pre><p>See <a href=#statistics-in-hive:-existing-tables>Statistics in Hive: Existing Tables</a> for more information about the ANALYZE TABLE command.</p>
 <h3 id=describe-partition>Describe Partition</h3>
 <p>There are two formats for the describe partition syntax, depending on whether or not the database is specified.</p>
 <p>If the database is not specified, the optional column information is provided after a dot:</p>
-<pre tabindex=0><code>DESCRIBE [EXTENDED|FORMATTED] table\_name[.column\_name] PARTITION partition\_spec;
+<pre tabindex=0><code>DESCRIBE [EXTENDED|FORMATTED] table_name[.column_name] PARTITION partition_spec;
                                         -- (Note: Hive 1.x.x and 0.x.x only. See &quot;Hive 2.0+: New Syntax&quot; below)
 </code></pre><p>If the database is specified, the optional column information is provided after a space:</p>
-<pre tabindex=0><code>DESCRIBE [EXTENDED|FORMATTED] [db\_name.]table\_name [column\_name] PARTITION partition\_spec;
+<pre tabindex=0><code>DESCRIBE [EXTENDED|FORMATTED] [db_name.]table_name [column_name] PARTITION partition_spec;
                                         -- (Note: Hive 1.x.x and 0.x.x only. See &quot;Hive 2.0+: New Syntax&quot; below)
 </code></pre><p>This statement lists metadata for a given partition. The output is similar to that of DESCRIBE table_name. Presently, the column information associated with a particular partition is not used while preparing plans. As of Hive 1.2 (<a href=https://issues.apache.org/jira/browse/HIVE-10307>HIVE-10307</a>), the partition column values specified in <em>partition_spec</em> are type validated, converted and normalized to their column types when <a href=#hive-typecheck-on-insert> [...]
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>hive&gt; show partitions part\_table;
+<pre tabindex=0><code>hive&gt; show partitions part_table;
 OK
 d=abc
 
-hive&gt; DESCRIBE extended part\_table partition (d='abc');
+hive&gt; DESCRIBE extended part_table partition (d='abc');
 OK
 i                       int                                         
 d                       string                                      
                  
 # Partition Information          
-# col\_name              data\_type               comment             
+# col_name              data_type               comment             
                  
 d                       string                                      
                  
-Detailed Partition Information  Partition(values:[abc], dbName:default, tableName:part\_table, createTime:1459382234, lastAccessTime:0, sd:StorageDescriptor(cols:[FieldSchema(name:i, type:int, comment:null), FieldSchema(name:d, type:string, comment:null)], location:file:/tmp/warehouse/part\_table/d=abc, inputFormat:org.apache.hadoop.mapred.TextInputFormat, outputFormat:org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat, compressed:false, numBuckets:-1, serdeInfo:SerDeInfo(name:nu [...]
+Detailed Partition Information  Partition(values:[abc], dbName:default, tableName:part_table, createTime:1459382234, lastAccessTime:0, sd:StorageDescriptor(cols:[FieldSchema(name:i, type:int, comment:null), FieldSchema(name:d, type:string, comment:null)], location:file:/tmp/warehouse/part_table/d=abc, inputFormat:org.apache.hadoop.mapred.TextInputFormat, outputFormat:org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat, compressed:false, numBuckets:-1, serdeInfo:SerDeInfo(name:null [...]
 Time taken: 0.325 seconds, Fetched: 9 row(s)
 
-hive&gt; DESCRIBE formatted part\_table partition (d='abc');
+hive&gt; DESCRIBE formatted part_table partition (d='abc');
 OK
-# col\_name              data\_type               comment             
+# col_name              data_type               comment             
                  
 i                       int                                         
                  
 # Partition Information          
-# col\_name              data\_type               comment             
+# col_name              data_type               comment             
                  
 d                       string                                      
                  
 # Detailed Partition Information                 
 Partition Value:        [abc]                    
 Database:               default                  
-Table:                  part\_table               
+Table:                  part_table               
 CreateTime:             Wed Mar 30 16:57:14 PDT 2016     
 LastAccessTime:         UNKNOWN                  
 Protect Mode:           None                     
-Location:               file:/tmp/warehouse/part\_table/d=abc     
+Location:               file:/tmp/warehouse/part_table/d=abc     
 Partition Parameters:            
-        COLUMN\_STATS\_ACCURATE   true                
+        COLUMN_STATS_ACCURATE   true                
         numFiles                1                   
         numRows                 1                   
         rawDataSize             1                   
         totalSize               2                   
-        transient\_lastDdlTime   1459382234          
+        transient_lastDdlTime   1459382234          
                  
 # Storage Information            
 SerDe Library:          org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe       
@@ -1680,7 +1680,7 @@ Time taken: 0.334 seconds, Fetched: 35 row(s)
 <p>Hive 2.0+: New syntax</p>
 <p>In Hive 2.0 release onward, the describe table command has a syntax change which is backward incompatible. See <a href=https://issues.apache.org/jira/browse/HIVE-12184>HIVE-12184</a> for details.</p>
 <pre tabindex=0><code>DESCRIBE [EXTENDED | FORMATTED]
-    [db\_name.]table\_name [PARTITION partition\_spec] [col\_name ( [.field\_name] | [.'$elem$'] | [.'$key$'] | [.'$value$'] )* ];
+    [db_name.]table_name [PARTITION partition_spec] [col_name ( [.field_name] | [.'$elem$'] | [.'$key$'] | [.'$value$'] )* ];
 
 </code></pre><p>Warning: The new syntax could break current scripts.</p>
 <ul>
@@ -1688,8 +1688,8 @@ Time taken: 0.334 seconds, Fetched: 35 row(s)
 <li>Optional partition_spec has to appear after the table_name but prior to the optional column_name. In the previous syntax, column_name appears in between table_name and partition_spec.</li>
 </ul>
 <p><strong>Examples:</strong></p>
-<pre tabindex=0><code>DESCRIBE FORMATTED default.src\_table PARTITION (part\_col = 100) columnA;
-DESCRIBE default.src\_thrift lintString.$elem$.myint;
+<pre tabindex=0><code>DESCRIBE FORMATTED default.src_table PARTITION (part_col = 100) columnA;
+DESCRIBE default.src_thrift lintString.$elem$.myint;
 </code></pre><h2 id=abort>Abort</h2>
 <ul>
 <li><a href=#abort-transactions>Abort Transactions</a></li>
diff --git a/docs/latest/languagemanual-dml_27362036/index.html b/docs/latest/languagemanual-dml_27362036/index.html
index 2d84b1d..190aa4f 100644
--- a/docs/latest/languagemanual-dml_27362036/index.html
+++ b/docs/latest/languagemanual-dml_27362036/index.html
@@ -260,22 +260,22 @@ LOAD DATA LOCAL INPATH 'filepath' INTO TABLE tab1;
 <p>Query Results can be inserted into tables by using the insert clause.</p>
 <h5 id=syntax-1>Syntax</h5>
 <pre tabindex=0><code>Standard syntax:
-INSERT OVERWRITE TABLE tablename1 [PARTITION (partcol1=val1, partcol2=val2 ...) [IF NOT EXISTS]] select\_statement1 FROM from\_statement;
-INSERT INTO TABLE tablename1 [PARTITION (partcol1=val1, partcol2=val2 ...)] select\_statement1 FROM from\_statement;
+INSERT OVERWRITE TABLE tablename1 [PARTITION (partcol1=val1, partcol2=val2 ...) [IF NOT EXISTS]] select_statement1 FROM from_statement;
+INSERT INTO TABLE tablename1 [PARTITION (partcol1=val1, partcol2=val2 ...)] select_statement1 FROM from_statement;
 
 Hive extension (multiple inserts):
-FROM from\_statement
-INSERT OVERWRITE TABLE tablename1 [PARTITION (partcol1=val1, partcol2=val2 ...) [IF NOT EXISTS]] select\_statement1
-[INSERT OVERWRITE TABLE tablename2 [PARTITION ... [IF NOT EXISTS]] select\_statement2] 
-[INSERT INTO TABLE tablename2 [PARTITION ...] select\_statement2] ...;
-FROM from\_statement
-INSERT INTO TABLE tablename1 [PARTITION (partcol1=val1, partcol2=val2 ...)] select\_statement1
-[INSERT INTO TABLE tablename2 [PARTITION ...] select\_statement2] 
-[INSERT OVERWRITE TABLE tablename2 [PARTITION ... [IF NOT EXISTS]] select\_statement2] ...;
+FROM from_statement
+INSERT OVERWRITE TABLE tablename1 [PARTITION (partcol1=val1, partcol2=val2 ...) [IF NOT EXISTS]] select_statement1
+[INSERT OVERWRITE TABLE tablename2 [PARTITION ... [IF NOT EXISTS]] select_statement2] 
+[INSERT INTO TABLE tablename2 [PARTITION ...] select_statement2] ...;
+FROM from_statement
+INSERT INTO TABLE tablename1 [PARTITION (partcol1=val1, partcol2=val2 ...)] select_statement1
+[INSERT INTO TABLE tablename2 [PARTITION ...] select_statement2] 
+[INSERT OVERWRITE TABLE tablename2 [PARTITION ... [IF NOT EXISTS]] select_statement2] ...;
 
 Hive extension (dynamic partition inserts):
-INSERT OVERWRITE TABLE tablename PARTITION (partcol1[=val1], partcol2[=val2] ...) select\_statement FROM from\_statement;
-INSERT INTO TABLE tablename PARTITION (partcol1[=val1], partcol2[=val2] ...) select\_statement FROM from\_statement;
+INSERT OVERWRITE TABLE tablename PARTITION (partcol1[=val1], partcol2[=val2] ...) select_statement FROM from_statement;
+INSERT INTO TABLE tablename PARTITION (partcol1[=val1], partcol2[=val2] ...) select_statement FROM from_statement;
 </code></pre><h5 id=synopsis-1>Synopsis</h5>
 <ul>
 <li>INSERT OVERWRITE will overwrite any existing data in the table or partition
@@ -352,9 +352,9 @@ An immutable table is protected against accidental updates due to a script load
 </tbody>
 </table>
 <h6 id=example>Example</h6>
-<pre tabindex=0><code>FROM page\_view\_stg pvs
-INSERT OVERWRITE TABLE page\_view PARTITION(dt='2008-06-08', country)
-       SELECT pvs.viewTime, pvs.userid, pvs.page\_url, pvs.referrer\_url, null, null, pvs.ip, pvs.cnt
+<pre tabindex=0><code>FROM page_view_stg pvs
+INSERT OVERWRITE TABLE page_view PARTITION(dt='2008-06-08', country)
+       SELECT pvs.viewTime, pvs.userid, pvs.page_url, pvs.referrer_url, null, null, pvs.ip, pvs.cnt
 
 </code></pre><p>Here the <code>country</code> partition will be dynamically created by the last column from the <code>SELECT</code> clause (i.e. <code>pvs.cnt</code>). Note that the name is not used. In <code>nonstrict</code> mode the <code>dt</code> partition could also be dynamically created.</p>
 <h6 id=additional-documentation>Additional Documentation</h6>
@@ -378,16 +378,16 @@ INSERT OVERWRITE TABLE page\_view PARTITION(dt='2008-06-08', country)
 <h5 id=syntax-2>Syntax</h5>
 <pre tabindex=0><code>Standard syntax:
 INSERT OVERWRITE [LOCAL] DIRECTORY directory1
-  [ROW FORMAT row\_format] [STORED AS file\_format] (Note: Only available starting with Hive 0.11.0)
+  [ROW FORMAT row_format] [STORED AS file_format] (Note: Only available starting with Hive 0.11.0)
   SELECT ... FROM ...
 
 Hive extension (multiple inserts):
-FROM from\_statement
-INSERT OVERWRITE [LOCAL] DIRECTORY directory1 select\_statement1
-[INSERT OVERWRITE [LOCAL] DIRECTORY directory2 select\_statement2] ...
+FROM from_statement
+INSERT OVERWRITE [LOCAL] DIRECTORY directory1 select_statement1
+[INSERT OVERWRITE [LOCAL] DIRECTORY directory2 select_statement2] ...
 
  
-row\_format
+row_format
   : DELIMITED [FIELDS TERMINATED BY char [ESCAPED BY char]] [COLLECTION ITEMS TERMINATED BY char]
         [MAP KEYS TERMINATED BY char] [LINES TERMINATED BY char]
         [NULL DEFINED AS char] (Note: Only available starting with Hive 0.13)
@@ -411,9 +411,9 @@ row\_format
 <p>INSERT&mldr;VALUES is available starting in <a href=https://issues.apache.org/jira/browse/HIVE-5317>Hive 0.14</a>.</p>
 <h5 id=syntax-3>Syntax</h5>
 <pre tabindex=0><code>Standard Syntax:
-INSERT INTO TABLE tablename [PARTITION (partcol1[=val1], partcol2[=val2] ...)] VALUES values\_row [, values\_row ...]
+INSERT INTO TABLE tablename [PARTITION (partcol1[=val1], partcol2[=val2] ...)] VALUES values_row [, values_row ...]
  
-Where values\_row is:
+Where values_row is:
 ( value [, value ...] )
 where a value is either null or any valid SQL literal
 </code></pre><h5 id=synopsis-3>Synopsis</h5>
@@ -431,7 +431,7 @@ where a value is either null or any valid SQL literal
 INSERT INTO TABLE students
   VALUES ('fred flintstone', 35, 1.28), ('barney rubble', 32, 2.32);
 
-CREATE TABLE pageviews (userid VARCHAR(64), link STRING, came\_from STRING)
+CREATE TABLE pageviews (userid VARCHAR(64), link STRING, came_from STRING)
   PARTITIONED BY (datestamp STRING) CLUSTERED BY (userid) INTO 256 BUCKETS STORED AS ORC;
 
 INSERT INTO TABLE pageviews PARTITION (datestamp = '2014-09-23')
diff --git a/docs/latest/languagemanual-explain_27362037/index.html b/docs/latest/languagemanual-explain_27362037/index.html
index 76ca52b..c5eebd0 100644
--- a/docs/latest/languagemanual-explain_27362037/index.html
+++ b/docs/latest/languagemanual-explain_27362037/index.html
@@ -147,7 +147,7 @@ ASF
 <h3 id=example>Example</h3>
 <p>As an example, consider the following <code>EXPLAIN</code> query:</p>
 <pre tabindex=0><code>EXPLAIN
-FROM src INSERT OVERWRITE TABLE dest\_g1 SELECT src.key, sum(substr(src.value,4)) GROUP BY src.key;
+FROM src INSERT OVERWRITE TABLE dest_g1 SELECT src.key, sum(substr(src.value,4)) GROUP BY src.key;
 </code></pre><p>The output of this statement contains the following parts:</p>
 <ul>
 <li>The Dependency Graph</li>
@@ -191,7 +191,7 @@ FROM src INSERT OVERWRITE TABLE dest\_g1 SELECT src.key, sum(substr(src.value,4)
             table:
                 input format: org.apache.hadoop.mapred.SequenceFileInputFormat
                 output format: org.apache.hadoop.mapred.SequenceFileOutputFormat
-                name: binary\_table
+                name: binary_table
 
   Stage: Stage-2
     Map Reduce
@@ -234,8 +234,8 @@ FROM src INSERT OVERWRITE TABLE dest\_g1 SELECT src.key, sum(substr(src.value,4)
                 table:
                     input format: org.apache.hadoop.mapred.TextInputFormat
                     output format: org.apache.hadoop.hive.ql.io.IgnoreKeyTextOutputFormat
-                    serde: org.apache.hadoop.hive.serde2.dynamic\_type.DynamicSerDe
-                    name: dest\_g1
+                    serde: org.apache.hadoop.hive.serde2.dynamic_type.DynamicSerDe
+                    name: dest_g1
 
   Stage: Stage-0
     Move Operator
@@ -244,8 +244,8 @@ FROM src INSERT OVERWRITE TABLE dest\_g1 SELECT src.key, sum(substr(src.value,4)
             table:
                 input format: org.apache.hadoop.mapred.TextInputFormat
                 output format: org.apache.hadoop.hive.ql.io.IgnoreKeyTextOutputFormat
-                serde: org.apache.hadoop.hive.serde2.dynamic\_type.DynamicSerDe
-                name: dest\_g1
+                serde: org.apache.hadoop.hive.serde2.dynamic_type.DynamicSerDe
+                name: dest_g1
 
 </code></pre><p>In this example there are 2 map/reduce stages (Stage-1 and Stage-2) and 1 File System related stage (Stage-0). Stage-0 basically moves the results from a temporary directory to the directory corresponding to the table dest_g1.<br>
 <code>Sort order</code> indicates the number of columns in key expressions that are used for sorting. Each &ldquo;<code>+</code>&rdquo; represents one column sorted in ascending order, and each &ldquo;<code>-</code>&rdquo; represents a column sorted in descending order.</p>
@@ -263,120 +263,120 @@ FROM src INSERT OVERWRITE TABLE dest\_g1 SELECT src.key, sum(substr(src.value,4)
 </ul>
 <p>For example, we can execute the following statement:</p>
 <pre tabindex=0><code>EXPLAIN CBO
-WITH customer\_total\_return AS
-(SELECT sr\_customer\_sk AS ctr\_customer\_sk,
-  sr\_store\_sk AS ctr\_store\_sk,
-  SUM(SR\_FEE) AS ctr\_total\_return
-  FROM store\_returns, date\_dim
-  WHERE sr\_returned\_date\_sk = d\_date\_sk
-    AND d\_year =2000
-  GROUP BY sr\_customer\_sk, sr\_store\_sk)
-SELECT c\_customer\_id
-FROM customer\_total\_return ctr1, store, customer
-WHERE ctr1.ctr\_total\_return &gt; (SELECT AVG(ctr\_total\_return)*1.2
-FROM customer\_total\_return ctr2
-WHERE ctr1.ctr\_store\_sk = ctr2.ctr\_store\_sk)
-  AND s\_store\_sk = ctr1.ctr\_store\_sk
-  AND s\_state = 'NM'
-  AND ctr1.ctr\_customer\_sk = c\_customer\_sk
-ORDER BY c\_customer\_id
+WITH customer_total_return AS
+(SELECT sr_customer_sk AS ctr_customer_sk,
+  sr_store_sk AS ctr_store_sk,
+  SUM(SR_FEE) AS ctr_total_return
+  FROM store_returns, date_dim
+  WHERE sr_returned_date_sk = d_date_sk
+    AND d_year =2000
+  GROUP BY sr_customer_sk, sr_store_sk)
+SELECT c_customer_id
+FROM customer_total_return ctr1, store, customer
+WHERE ctr1.ctr_total_return &gt; (SELECT AVG(ctr_total_return)*1.2
+FROM customer_total_return ctr2
+WHERE ctr1.ctr_store_sk = ctr2.ctr_store_sk)
+  AND s_store_sk = ctr1.ctr_store_sk
+  AND s_state = 'NM'
+  AND ctr1.ctr_customer_sk = c_customer_sk
+ORDER BY c_customer_id
 LIMIT 100
 
 </code></pre><p>The query will be optimized and Hive produces the following output:</p>
 <pre tabindex=0><code>CBO PLAN:
 HiveSortLimit(sort0=[$0], dir0=[ASC], fetch=[100])
-  HiveProject(c\_customer\_id=[$1])
+  HiveProject(c_customer_id=[$1])
     HiveJoin(condition=[AND(=($3, $7), &gt;($4, $6))], joinType=[inner], algorithm=[none], cost=[not available])
       HiveJoin(condition=[=($2, $0)], joinType=[inner], algorithm=[none], cost=[not available])
-        HiveProject(c\_customer\_sk=[$0], c\_customer\_id=[$1])
+        HiveProject(c_customer_sk=[$0], c_customer_id=[$1])
           HiveFilter(condition=[IS NOT NULL($0)])
             HiveTableScan(table=[[default, customer]], table:alias=[customer])
         HiveJoin(condition=[=($3, $1)], joinType=[inner], algorithm=[none], cost=[not available])
-          HiveProject(sr\_customer\_sk=[$0], sr\_store\_sk=[$1], $f2=[$2])
+          HiveProject(sr_customer_sk=[$0], sr_store_sk=[$1], $f2=[$2])
             HiveAggregate(group=[{1, 2}], agg#0=[sum($3)])
               HiveJoin(condition=[=($0, $4)], joinType=[inner], algorithm=[none], cost=[not available])
-                HiveProject(sr\_returned\_date\_sk=[$0], sr\_customer\_sk=[$3], sr\_store\_sk=[$7], sr\_fee=[$14])
+                HiveProject(sr_returned_date_sk=[$0], sr_customer_sk=[$3], sr_store_sk=[$7], sr_fee=[$14])
                   HiveFilter(condition=[AND(IS NOT NULL($0), IS NOT NULL($7), IS NOT NULL($3))])
-                    HiveTableScan(table=[[default, store\_returns]], table:alias=[store\_returns])
-                HiveProject(d\_date\_sk=[$0])
+                    HiveTableScan(table=[[default, store_returns]], table:alias=[store_returns])
+                HiveProject(d_date_sk=[$0])
                   HiveFilter(condition=[AND(=($6, 2000), IS NOT NULL($0))])
-                    HiveTableScan(table=[[default, date\_dim]], table:alias=[date\_dim])
-          HiveProject(s\_store\_sk=[$0])
-            HiveFilter(condition=[AND(=($24, \_UTF-16LE'NM'), IS NOT NULL($0))])
+                    HiveTableScan(table=[[default, date_dim]], table:alias=[date_dim])
+          HiveProject(s_store_sk=[$0])
+            HiveFilter(condition=[AND(=($24, _UTF-16LE'NM'), IS NOT NULL($0))])
               HiveTableScan(table=[[default, store]], table:alias=[store])
-      HiveProject(\_o\_\_c0=[*(/($1, $2), 1.2)], ctr\_store\_sk=[$0])
+      HiveProject(_o__c0=[*(/($1, $2), 1.2)], ctr_store_sk=[$0])
         HiveAggregate(group=[{1}], agg#0=[sum($2)], agg#1=[count($2)])
-          HiveProject(sr\_customer\_sk=[$0], sr\_store\_sk=[$1], $f2=[$2])
+          HiveProject(sr_customer_sk=[$0], sr_store_sk=[$1], $f2=[$2])
             HiveAggregate(group=[{1, 2}], agg#0=[sum($3)])
               HiveJoin(condition=[=($0, $4)], joinType=[inner], algorithm=[none], cost=[not available])
-                HiveProject(sr\_returned\_date\_sk=[$0], sr\_customer\_sk=[$3], sr\_store\_sk=[$7], sr\_fee=[$14])
+                HiveProject(sr_returned_date_sk=[$0], sr_customer_sk=[$3], sr_store_sk=[$7], sr_fee=[$14])
                   HiveFilter(condition=[AND(IS NOT NULL($0), IS NOT NULL($7))])
-                    HiveTableScan(table=[[default, store\_returns]], table:alias=[store\_returns])
-                HiveProject(d\_date\_sk=[$0])
+                    HiveTableScan(table=[[default, store_returns]], table:alias=[store_returns])
+                HiveProject(d_date_sk=[$0])
                   HiveFilter(condition=[AND(=($6, 2000), IS NOT NULL($0))])
-                    HiveTableScan(table=[[default, date\_dim]], table:alias=[date\_dim])
+                    HiveTableScan(table=[[default, date_dim]], table:alias=[date_dim])
 </code></pre><p>In turn, we can execute the following command:</p>
 <pre tabindex=0><code>EXPLAIN CBO COST
-WITH customer\_total\_return AS
-(SELECT sr\_customer\_sk AS ctr\_customer\_sk,
-  sr\_store\_sk AS ctr\_store\_sk,
-  SUM(SR\_FEE) AS ctr\_total\_return
-  FROM store\_returns, date\_dim
-  WHERE sr\_returned\_date\_sk = d\_date\_sk
-    AND d\_year =2000
-  GROUP BY sr\_customer\_sk, sr\_store\_sk)
-SELECT c\_customer\_id
-FROM customer\_total\_return ctr1, store, customer
-WHERE ctr1.ctr\_total\_return &gt; (SELECT AVG(ctr\_total\_return)*1.2
-FROM customer\_total\_return ctr2
-WHERE ctr1.ctr\_store\_sk = ctr2.ctr\_store\_sk)
-  AND s\_store\_sk = ctr1.ctr\_store\_sk
-  AND s\_state = 'NM'
-  AND ctr1.ctr\_customer\_sk = c\_customer\_sk
-ORDER BY c\_customer\_id
+WITH customer_total_return AS
+(SELECT sr_customer_sk AS ctr_customer_sk,
+  sr_store_sk AS ctr_store_sk,
+  SUM(SR_FEE) AS ctr_total_return
+  FROM store_returns, date_dim
+  WHERE sr_returned_date_sk = d_date_sk
+    AND d_year =2000
+  GROUP BY sr_customer_sk, sr_store_sk)
+SELECT c_customer_id
+FROM customer_total_return ctr1, store, customer
+WHERE ctr1.ctr_total_return &gt; (SELECT AVG(ctr_total_return)*1.2
+FROM customer_total_return ctr2
+WHERE ctr1.ctr_store_sk = ctr2.ctr_store_sk)
+  AND s_store_sk = ctr1.ctr_store_sk
+  AND s_state = 'NM'
+  AND ctr1.ctr_customer_sk = c_customer_sk
+ORDER BY c_customer_id
 LIMIT 100
 
 </code></pre><p>It will produce a similar plan, but the cost for each operator will be embedded next to the operator descriptors:</p>
 <pre tabindex=0><code>CBO PLAN:
 HiveSortLimit(sort0=[$0], dir0=[ASC], fetch=[100]): rowcount = 100.0, cumulative cost = {2.395588892021712E26 rows, 1.197794434438787E26 cpu, 0.0 io}, id = 1683
-  HiveProject(c\_customer\_id=[$1]): rowcount = 1.1977944344387866E26, cumulative cost = {2.395588892021712E26 rows, 1.197794434438787E26 cpu, 0.0 io}, id = 1681
+  HiveProject(c_customer_id=[$1]): rowcount = 1.1977944344387866E26, cumulative cost = {2.395588892021712E26 rows, 1.197794434438787E26 cpu, 0.0 io}, id = 1681
     HiveJoin(condition=[AND(=($3, $7), &gt;($4, $6))], joinType=[inner], algorithm=[none], cost=[not available]): rowcount = 1.1977944344387866E26, cumulative cost = {1.1977944575829254E26 rows, 4.160211553874922E10 cpu, 0.0 io}, id = 1679
       HiveJoin(condition=[=($2, $0)], joinType=[inner], algorithm=[none], cost=[not available]): rowcount = 2.3144135067474273E18, cumulative cost = {2.3144137967122499E18 rows, 1.921860676139634E10 cpu, 0.0 io}, id = 1663
-        HiveProject(c\_customer\_sk=[$0], c\_customer\_id=[$1]): rowcount = 7.2E7, cumulative cost = {2.24E8 rows, 3.04000001E8 cpu, 0.0 io}, id = 1640
+        HiveProject(c_customer_sk=[$0], c_customer_id=[$1]): rowcount = 7.2E7, cumulative cost = {2.24E8 rows, 3.04000001E8 cpu, 0.0 io}, id = 1640
           HiveFilter(condition=[IS NOT NULL($0)]): rowcount = 7.2E7, cumulative cost = {1.52E8 rows, 1.60000001E8 cpu, 0.0 io}, id = 1638
             HiveTableScan(table=[[default, customer]], table:alias=[customer]): rowcount = 8.0E7, cumulative cost = {8.0E7 rows, 8.0000001E7 cpu, 0.0 io}, id = 1055
         HiveJoin(condition=[=($3, $1)], joinType=[inner], algorithm=[none], cost=[not available]): rowcount = 2.1429754692105807E11, cumulative cost = {2.897408225471977E11 rows, 1.891460676039634E10 cpu, 0.0 io}, id = 1661
-          HiveProject(sr\_customer\_sk=[$0], sr\_store\_sk=[$1], $f2=[$2]): rowcount = 6.210443022113779E9, cumulative cost = {7.544327346205959E10 rows, 1.891460312135634E10 cpu, 0.0 io}, id = 1685
+          HiveProject(sr_customer_sk=[$0], sr_store_sk=[$1], $f2=[$2]): rowcount = 6.210443022113779E9, cumulative cost = {7.544327346205959E10 rows, 1.891460312135634E10 cpu, 0.0 io}, id = 1685
             HiveAggregate(group=[{1, 2}], agg#0=[sum($3)]): rowcount = 6.210443022113779E9, cumulative cost = {6.92328304399458E10 rows, 2.8327405501500005E8 cpu, 0.0 io}, id = 1654
               HiveJoin(condition=[=($0, $4)], joinType=[inner], algorithm=[none], cost=[not available]): rowcount = 6.2104430221137794E10, cumulative cost = {6.2246082040067795E10 rows, 2.8327405501500005E8 cpu, 0.0 io}, id = 1652
-                HiveProject(sr\_returned\_date\_sk=[$0], sr\_customer\_sk=[$3], sr\_store\_sk=[$7], sr\_fee=[$14]): rowcount = 4.198394835000001E7, cumulative cost = {1.4155904670000002E8 rows, 2.8311809440000004E8 cpu, 0.0 io}, id = 1645
+                HiveProject(sr_returned_date_sk=[$0], sr_customer_sk=[$3], sr_store_sk=[$7], sr_fee=[$14]): rowcount = 4.198394835000001E7, cumulative cost = {1.4155904670000002E8 rows, 2.8311809440000004E8 cpu, 0.0 io}, id = 1645
                   HiveFilter(condition=[AND(IS NOT NULL($0), IS NOT NULL($7), IS NOT NULL($3))]): rowcount = 4.198394835000001E7, cumulative cost = {9.957509835000001E7 rows, 1.15182301E8 cpu, 0.0 io}, id = 1643
-                    HiveTableScan(table=[[default, store\_returns]], table:alias=[store\_returns]): rowcount = 5.759115E7, cumulative cost = {5.759115E7 rows, 5.7591151E7 cpu, 0.0 io}, id = 1040
-                HiveProject(d\_date\_sk=[$0]): rowcount = 9861.615, cumulative cost = {92772.23000000001 rows, 155960.615 cpu, 0.0 io}, id = 1650
+                    HiveTableScan(table=[[default, store_returns]], table:alias=[store_returns]): rowcount = 5.759115E7, cumulative cost = {5.759115E7 rows, 5.7591151E7 cpu, 0.0 io}, id = 1040
+                HiveProject(d_date_sk=[$0]): rowcount = 9861.615, cumulative cost = {92772.23000000001 rows, 155960.615 cpu, 0.0 io}, id = 1650
                   HiveFilter(condition=[AND(=($6, 2000), IS NOT NULL($0))]): rowcount = 9861.615, cumulative cost = {82910.615 rows, 146099.0 cpu, 0.0 io}, id = 1648
-                    HiveTableScan(table=[[default, date\_dim]], table:alias=[date\_dim]): rowcount = 73049.0, cumulative cost = {73049.0 rows, 73050.0 cpu, 0.0 io}, id = 1043
-          HiveProject(s\_store\_sk=[$0]): rowcount = 230.04000000000002, cumulative cost = {2164.08 rows, 3639.04 cpu, 0.0 io}, id = 1659
-            HiveFilter(condition=[AND(=($24, \_UTF-16LE'NM'), IS NOT NULL($0))]): rowcount = 230.04000000000002, cumulative cost = {1934.04 rows, 3409.0 cpu, 0.0 io}, id = 1657
+                    HiveTableScan(table=[[default, date_dim]], table:alias=[date_dim]): rowcount = 73049.0, cumulative cost = {73049.0 rows, 73050.0 cpu, 0.0 io}, id = 1043
+          HiveProject(s_store_sk=[$0]): rowcount = 230.04000000000002, cumulative cost = {2164.08 rows, 3639.04 cpu, 0.0 io}, id = 1659
+            HiveFilter(condition=[AND(=($24, _UTF-16LE'NM'), IS NOT NULL($0))]): rowcount = 230.04000000000002, cumulative cost = {1934.04 rows, 3409.0 cpu, 0.0 io}, id = 1657
               HiveTableScan(table=[[default, store]], table:alias=[store]): rowcount = 1704.0, cumulative cost = {1704.0 rows, 1705.0 cpu, 0.0 io}, id = 1050
-      HiveProject(\_o\_\_c0=[*(/($1, $2), 1.2)], ctr\_store\_sk=[$0]): rowcount = 6.900492246793088E8, cumulative cost = {8.537206083312463E10 rows, 2.2383508777352882E10 cpu, 0.0 io}, id = 1677
+      HiveProject(_o__c0=[*(/($1, $2), 1.2)], ctr_store_sk=[$0]): rowcount = 6.900492246793088E8, cumulative cost = {8.537206083312463E10 rows, 2.2383508777352882E10 cpu, 0.0 io}, id = 1677
         HiveAggregate(group=[{1}], agg#0=[sum($2)], agg#1=[count($2)]): rowcount = 6.900492246793088E8, cumulative cost = {8.468201160844533E10 rows, 2.1003410327994267E10 cpu, 0.0 io}, id = 1675
-          HiveProject(sr\_customer\_sk=[$0], sr\_store\_sk=[$1], $f2=[$2]): rowcount = 6.900492246793088E9, cumulative cost = {8.381945007759619E10 rows, 2.1003410327994267E10 cpu, 0.0 io}, id = 1686
+          HiveProject(sr_customer_sk=[$0], sr_store_sk=[$1], $f2=[$2]): rowcount = 6.900492246793088E9, cumulative cost = {8.381945007759619E10 rows, 2.1003410327994267E10 cpu, 0.0 io}, id = 1686
             HiveAggregate(group=[{1, 2}], agg#0=[sum($3)]): rowcount = 6.900492246793088E9, cumulative cost = {7.69189578308031E10 rows, 3.01933587615E8 cpu, 0.0 io}, id = 1673
               HiveJoin(condition=[=($0, $4)], joinType=[inner], algorithm=[none], cost=[not available]): rowcount = 6.900492246793088E10, cumulative cost = {6.915590405316087E10 rows, 3.01933587615E8 cpu, 0.0 io}, id = 1671
-                HiveProject(sr\_returned\_date\_sk=[$0], sr\_customer\_sk=[$3], sr\_store\_sk=[$7], sr\_fee=[$14]): rowcount = 4.66488315E7, cumulative cost = {1.50888813E8 rows, 3.01777627E8 cpu, 0.0 io}, id = 1667
+                HiveProject(sr_returned_date_sk=[$0], sr_customer_sk=[$3], sr_store_sk=[$7], sr_fee=[$14]): rowcount = 4.66488315E7, cumulative cost = {1.50888813E8 rows, 3.01777627E8 cpu, 0.0 io}, id = 1667
                   HiveFilter(condition=[AND(IS NOT NULL($0), IS NOT NULL($7))]): rowcount = 4.66488315E7, cumulative cost = {1.042399815E8 rows, 1.15182301E8 cpu, 0.0 io}, id = 1665
-                    HiveTableScan(table=[[default, store\_returns]], table:alias=[store\_returns]): rowcount = 5.759115E7, cumulative cost = {5.759115E7 rows, 5.7591151E7 cpu, 0.0 io}, id = 1040
-                HiveProject(d\_date\_sk=[$0]): rowcount = 9861.615, cumulative cost = {92772.23000000001 rows, 155960.615 cpu, 0.0 io}, id = 1650
+                    HiveTableScan(table=[[default, store_returns]], table:alias=[store_returns]): rowcount = 5.759115E7, cumulative cost = {5.759115E7 rows, 5.7591151E7 cpu, 0.0 io}, id = 1040
+                HiveProject(d_date_sk=[$0]): rowcount = 9861.615, cumulative cost = {92772.23000000001 rows, 155960.615 cpu, 0.0 io}, id = 1650
                   HiveFilter(condition=[AND(=($6, 2000), IS NOT NULL($0))]): rowcount = 9861.615, cumulative cost = {82910.615 rows, 146099.0 cpu, 0.0 io}, id = 1648
-                    HiveTableScan(table=[[default, date\_dim]], table:alias=[date\_dim]): rowcount = 73049.0, cumulative cost = {73049.0 rows, 73050.0 cpu, 0.0 io}, id = 1043
+                    HiveTableScan(table=[[default, date_dim]], table:alias=[date_dim]): rowcount = 73049.0, cumulative cost = {73049.0 rows, 73050.0 cpu, 0.0 io}, id = 1043
 </code></pre><h3 id=the-ast-clause>The AST Clause</h3>
 <p>Outputs the query&rsquo;s Abstract Syntax Tree.</p>
 <p>Example:</p>
 <pre tabindex=0><code>EXPLAIN AST
-FROM src INSERT OVERWRITE TABLE dest\_g1 SELECT src.key, sum(substr(src.value,4)) GROUP BY src.key;
+FROM src INSERT OVERWRITE TABLE dest_g1 SELECT src.key, sum(substr(src.value,4)) GROUP BY src.key;
 </code></pre><p>Outputs:</p>
 <pre tabindex=0><code>ABSTRACT SYNTAX TREE:
-  (TOK\_QUERY (TOK\_FROM (TOK\_TABREF src)) (TOK\_INSERT (TOK\_DESTINATION (TOK\_TAB dest\_g1)) (TOK\_SELECT (TOK\_SELEXPR (TOK\_COLREF src key)) (TOK\_SELEXPR (TOK\_FUNCTION sum (TOK\_FUNCTION substr (TOK\_COLREF src value) 4)))) (TOK\_GROUPBY (TOK\_COLREF src key))))
+  (TOK_QUERY (TOK_FROM (TOK_TABREF src)) (TOK_INSERT (TOK_DESTINATION (TOK_TAB dest_g1)) (TOK_SELECT (TOK_SELEXPR (TOK_COLREF src key)) (TOK_SELEXPR (TOK_FUNCTION sum (TOK_FUNCTION substr (TOK_COLREF src value) 4)))) (TOK_GROUPBY (TOK_COLREF src key))))
 
 </code></pre><h3 id=the-dependency-clause>The DEPENDENCY Clause</h3>
 <p>The use of <code>DEPENDENCY</code> in the <code>EXPLAIN</code> statement produces extra information about the inputs in the plan. It shows various attributes for the inputs. For example, for a query like:</p>
@@ -384,7 +384,7 @@ FROM src INSERT OVERWRITE TABLE dest\_g1 SELECT src.key, sum(substr(src.value,4)
   SELECT key, count(1) FROM srcpart WHERE ds IS NOT NULL GROUP BY key
 
 </code></pre><p>the following output is produced:</p>
-<pre tabindex=0><code>{&quot;input\_partitions&quot;:[{&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-08/hr=11&quot;},{&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-08/hr=12&quot;},{&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-09/hr=11&quot;},{&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-09/hr=12&q [...]
+<pre tabindex=0><code>{&quot;input_partitions&quot;:[{&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-08/hr=11&quot;},{&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-08/hr=12&quot;},{&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-09/hr=11&quot;},{&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-09/hr=12&qu [...]
 
 </code></pre><p>The inputs contain both the tables and the partitions. Note that the table is present even if none of the partitions is accessed in the query.</p>
 <p>The dependencies show the parents in case a table is accessed via a view. Consider the following queries:</p>
@@ -392,7 +392,7 @@ FROM src INSERT OVERWRITE TABLE dest\_g1 SELECT src.key, sum(substr(src.value,4)
 EXPLAIN DEPENDENCY SELECT * FROM V1;
 
 </code></pre><p>The following output is produced:</p>
-<pre tabindex=0><code>{&quot;input\_partitions&quot;:[],&quot;input\_tables&quot;:[{&quot;tablename&quot;:&quot;default@v1&quot;,&quot;tabletype&quot;:&quot;VIRTUAL\_VIEW&quot;},{&quot;tablename&quot;:&quot;default@src&quot;,&quot;tabletype&quot;:&quot;MANAGED\_TABLE&quot;,&quot;tableParents&quot;:&quot;[default@v1]&quot;}]}
+<pre tabindex=0><code>{&quot;input_partitions&quot;:[],&quot;input_tables&quot;:[{&quot;tablename&quot;:&quot;default@v1&quot;,&quot;tabletype&quot;:&quot;VIRTUAL_VIEW&quot;},{&quot;tablename&quot;:&quot;default@src&quot;,&quot;tabletype&quot;:&quot;MANAGED_TABLE&quot;,&quot;tableParents&quot;:&quot;[default@v1]&quot;}]}
 
 </code></pre><p>As above, the inputs contain the view V1 and the table &lsquo;src&rsquo; that the view V1 refers to.</p>
 <p>All the outputs are shown if a table is being accessed via multiple parents.</p>
@@ -403,7 +403,7 @@ CREATE VIEW V4 AS
 EXPLAIN DEPENDENCY SELECT * FROM V4;
 
 </code></pre><p>The following output is produced.</p>
-<pre tabindex=0><code>{&quot;input\_partitions&quot;:[{&quot;partitionParents&quot;:&quot;[default@v2]&quot;,&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-08/hr=11&quot;},{&quot;partitionParents&quot;:&quot;[default@v2]&quot;,&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-08/hr=12&quot;},{&quot;partitionParents&quot;:&quot;[default@v2]&quot;,&quot;partitionName&quot;:&quot;default&lt;at:var at: [...]
+<pre tabindex=0><code>{&quot;input_partitions&quot;:[{&quot;partitionParents&quot;:&quot;[default@v2]&quot;,&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-08/hr=11&quot;},{&quot;partitionParents&quot;:&quot;[default@v2]&quot;,&quot;partitionName&quot;:&quot;default&lt;at:var at:name=&quot;srcpart&quot; /&gt;ds=2008-04-08/hr=12&quot;},{&quot;partitionParents&quot;:&quot;[default@v2]&quot;,&quot;partitionName&quot;:&quot;default&lt;at:var at:n [...]
 
 </code></pre><p>As can be seen, src is being accessed via parents v1 and v4.</p>
 <h3 id=the-authorization-clause>The AUTHORIZATION Clause</h3>
@@ -421,17 +421,17 @@ EXPLAIN DEPENDENCY SELECT * FROM V4;
   default@srcpart@ds=2008-04-09/hr=12
 OUTPUTS: 
   hdfs://localhost:9000/tmp/.../-mr-10000
-CURRENT\_USER: 
+CURRENT_USER: 
   navis
 OPERATION: 
   QUERY
-AUTHORIZATION\_FAILURES: 
-  Permission denied: Principal [name=navis, type=USER] does not have following privileges for operation QUERY [[SELECT] on Object [type=TABLE\_OR\_VIEW, name=default.src], [SELECT] on Object [type=TABLE\_OR\_VIEW, name=default.srcpart]]
+AUTHORIZATION_FAILURES: 
+  Permission denied: Principal [name=navis, type=USER] does not have following privileges for operation QUERY [[SELECT] on Object [type=TABLE_OR_VIEW, name=default.src], [SELECT] on Object [type=TABLE_OR_VIEW, name=default.srcpart]]
 
 </code></pre><p>With the <code>FORMATTED</code> keyword, it will be returned in JSON format.</p>
 <pre tabindex=0><code>  
 
-</code></pre><pre tabindex=0><code>&quot;OUTPUTS&quot;:[&quot;hdfs://localhost:9000/tmp/.../-mr-10000&quot;],&quot;INPUTS&quot;:[&quot;default@srcpart&quot;,&quot;default@src&quot;,&quot;default@srcpart@ds=2008-04-08/hr=11&quot;,&quot;default@srcpart@ds=2008-04-08/hr=12&quot;,&quot;default@srcpart@ds=2008-04-09/hr=11&quot;,&quot;default@srcpart@ds=2008-04-09/hr=12&quot;],&quot;OPERATION&quot;:&quot;QUERY&quot;,&quot;CURRENT\_USER&quot;:&quot;navis&quot;,&quot;AUTHORIZATION\_FAILURES&quot [...]
+</code></pre><pre tabindex=0><code>&quot;OUTPUTS&quot;:[&quot;hdfs://localhost:9000/tmp/.../-mr-10000&quot;],&quot;INPUTS&quot;:[&quot;default@srcpart&quot;,&quot;default@src&quot;,&quot;default@srcpart@ds=2008-04-08/hr=11&quot;,&quot;default@srcpart@ds=2008-04-08/hr=12&quot;,&quot;default@srcpart@ds=2008-04-09/hr=11&quot;,&quot;default@srcpart@ds=2008-04-09/hr=12&quot;],&quot;OPERATION&quot;:&quot;QUERY&quot;,&quot;CURRENT_USER&quot;:&quot;navis&quot;,&quot;AUTHORIZATION_FAILURES&quot;: [...]
 
 </code></pre><h3 id=the-locks-clause>The LOCKS Clause</h3>
 <p>This is useful to understand what locks the system will acquire to run the specified query.  Since Hive release 3.2.0 (<a href=https://issues.apache.org/jira/browse/HIVE-17683>HIVE-17683</a>).</p>
@@ -440,13 +440,13 @@ AUTHORIZATION\_FAILURES:
 
 </code></pre><p>Will produce output like this.</p>
 <pre tabindex=0><code>LOCK INFORMATION:
-default.source -&gt; SHARED\_READ
-default.target.p=1/q=2 -&gt; SHARED\_READ
-default.target.p=1/q=3 -&gt; SHARED\_READ
-default.target.p=2/q=2 -&gt; SHARED\_READ
-default.target.p=2/q=2 -&gt; SHARED\_WRITE
-default.target.p=1/q=3 -&gt; SHARED\_WRITE
-default.target.p=1/q=2 -&gt; SHARED\_WRITE
+default.source -&gt; SHARED_READ
+default.target.p=1/q=2 -&gt; SHARED_READ
+default.target.p=1/q=3 -&gt; SHARED_READ
+default.target.p=2/q=2 -&gt; SHARED_READ
+default.target.p=2/q=2 -&gt; SHARED_WRITE
+default.target.p=1/q=3 -&gt; SHARED_WRITE
+default.target.p=1/q=2 -&gt; SHARED_WRITE
 </code></pre><pre tabindex=0><code>  
 
 </code></pre><pre tabindex=0><code>EXPLAIN FORMATTED LOCKS &lt;sql&gt;
@@ -470,7 +470,7 @@ default.target.p=1/q=2 -&gt; SHARED\_WRITE
 <p>Example:</p>
 <p>For the below tablescan; the estimation was 500 rows; but actually the scan only yielded 13 rows.</p>
 <pre tabindex=0><code>[...]
-              TableScan [TS\_13] (rows=500/13 width=178)
+              TableScan [TS_13] (rows=500/13 width=178)
                 Output:[&quot;key&quot;,&quot;value&quot;]
 [...]
 </code></pre><h3 id=user-level-explain-output>User-level Explain Output</h3>
@@ -478,37 +478,37 @@ default.target.p=1/q=2 -&gt; SHARED\_WRITE
 <p>Since <a href=https://issues.apache.org/jira/browse/HIVE-18469>HIVE-18469</a> in Hive 3.1.0, the user-level explain extended output for any query will be shown in the WebUI / Drilldown / Query Plan after <strong>set <a href=#hive-server2-webui-explain-output>hive.server2.webui.explain.output</a>=true</strong> (default is <strong>false</strong>).</p>
 <p>Since <a href=https://issues.apache.org/jira/browse/HIVE-9780>HIVE-9780</a> in Hive 1.2.0, we support a user-level explain for Hive on Tez users. After <strong>set <a href=#hive-explain-user>hive.explain.user</a>=true</strong> (default is <strong>false</strong>) if the following query is sent, the user can see a much more clearly readable tree of operations.</p>
 <p>Since <a href=https://issues.apache.org/jira/browse/HIVE-11133>HIVE-11133</a> in Hive 3.0.0, we support a user-level explain for Hive on Spark users. A separate configuration is used for Hive-on-Spark, <strong><a href=#hive-spark-explain-user>hive.spark.explain.user</a></strong> which is set to false by default.</p>
-<pre tabindex=0><code>EXPLAIN select sum(hash(key)), sum(hash(value)) from src\_orc\_merge\_test\_part where ds='2012-01-03' and ts='2012-01-03+14:46:31'
+<pre tabindex=0><code>EXPLAIN select sum(hash(key)), sum(hash(value)) from src_orc_merge_test_part where ds='2012-01-03' and ts='2012-01-03+14:46:31'
 </code></pre><pre tabindex=0><code>Plan optimized by CBO.
 Vertex dependency in root stage
-Reducer 2 &lt;- Map 1 (SIMPLE\_EDGE)
+Reducer 2 &lt;- Map 1 (SIMPLE_EDGE)
 Stage-0
    Fetch Operator
       limit:-1
       Stage-1
          Reducer 2
-         File Output Operator [FS\_8]
+         File Output Operator [FS_8]
             compressed:false
             Statistics:Num rows: 1 Data size: 16 Basic stats: COMPLETE Column stats: NONE
             table:{&quot;serde:&quot;:&quot;org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe&quot;,&quot;input format:&quot;:&quot;org.apache.hadoop.mapred.TextInputFormat&quot;,&quot;output format:&quot;:&quot;org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat&quot;}
-            Group By Operator [GBY\_6]
-            |  aggregations:[&quot;sum(VALUE.\_col0)&quot;,&quot;sum(VALUE.\_col1)&quot;]
-            |  outputColumnNames:[&quot;\_col0&quot;,&quot;\_col1&quot;]
+            Group By Operator [GBY_6]
+            |  aggregations:[&quot;sum(VALUE._col0)&quot;,&quot;sum(VALUE._col1)&quot;]
+            |  outputColumnNames:[&quot;_col0&quot;,&quot;_col1&quot;]
             |  Statistics:Num rows: 1 Data size: 16 Basic stats: COMPLETE Column stats: NONE
-            |&lt;-Map 1 [SIMPLE\_EDGE]
-               Reduce Output Operator [RS\_5]
+            |&lt;-Map 1 [SIMPLE_EDGE]
+               Reduce Output Operator [RS_5]
                   sort order:
                   Statistics:Num rows: 1 Data size: 16 Basic stats: COMPLETE Column stats: NONE
-                  value expressions:\_col0 (type: bigint), \_col1 (type: bigint)
-                  Group By Operator [GBY\_4]
-                     aggregations:[&quot;sum(\_col0)&quot;,&quot;sum(\_col1)&quot;]
-                     outputColumnNames:[&quot;\_col0&quot;,&quot;\_col1&quot;]
+                  value expressions:_col0 (type: bigint), _col1 (type: bigint)
+                  Group By Operator [GBY_4]
+                     aggregations:[&quot;sum(_col0)&quot;,&quot;sum(_col1)&quot;]
+                     outputColumnNames:[&quot;_col0&quot;,&quot;_col1&quot;]
                      Statistics:Num rows: 1 Data size: 16 Basic stats: COMPLETE Column stats: NONE
-                     Select Operator [SEL\_2]
-                        outputColumnNames:[&quot;\_col0&quot;,&quot;\_col1&quot;]
+                     Select Operator [SEL_2]
+                        outputColumnNames:[&quot;_col0&quot;,&quot;_col1&quot;]
                         Statistics:Num rows: 500 Data size: 47000 Basic stats: COMPLETE Column stats: NONE
-                        TableScan [TS\_0]
-                           alias:src\_orc\_merge\_test\_part
+                        TableScan [TS_0]
+                           alias:src_orc_merge_test_part
                            Statistics:Num rows: 500 Data size: 47000 Basic stats: COMPLETE Column stats: NONE
 
 </code></pre>
diff --git a/docs/latest/languagemanual-groupby_27362038/index.html b/docs/latest/languagemanual-groupby_27362038/index.html
index 8466250..6d5efd9 100644
--- a/docs/latest/languagemanual-groupby_27362038/index.html
+++ b/docs/latest/languagemanual-groupby_27362038/index.html
@@ -148,23 +148,23 @@ groupByQuery: SELECT expression (, expression)* FROM src groupByClause?
 
 </code></pre><p>Note that for versions of Hive which don&rsquo;t include <a href=https://issues.apache.org/jira/browse/HIVE-287>HIVE-287</a>, you&rsquo;ll need to use COUNT(1) in place of COUNT(*).</p>
 <p>In order to count the number of distinct users by gender one could write the following query:</p>
-<pre tabindex=0><code>  INSERT OVERWRITE TABLE pv\_gender\_sum
-  SELECT pv\_users.gender, count (DISTINCT pv\_users.userid)
-  FROM pv\_users
-  GROUP BY pv\_users.gender;
+<pre tabindex=0><code>  INSERT OVERWRITE TABLE pv_gender_sum
+  SELECT pv_users.gender, count (DISTINCT pv_users.userid)
+  FROM pv_users
+  GROUP BY pv_users.gender;
 
 </code></pre><p>Multiple aggregations can be done at the same time, however, no two aggregations can have different DISTINCT columns. For example, the following is possible because count(DISTINCT) and sum(DISTINCT) specify the same column:</p>
-<pre tabindex=0><code>  INSERT OVERWRITE TABLE pv\_gender\_agg
-  SELECT pv\_users.gender, count(DISTINCT pv\_users.userid), count(*), sum(DISTINCT pv\_users.userid)
-  FROM pv\_users
-  GROUP BY pv\_users.gender;
+<pre tabindex=0><code>  INSERT OVERWRITE TABLE pv_gender_agg
+  SELECT pv_users.gender, count(DISTINCT pv_users.userid), count(*), sum(DISTINCT pv_users.userid)
+  FROM pv_users
+  GROUP BY pv_users.gender;
 
 </code></pre><p>Note that for versions of Hive which don&rsquo;t include <a href=https://issues.apache.org/jira/browse/HIVE-287>HIVE-287</a>, you&rsquo;ll need to use COUNT(1) in place of COUNT(*).</p>
 <p>However, the following query is not allowed. We don&rsquo;t allow multiple DISTINCT expressions in the same query.</p>
-<pre tabindex=0><code>  INSERT OVERWRITE TABLE pv\_gender\_agg
-  SELECT pv\_users.gender, count(DISTINCT pv\_users.userid), count(DISTINCT pv\_users.ip)
-  FROM pv\_users
-  GROUP BY pv\_users.gender;
+<pre tabindex=0><code>  INSERT OVERWRITE TABLE pv_gender_agg
+  SELECT pv_users.gender, count(DISTINCT pv_users.userid), count(DISTINCT pv_users.ip)
+  FROM pv_users
+  GROUP BY pv_users.gender;
 
 </code></pre><h3 id=select-statement-and-group-by-clause>Select statement and group by clause</h3>
 <p>When using group by clause, the select statement can only include columns included in the group by clause. Of course, you can have as many aggregation functions (e.g. <code>count</code>) in the select statement as well.<br>
@@ -201,13 +201,13 @@ GROUP BY
 <h2 id=advanced-features>Advanced Features</h2>
 <h3 id=multi-group-by-inserts>Multi-Group-By Inserts</h3>
 <p>The output of the aggregations or simple selects can be further sent into multiple tables or even to hadoop dfs files (which can then be manipulated using hdfs utilitites). e.g. if along with the gender breakdown, one needed to find the breakdown of unique page views by age, one could accomplish that with the following query:</p>
-<pre tabindex=0><code>  FROM pv\_users 
-  INSERT OVERWRITE TABLE pv\_gender\_sum
-    SELECT pv\_users.gender, count(DISTINCT pv\_users.userid) 
-    GROUP BY pv\_users.gender 
-  INSERT OVERWRITE DIRECTORY '/user/facebook/tmp/pv\_age\_sum'
-    SELECT pv\_users.age, count(DISTINCT pv\_users.userid) 
-    GROUP BY pv\_users.age; 
+<pre tabindex=0><code>  FROM pv_users 
+  INSERT OVERWRITE TABLE pv_gender_sum
+    SELECT pv_users.gender, count(DISTINCT pv_users.userid) 
+    GROUP BY pv_users.gender 
+  INSERT OVERWRITE DIRECTORY '/user/facebook/tmp/pv_age_sum'
+    SELECT pv_users.age, count(DISTINCT pv_users.userid) 
+    GROUP BY pv_users.age; 
 
 </code></pre><h3 id=map-side-aggregation-for-group-by>Map-side Aggregation for Group By</h3>
 <p><em>hive.map.aggr</em> controls how we do aggregations. The default is false. If it is set to true, Hive will do the first-level aggregation directly in the map task.<br>
diff --git a/docs/latest/languagemanual-importexport_27837968/index.html b/docs/latest/languagemanual-importexport_27837968/index.html
index ff852fc..d95d988 100644
--- a/docs/latest/languagemanual-importexport_27837968/index.html
+++ b/docs/latest/languagemanual-importexport_27837968/index.html
@@ -137,12 +137,12 @@ ASF
 <p>The <code>EXPORT</code> and <code>IMPORT</code> commands work independently of the source and target metastore DBMS used; for example, they can be used between Derby and MySQL databases.</p>
 <p><code>IMPORT</code> will create target table/partition if it does not exist.  All the table properties/parameters will be that of table that was used in <code>EXPORT</code> to generate the archive.  If target exists, checks are performed that it has appropriate schema, Input/OutputFormat, etc.  If target table exists and is not partitioned, it must be empty.  If target table exists and is partitioned, partitions being imported must not exist in the table.  </p>
 <h3 id=export-syntax>Export Syntax</h3>
-<pre tabindex=0><code>EXPORT TABLE tablename [PARTITION (part\_column=&quot;value&quot;[, ...])] 
-  TO 'export\_target\_path' [ FOR replication('eventid') ]
+<pre tabindex=0><code>EXPORT TABLE tablename [PARTITION (part_column=&quot;value&quot;[, ...])] 
+  TO 'export_target_path' [ FOR replication('eventid') ]
 </code></pre><h3 id=import-syntax>Import Syntax</h3>
-<pre tabindex=0><code>IMPORT [[EXTERNAL] TABLE new\_or\_original\_tablename [PARTITION (part\_column=&quot;value&quot;[, ...])]] 
-  FROM 'source\_path' 
-  [LOCATION 'import\_target\_path']
+<pre tabindex=0><code>IMPORT [[EXTERNAL] TABLE new_or_original_tablename [PARTITION (part_column=&quot;value&quot;[, ...])]] 
+  FROM 'source_path' 
+  [LOCATION 'import_target_path']
 
 </code></pre><h3 id=replication-usage>Replication usage</h3>
 <p>The <code>EXPORT</code> and <code>IMPORT</code> commands behave slightly differently when used in the context of replication, and are intended to be used by tools that perform replication between hive warehouses. In most cases, end users will not need to use this additional tag, except when doing a manual bootstrap of a replication-destination warehouse so that an incremental replication tool can take over from that point.</p>
@@ -151,29 +151,29 @@ ASF
 <p>For those using EXPORT for the first-time manual bootstrapping usecase, users are recommended to use a " FOR replication(&lsquo;bootstrapping&rsquo;) " tag. (Advanced users note : The choice of &ldquo;bootstrapping&rdquo; here is arbitrary-ish, and could just as well have been &ldquo;foo&rdquo;. The real goal is to have a value such that all further incremental replication ids will be greater than this original id. Thus, the integral value of this initial id should be 0, and thus, any [...]
 <h3 id=examples>Examples</h3>
 <p>Simple export and import:</p>
-<pre tabindex=0><code>export table department to 'hdfs\_exports\_location/department';
-import from 'hdfs\_exports\_location/department';
+<pre tabindex=0><code>export table department to 'hdfs_exports_location/department';
+import from 'hdfs_exports_location/department';
 
 </code></pre><p>Rename table on import:</p>
-<pre tabindex=0><code>export table department to 'hdfs\_exports\_location/department';
-import table imported\_dept from 'hdfs\_exports\_location/department';
+<pre tabindex=0><code>export table department to 'hdfs_exports_location/department';
+import table imported_dept from 'hdfs_exports_location/department';
 
 </code></pre><p>Export partition and import:</p>
-<pre tabindex=0><code>export table employee partition (emp\_country=&quot;in&quot;, emp\_state=&quot;ka&quot;) to 'hdfs\_exports\_location/employee';
-import from 'hdfs\_exports\_location/employee';
+<pre tabindex=0><code>export table employee partition (emp_country=&quot;in&quot;, emp_state=&quot;ka&quot;) to 'hdfs_exports_location/employee';
+import from 'hdfs_exports_location/employee';
 
 </code></pre><p>Export table and import partition:</p>
-<pre tabindex=0><code>export table employee to 'hdfs\_exports\_location/employee';
-import table employee partition (emp\_country=&quot;us&quot;, emp\_state=&quot;tn&quot;) from 'hdfs\_exports\_location/employee';
+<pre tabindex=0><code>export table employee to 'hdfs_exports_location/employee';
+import table employee partition (emp_country=&quot;us&quot;, emp_state=&quot;tn&quot;) from 'hdfs_exports_location/employee';
 
 </code></pre><p>Specify the import location:</p>
-<pre tabindex=0><code>export table department to 'hdfs\_exports\_location/department';
-import table department from 'hdfs\_exports\_location/department' 
-       location 'import\_target\_location/department';
+<pre tabindex=0><code>export table department to 'hdfs_exports_location/department';
+import table department from 'hdfs_exports_location/department' 
+       location 'import_target_location/department';
 
 </code></pre><p>Import as an external table:</p>
-<pre tabindex=0><code>export table department to 'hdfs\_exports\_location/department';
-import external table department from 'hdfs\_exports\_location/department';
+<pre tabindex=0><code>export table department to 'hdfs_exports_location/department';
+import external table department from 'hdfs_exports_location/department';
 
 </code></pre>
 </div>
diff --git a/docs/latest/languagemanual-indexing_31822176/index.html b/docs/latest/languagemanual-indexing_31822176/index.html
index c98fe3a..517d519 100644
--- a/docs/latest/languagemanual-indexing_31822176/index.html
+++ b/docs/latest/languagemanual-indexing_31822176/index.html
@@ -155,42 +155,42 @@ ASF
 <p>In Hive 0.12.0 and earlier releases, the index name is case-sensitive for CREATE INDEX and DROP INDEX statements. However, ALTER INDEX requires an index name that was created with lowercase letters (see <a href=https://issues.apache.org/jira/browse/HIVE-2752>HIVE-2752</a>). This bug is fixed in <a href=https://issues.apache.org/jira/browse/HIVE-2752>Hive 0.13.0</a> by making index names case-insensitive for all HiveQL statements. For releases prior to 0.13.0, the best practice is to u [...]
 <p> </p>
 <p>Create/build, show, and drop index:</p>
-<pre tabindex=0><code>CREATE INDEX table01\_index ON TABLE table01 (column2) AS 'COMPACT';
+<pre tabindex=0><code>CREATE INDEX table01_index ON TABLE table01 (column2) AS 'COMPACT';
 SHOW INDEX ON table01;
-DROP INDEX table01\_index ON table01;
+DROP INDEX table01_index ON table01;
 
 </code></pre><p>Create then build, show formatted (with column names), and drop index:</p>
-<pre tabindex=0><code>CREATE INDEX table02\_index ON TABLE table02 (column3) AS 'COMPACT' WITH DEFERRED REBUILD;
-ALTER INDEX table02\_index ON table2 REBUILD;
+<pre tabindex=0><code>CREATE INDEX table02_index ON TABLE table02 (column3) AS 'COMPACT' WITH DEFERRED REBUILD;
+ALTER INDEX table02_index ON table2 REBUILD;
 SHOW FORMATTED INDEX ON table02;
-DROP INDEX table02\_index ON table02;
+DROP INDEX table02_index ON table02;
 
 </code></pre><p>Create bitmap index, build, show, and drop:</p>
-<pre tabindex=0><code>CREATE INDEX table03\_index ON TABLE table03 (column4) AS 'BITMAP' WITH DEFERRED REBUILD;
-ALTER INDEX table03\_index ON table03 REBUILD;
+<pre tabindex=0><code>CREATE INDEX table03_index ON TABLE table03 (column4) AS 'BITMAP' WITH DEFERRED REBUILD;
+ALTER INDEX table03_index ON table03 REBUILD;
 SHOW FORMATTED INDEX ON table03;
-DROP INDEX table03\_index ON table03;
+DROP INDEX table03_index ON table03;
 
 </code></pre><p>Create index in a new table:</p>
-<pre tabindex=0><code>CREATE INDEX table04\_index ON TABLE table04 (column5) AS 'COMPACT' WITH DEFERRED REBUILD IN TABLE table04\_index\_table;
+<pre tabindex=0><code>CREATE INDEX table04_index ON TABLE table04 (column5) AS 'COMPACT' WITH DEFERRED REBUILD IN TABLE table04_index_table;
 
 </code></pre><p>Create index stored as RCFile:</p>
-<pre tabindex=0><code>CREATE INDEX table05\_index ON TABLE table05 (column6) AS 'COMPACT' STORED AS RCFILE;
+<pre tabindex=0><code>CREATE INDEX table05_index ON TABLE table05 (column6) AS 'COMPACT' STORED AS RCFILE;
 
 </code></pre><p>Create index stored as text file:</p>
-<pre tabindex=0><code>CREATE INDEX table06\_index ON TABLE table06 (column7) AS 'COMPACT' ROW FORMAT DELIMITED FIELDS TERMINATED BY '\t' STORED AS TEXTFILE;
+<pre tabindex=0><code>CREATE INDEX table06_index ON TABLE table06 (column7) AS 'COMPACT' ROW FORMAT DELIMITED FIELDS TERMINATED BY '\t' STORED AS TEXTFILE;
 
 </code></pre><p>Create index with index properties:</p>
-<pre tabindex=0><code>CREATE INDEX table07\_index ON TABLE table07 (column8) AS 'COMPACT' IDXPROPERTIES (&quot;prop1&quot;=&quot;value1&quot;, &quot;prop2&quot;=&quot;value2&quot;);
+<pre tabindex=0><code>CREATE INDEX table07_index ON TABLE table07 (column8) AS 'COMPACT' IDXPROPERTIES (&quot;prop1&quot;=&quot;value1&quot;, &quot;prop2&quot;=&quot;value2&quot;);
 
 </code></pre><p>Create index with table properties:</p>
-<pre tabindex=0><code>CREATE INDEX table08\_index ON TABLE table08 (column9) AS 'COMPACT' TBLPROPERTIES (&quot;prop3&quot;=&quot;value3&quot;, &quot;prop4&quot;=&quot;value4&quot;);
+<pre tabindex=0><code>CREATE INDEX table08_index ON TABLE table08 (column9) AS 'COMPACT' TBLPROPERTIES (&quot;prop3&quot;=&quot;value3&quot;, &quot;prop4&quot;=&quot;value4&quot;);
 
 </code></pre><p>Drop index if exists:</p>
-<pre tabindex=0><code>DROP INDEX IF EXISTS table09\_index ON table09;
+<pre tabindex=0><code>DROP INDEX IF EXISTS table09_index ON table09;
 
 </code></pre><p>Rebuild index on a partition:</p>
-<pre tabindex=0><code>ALTER INDEX table10\_index ON table10 PARTITION (columnX='valueQ', columnY='valueR') REBUILD;
+<pre tabindex=0><code>ALTER INDEX table10_index ON table10 PARTITION (columnX='valueQ', columnY='valueR') REBUILD;
 </code></pre>
 </div>
 </div>
diff --git a/docs/latest/languagemanual-joinoptimization_33293167/index.html b/docs/latest/languagemanual-joinoptimization_33293167/index.html
index dae1c31..0216578 100644
--- a/docs/latest/languagemanual-joinoptimization_33293167/index.html
+++ b/docs/latest/languagemanual-joinoptimization_33293167/index.html
@@ -183,25 +183,25 @@ ASF
 <p>The <a href=http://www.tpc.org/tpcds/>TPC DS</a> is an example of such a schema. It models a typical retail warehouse where the events are sales and typical dimensions are date of sale, time of sale, or demographic of the purchasing party. Typical queries aggregate and filter fact tables along properties in the dimension tables.</p>
 <h3 id=star-schema-example>Star Schema Example</h3>
 <pre tabindex=0><code>Select count(*) cnt
-From store\_sales ss
-     join household\_demographics hd on (ss.ss\_hdemo\_sk = hd.hd\_demo\_sk)
-     join time\_dim t on (ss.ss\_sold\_time\_sk = t.t\_time\_sk)
-     join store s on (s.s\_store\_sk = ss.ss\_store\_sk)
+From store_sales ss
+     join household_demographics hd on (ss.ss_hdemo_sk = hd.hd_demo_sk)
+     join time_dim t on (ss.ss_sold_time_sk = t.t_time_sk)
+     join store s on (s.s_store_sk = ss.ss_store_sk)
 Where
-     t.t\_hour = 8
-     t.t\_minute &gt;= 30
-     hd.hd\_dep\_count = 2
+     t.t_hour = 8
+     t.t_minute &gt;= 30
+     hd.hd_dep_count = 2
 order by cnt;
 
 </code></pre><h3 id=prior-support-for-mapjoin>Prior Support for MAPJOIN</h3>
 <p>Hive supports MAPJOINs, which are well suited for this scenario – at least for dimensions small enough to fit in memory. Before release 0.11, a MAPJOIN could be invoked either through an optimizer hint:</p>
-<pre tabindex=0><code>select /*+ MAPJOIN(time\_dim) */ count(*) from
-store\_sales join time\_dim on (ss\_sold\_time\_sk = t\_time\_sk)
+<pre tabindex=0><code>select /*+ MAPJOIN(time_dim) */ count(*) from
+store_sales join time_dim on (ss_sold_time_sk = t_time_sk)
 
 </code></pre><p>or via auto join conversion:</p>
 <pre tabindex=0><code>set hive.auto.convert.join=true;
 select count(*) from
-store\_sales join time\_dim on (ss\_sold\_time\_sk = t\_time\_sk)
+store_sales join time_dim on (ss_sold_time_sk = t_time_sk)
 
 </code></pre><p>The default value for <a href=#hive-auto-convert-join>hive.auto.convert.join</a> was false in Hive 0.10.0.  Hive 0.11.0 changed the default to true (<a href=https://issues.apache.org/jira/browse/HIVE-3297>HIVE-3297</a>). Note that <a href=#hive-default-xml-template>hive-default.xml.template</a> incorrectly gives the default as false in Hive 0.11.0 through 0.13.1.</p>
 <p>MAPJOINs are processed by loading the smaller table into an in-memory hash map and matching keys with the larger table as they are streamed through. The prior implementation has this division of labor:</p>
@@ -243,11 +243,11 @@ store\_sales join time\_dim on (ss\_sold\_time\_sk = t\_time\_sk)
 <p>The following sections describe each of these optimizer enhancements.</p>
 <h4 id=optimize-chains-of-map-joins>Optimize Chains of Map Joins</h4>
 <p>The following query will produce two separate map-only jobs when executed:</p>
-<pre tabindex=0><code>select /*+ MAPJOIN(time\_dim, date\_dim) */ count(*) from
-store\_sales 
-join time\_dim on (ss\_sold\_time\_sk = t\_time\_sk) 
-join date\_dim on (ss\_sold\_date\_sk = d\_date\_sk)
-where t\_hour = 8 and d\_year = 2002
+<pre tabindex=0><code>select /*+ MAPJOIN(time_dim, date_dim) */ count(*) from
+store_sales 
+join time_dim on (ss_sold_time_sk = t_time_sk) 
+join date_dim on (ss_sold_date_sk = d_date_sk)
+where t_hour = 8 and d_year = 2002
 
 </code></pre><p>It is likely, though, that for small dimension tables the parts of both tables needed would fit into memory at the same time. This reduces the time needed to execute this query dramatically, as the fact table is only read once instead of reading it twice and writing it to HDFS to communicate between the jobs.</p>
 <h6 id=current-and-future-optimizations>Current and Future Optimizations</h6>
@@ -266,10 +266,10 @@ set hive.auto.convert.join.noconditionaltask.size = 10000000;
 <p>The <a href=#size-configuration>size configuration</a> enables the user to control what size table can fit in memory. This value represents the sum of the sizes of tables that can be converted to hashmaps that fit in memory. Currently, n-1 tables of the join have to fit in memory for the map-join optimization to take effect. There is no check to see if the table is a compressed one or not and what the potential size of the table can be. The effect of this assumption on the results is  [...]
 <p>For example, the previous query just becomes:</p>
 <pre tabindex=0><code>select count(*) from
-store\_sales 
-join time\_dim on (ss\_sold\_time\_sk = t\_time\_sk)
-join date\_dim on (ss\_sold\_date\_sk = d\_date\_sk)
-where t\_hour = 8 and d\_year = 2002
+store_sales 
+join time_dim on (ss_sold_time_sk = t_time_sk)
+join date_dim on (ss_sold_date_sk = d_date_sk)
+where t_hour = 8 and d_year = 2002
 
 </code></pre><p>If time_dim and date_dim fit in the size configuration provided, the respective joins are converted to map-joins. If the sum of the sizes of the tables can fit in the configured size, then the two map-joins are combined resulting in a single map-join. This reduces the number of MR-jobs required and significantly boosts the speed of execution of this query. This example can be easily extended for multi-way joins as well and will work as expected.</p>
 <p>Outer joins offer more challenges. Since a map-join operator can only stream one table, the streamed table needs to be the one from which all of the rows are required. For the left outer join, this is the table on the left side of the join; for the right outer join, the table on the right side, etc. This means that even though an inner join can be converted to a map-join, an outer join cannot be converted. An outer join can only be converted if the table(s) apart from the one that nee [...]
@@ -305,12 +305,12 @@ org.apache.hadoop.hive.ql.optimizer.TableSizeBasedBigTableSelectorForAutoSMJ
 <p>The following query results in an index out of bounds exception because emp_person let us say for example has 1 sort column while emp_pay_history has 2 sort columns.</p>
 <p><strong>Error Hive 0.11</strong></p>
 <pre tabindex=0><code>SELECT p.*, py.*
-FROM emp\_person p INNER JOIN emp\_pay\_history py
+FROM emp_person p INNER JOIN emp_pay_history py
 ON   p.empid = py.empid
 </code></pre><p>This works fine.</p>
 <p><strong>Working query Hive 0.11</strong></p>
 <pre tabindex=0><code>SELECT p.*, py.*
-FROM emp\_pay\_history py INNER JOIN emp\_person p
+FROM emp_pay_history py INNER JOIN emp_person p
 ON   p.empid = py.empid
 
 </code></pre><p> </p>
diff --git a/docs/latest/languagemanual-joins_27362039/index.html b/docs/latest/languagemanual-joins_27362039/index.html
index 97a6021..088f207 100644
--- a/docs/latest/languagemanual-joins_27362039/index.html
+++ b/docs/latest/languagemanual-joins_27362039/index.html
@@ -133,22 +133,22 @@ ASF
 </ul>
 <h2 id=join-syntax>Join Syntax</h2>
 <p>Hive supports the following syntax for joining tables:</p>
-<pre tabindex=0><code>join\_table:
-    table\_reference [INNER] JOIN table\_factor [join\_condition]
-  | table\_reference {LEFT|RIGHT|FULL} [OUTER] JOIN table\_reference join\_condition
-  | table\_reference LEFT SEMI JOIN table\_reference join\_condition
-  | table\_reference CROSS JOIN table\_reference [join\_condition] (as of Hive 0.10)
+<pre tabindex=0><code>join_table:
+    table_reference [INNER] JOIN table_factor [join_condition]
+  | table_reference {LEFT|RIGHT|FULL} [OUTER] JOIN table_reference join_condition
+  | table_reference LEFT SEMI JOIN table_reference join_condition
+  | table_reference CROSS JOIN table_reference [join_condition] (as of Hive 0.10)
 
-table\_reference:
-    table\_factor
-  | join\_table
+table_reference:
+    table_factor
+  | join_table
 
-table\_factor:
-    tbl\_name [alias]
-  | table\_subquery alias
-  | ( table\_references )
+table_factor:
+    tbl_name [alias]
+  | table_subquery alias
+  | ( table_references )
 
-join\_condition:
+join_condition:
     ON expression
 
 </code></pre><p>See <a href=#select-syntax>Select Syntax</a> for the context of this join syntax.</p>
@@ -165,9 +165,9 @@ join\_condition:
 <p>Version 2.2.0+: Complex expressions in ON clause</p>
 <p>Complex expressions in ON clause are supported, starting with Hive 2.2.0 (see <a href=https://issues.apache.org/jira/browse/HIVE-15211>HIVE-15211</a>, <a href=https://issues.apache.org/jira/browse/HIVE-15251>HIVE-15251</a>). Prior to that, Hive did not support join conditions that are not equality conditions.</p>
 <p>In particular, syntax for join conditions was restricted as follows:</p>
-<pre tabindex=0><code>join\_condition:  
-    ON equality\_expression ( AND equality\_expression )*
-</code></pre><pre tabindex=0><code>equality\_expression:  
+<pre tabindex=0><code>join_condition:  
+    ON equality_expression ( AND equality_expression )*
+</code></pre><pre tabindex=0><code>equality_expression:  
     expression = expression
 </code></pre><h2 id=examples>Examples</h2>
 <p>Some salient points to consider when writing join queries are as follows:</p>
diff --git a/docs/latest/languagemanual-lateralview_27362040/index.html b/docs/latest/languagemanual-lateralview_27362040/index.html
index cc4068a..2757e91 100644
--- a/docs/latest/languagemanual-lateralview_27362040/index.html
+++ b/docs/latest/languagemanual-lateralview_27362040/index.html
@@ -174,7 +174,7 @@ fromClause: FROM baseTable (lateralView)*
 <p>and the user would like to count the total number of times an ad appears across all pages.</p>
 <p>A lateral view with <a href=#explode-->explode()</a> can be used to convert <code>adid_list</code> into separate rows using the query:</p>
 <pre tabindex=0><code>SELECT pageid, adid
-FROM pageAds LATERAL VIEW explode(adid\_list) adTable AS adid;
+FROM pageAds LATERAL VIEW explode(adid_list) adTable AS adid;
 
 </code></pre><p>The resulting output will be</p>
 <table>
@@ -213,7 +213,7 @@ FROM pageAds LATERAL VIEW explode(adid\_list) adTable AS adid;
 </table>
 <p>Then in order to count the number of times a particular ad appears, count/group by can be used:</p>
 <pre tabindex=0><code>SELECT adid, count(1)
-FROM pageAds LATERAL VIEW explode(adid\_list) adTable AS adid
+FROM pageAds LATERAL VIEW explode(adid_list) adTable AS adid
 GROUP BY adid;
 
 </code></pre><table>
diff --git a/docs/latest/languagemanual-lzo_33298193/index.html b/docs/latest/languagemanual-lzo_33298193/index.html
index b84485a..8142bae 100644
--- a/docs/latest/languagemanual-lzo_33298193/index.html
+++ b/docs/latest/languagemanual-lzo_33298193/index.html
@@ -177,8 +177,8 @@ ASF
 </code></pre><p>This creates <code>names.txt.lzo</code> on HDFS.</p>
 <h3 id=table-definition>Table Definition</h3>
 <p>The following <code>hive -e</code> command creates an LZO-compressed external table:</p>
-<pre tabindex=0><code>hive -e &quot;CREATE EXTERNAL TABLE IF NOT EXISTS hive\_table\_name (column\_1  datatype\_1......column\_N datatype\_N)
-         PARTITIONED BY (partition\_col\_1 datatype\_1 ....col\_P  datatype\_P)
+<pre tabindex=0><code>hive -e &quot;CREATE EXTERNAL TABLE IF NOT EXISTS hive_table_name (column_1  datatype_1......column_N datatype_N)
+         PARTITIONED BY (partition_col_1 datatype_1 ....col_P  datatype_P)
          ROW FORMAT DELIMITED FIELDS TERMINATED BY '\t'
          STORED AS INPUTFORMAT  \&quot;com.hadoop.mapred.DeprecatedLzoTextInputFormat\&quot;
                    OUTPUTFORMAT \&quot;org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat\&quot;;
diff --git a/docs/latest/languagemanual-orc_31818911/index.html b/docs/latest/languagemanual-orc_31818911/index.html
index 3e3bc43..c09d908 100644
--- a/docs/latest/languagemanual-orc_31818911/index.html
+++ b/docs/latest/languagemanual-orc_31818911/index.html
@@ -241,7 +241,7 @@ ASF
 ) stored as orc tblproperties (&quot;orc.compress&quot;=&quot;NONE&quot;);
 
 </code></pre><p>Version 0.14.0+: CONCATENATE</p>
-<p><code>[ALTER TABLE table\_name [PARTITION partition\_spec] CONCATENATE](#alter-table-table\_name-[partition-partition\_spec]-concatenate)</code> can be used to merge small ORC files into a larger file, starting in <a href=https://issues.apache.org/jira/browse/HIVE-7509>Hive 0.14.0</a>. The merge happens at the stripe level, which avoids decompressing and decoding the data.</p>
+<p><code>[ALTER TABLE table_name [PARTITION partition_spec] CONCATENATE](#alter-table-table_name-[partition-partition_spec]-concatenate)</code> can be used to merge small ORC files into a larger file, starting in <a href=https://issues.apache.org/jira/browse/HIVE-7509>Hive 0.14.0</a>. The merge happens at the stripe level, which avoids decompressing and decoding the data.</p>
 <h2 id=serialization-and-compression>Serialization and Compression</h2>
 <p>The serialization of column data in an ORC file depends on whether the data type is integer or string.</p>
 <h3 id=integer-column-serialization>Integer Column Serialization</h3>
@@ -292,13 +292,13 @@ ASF
 hive --orcfiledump &lt;location-of-orc-file&gt;
  
 // Hive version 1.1.0 and later:
-hive --orcfiledump [-d] [--rowindex &lt;col\_ids&gt;] &lt;location-of-orc-file&gt;
+hive --orcfiledump [-d] [--rowindex &lt;col_ids&gt;] &lt;location-of-orc-file&gt;
  
 // Hive version 1.2.0 and later:
-hive --orcfiledump [-d] [-t] [--rowindex &lt;col\_ids&gt;] &lt;location-of-orc-file&gt;
+hive --orcfiledump [-d] [-t] [--rowindex &lt;col_ids&gt;] &lt;location-of-orc-file&gt;
  
 // Hive version 1.3.0 and later:
-hive --orcfiledump [-j] [-p] [-d] [-t] [--rowindex &lt;col\_ids&gt;] [--recover] [--skip-dump] 
+hive --orcfiledump [-j] [-p] [-d] [-t] [--rowindex &lt;col_ids&gt;] [--recover] [--skip-dump] 
     [--backup-path &lt;new-path&gt;] &lt;location-of-orc-file-or-directory&gt;
 </code></pre><p>Specifying <code>-d</code> in the command will cause it to dump the ORC file data rather than the metadata (Hive <a href=https://issues.apache.org/jira/browse/HIVE-7896>1.1.0</a> and later).</p>
 <p>Specifying <code>--rowindex</code> with a comma separated list of column ids will cause it to print <a href=#row-indexes>row indexes</a> for the specified columns, where 0 is the top level struct containing all of the columns and 1 is the first column id (Hive <a href=https://issues.apache.org/jira/browse/HIVE-7896>1.1.0</a> and later).</p>
diff --git a/docs/latest/languagemanual-sampling_27362042/index.html b/docs/latest/languagemanual-sampling_27362042/index.html
index b5de18d..6477384 100644
--- a/docs/latest/languagemanual-sampling_27362042/index.html
+++ b/docs/latest/languagemanual-sampling_27362042/index.html
@@ -126,7 +126,7 @@ ASF
 <h2 id=sampling-syntax>Sampling Syntax</h2>
 <h3 id=sampling-bucketized-table>Sampling Bucketized Table</h3>
 <pre tabindex=0><code>
-table\_sample: TABLESAMPLE (BUCKET x OUT OF y [ON colname])
+table_sample: TABLESAMPLE (BUCKET x OUT OF y [ON colname])
 
 </code></pre><p>The TABLESAMPLE clause allows the users to write queries for samples of the data instead of the whole table. The TABLESAMPLE clause can be added to any table in the FROM clause. The buckets are numbered starting from 1. <strong>colname</strong> indicates the column on which to sample each row in the table. colname can be one of the non-partition columns in the table or <strong>rand()</strong> indicating sampling on the entire row instead of an individual column. The rows  [...]
 <p>In the following example the 3rd bucket out of the 32 buckets of the table source. &rsquo;s' is the table alias.</p>
@@ -150,7 +150,7 @@ FROM source TABLESAMPLE(BUCKET 3 OUT OF 32 ON rand()) s;
 <h3 id=block-sampling>Block Sampling</h3>
 <p>Block sampling is available starting with Hive 0.8. Addressed under JIRA - <a href=https://issues.apache.org/jira/browse/HIVE-2121>https://issues.apache.org/jira/browse/HIVE-2121</a></p>
 <pre tabindex=0><code>
-block\_sample: TABLESAMPLE (n PERCENT)
+block_sample: TABLESAMPLE (n PERCENT)
 
 </code></pre><p>This will allow Hive to pick up at least n% data size (notice it doesn&rsquo;t necessarily mean number of rows) as inputs. Only CombineHiveInputFormat is supported and some special compression formats are not handled. If we fail to sample it, the input of MapReduce job will be the whole table/partition. We do it in HDFS block level so that the sampling granularity is block size. For example, if block size is 256MB, even if n% of input size is only 100MB, you get 256MB of  [...]
 <p>In the following example the input size 0.1% or more will be used for the query.</p>
@@ -164,7 +164,7 @@ set hive.sample.seednumber=&lt;INTEGER&gt;;
 
 </code></pre><p>Or user can specify total length to be read, but it has same limitation with PERCENT sampling. (As of Hive 0.10.0 - <a href=https://issues.apache.org/jira/browse/HIVE-3401>https://issues.apache.org/jira/browse/HIVE-3401</a>)</p>
 <pre tabindex=0><code>
-block\_sample: TABLESAMPLE (ByteLengthLiteral)
+block_sample: TABLESAMPLE (ByteLengthLiteral)
 
 ByteLengthLiteral : (Digit)+ ('b' | 'B' | 'k' | 'K' | 'm' | 'M' | 'g' | 'G')
 
@@ -175,7 +175,7 @@ FROM source TABLESAMPLE(100M) s;
 
 </code></pre><p>Hive also supports limiting input by row count basis, but it acts differently with above two. First, it does not need CombineHiveInputFormat which means this can be used with non-native tables. Second, the row count given by user is applied to each split. So total row count can be vary by number of input splits. (As of Hive 0.10.0 - <a href=https://issues.apache.org/jira/browse/HIVE-3401>https://issues.apache.org/jira/browse/HIVE-3401</a>)</p>
 <pre tabindex=0><code>
-block\_sample: TABLESAMPLE (n ROWS)
+block_sample: TABLESAMPLE (n ROWS)
 
 </code></pre><p>For example, the following query will take the first 10 rows from each input split.</p>
 <pre tabindex=0><code>
diff --git a/docs/latest/languagemanual-select_27362043/index.html b/docs/latest/languagemanual-select_27362043/index.html
index dd48b48..232efd0 100644
--- a/docs/latest/languagemanual-select_27362043/index.html
+++ b/docs/latest/languagemanual-select_27362043/index.html
@@ -131,13 +131,13 @@ ASF
 <p><a href=https://hive.apache.org/docs/latest/languagemanual-groupby_27362038/>GROUP BY</a>; <a href=https://hive.apache.org/docs/latest/languagemanual-sortby_27362045/>SORT/ORDER/CLUSTER/DISTRIBUTE BY</a>; <a href=https://hive.apache.org/docs/latest/languagemanual-joins_27362039/>JOIN</a> (<a href=https://hive.apache.org/docs/latest/languagemanual-joins_27362039/>Hive Joins</a>, <a href=https://hive.apache.org/docs/latest/languagemanual-joinoptimization_33293167/>Join Optimization</a>, [...]
 <h2 id=select-syntax>Select Syntax</h2>
 <pre tabindex=0><code>[WITH CommonTableExpression (, CommonTableExpression)*]    (Note: Only available starting with Hive 0.13.0)
-SELECT [ALL | DISTINCT] select\_expr, select\_expr, ...
-  FROM table\_reference
-  [WHERE where\_condition]
-  [GROUP BY col\_list]
-  [ORDER BY col\_list]
-  [CLUSTER BY col\_list
-    | [DISTRIBUTE BY col\_list] [SORT BY col\_list]
+SELECT [ALL | DISTINCT] select_expr, select_expr, ...
+  FROM table_reference
+  [WHERE where_condition]
+  [GROUP BY col_list]
+  [ORDER BY col_list]
+  [CLUSTER BY col_list
+    | [DISTRIBUTE BY col_list] [SORT BY col_list]
   ]
  [LIMIT [offset,] rows]
 
@@ -157,16 +157,16 @@ SELECT [ALL | DISTINCT] select\_expr, select\_expr, ...
 </code></pre><p>Note</p>
 <p>As of <a href=https://issues.apache.org/jira/browse/HIVE-4144>Hive 0.13.0</a>, FROM is optional (for example, <code>SELECT 1+1</code>).</p>
 <ul>
-<li>To get the current database (as of <a href=https://issues.apache.org/jira/browse/HIVE-4144>Hive 0.13.0</a>), use the <a href=#current\_database---function>current_database() function</a>:</li>
+<li>To get the current database (as of <a href=https://issues.apache.org/jira/browse/HIVE-4144>Hive 0.13.0</a>), use the <a href=#current_database---function>current_database() function</a>:</li>
 </ul>
-<pre tabindex=0><code>SELECT current\_database()
+<pre tabindex=0><code>SELECT current_database()
 </code></pre><ul>
 <li>To specify a database, either qualify the table names with database names ("<code>db_name.table_name</code>" starting in <a href=https://issues.apache.org/jira/browse/HIVE-1517>Hive 0.7</a>) or issue the <a href=#use-statement>USE statement</a> before the query statement (starting in <a href=https://issues.apache.org/jira/browse/HIVE-675>Hive 0.6</a>).</li>
 </ul>
 <p>&ldquo;<code>db_name.table_name</code>&rdquo; allows a query to access tables in different databases.</p>
 <p>USE sets the database for all subsequent HiveQL statements. Reissue it with the keyword &ldquo;<code>default</code>&rdquo; to reset to the default database.</p>
-<pre tabindex=0><code>USE database\_name;
-SELECT query\_specifications;
+<pre tabindex=0><code>USE database_name;
+SELECT query_specifications;
 USE default;
 </code></pre><h3 id=where-clause>WHERE Clause</h3>
 <p>The WHERE condition is a <a href=https://hive.apache.org/docs/latest/languagemanual-types_27838462/>boolean</a> expression. For example, the following query returns only those sales records which have an amount greater than 10 from the US region. Hive supports a number of <a href=https://hive.apache.org/docs/latest/languagemanual-udf_27362046/>operators and UDFs</a> in the WHERE clause:</p>
@@ -191,14 +191,14 @@ hive&gt; SELECT DISTINCT col1 FROM t1
 </code></pre><p>ALL and DISTINCT can also be used in a UNION clause – see <a href=#union-syntax>Union Syntax</a> for more information.</p>
 <h3 id=partition-based-queries>Partition Based Queries</h3>
 <p>In general, a SELECT query scans the entire table (other than for <a href=https://hive.apache.org/docs/latest/languagemanual-sampling_27362042/>sampling</a>). If a table created using the <a href=#partitioned-by>PARTITIONED BY</a> clause, a query can do <strong>partition pruning</strong> and scan only a fraction of the table relevant to the partitions specified by the query. Hive currently does partition pruning if the partition predicates are specified in the WHERE clause or the ON c [...]
-<pre tabindex=0><code>    SELECT page\_views.*
-    FROM page\_views
-    WHERE page\_views.date &gt;= '2008-03-01' AND page\_views.date &lt;= '2008-03-31'
+<pre tabindex=0><code>    SELECT page_views.*
+    FROM page_views
+    WHERE page_views.date &gt;= '2008-03-01' AND page_views.date &lt;= '2008-03-31'
 
 </code></pre><p>If a table page_views is joined with another table dim_users, you can specify a range of partitions in the ON clause as follows:</p>
-<pre tabindex=0><code>    SELECT page\_views.*
-    FROM page\_views JOIN dim\_users
-      ON (page\_views.user\_id = dim\_users.id AND page\_views.date &gt;= '2008-03-01' AND page\_views.date &lt;= '2008-03-31')
+<pre tabindex=0><code>    SELECT page_views.*
+    FROM page_views JOIN dim_users
+      ON (page_views.user_id = dim_users.id AND page_views.date &gt;= '2008-03-01' AND page_views.date &lt;= '2008-03-31')
 
 </code></pre><ul>
 <li>See also <a href=https://hive.apache.org/docs/latest/partition-filter-syntax_103092177/>Partition Filter Syntax</a>.</li>
@@ -221,10 +221,10 @@ hive&gt; SELECT DISTINCT col1 FROM t1
 <p>The following query returns 5 arbitrary customers</p>
 <pre tabindex=0><code>SELECT * FROM customers LIMIT 5
 </code></pre><p>The following query returns the first 5 customers to be created</p>
-<pre tabindex=0><code>SELECT * FROM customers ORDER BY create\_date LIMIT 5
+<pre tabindex=0><code>SELECT * FROM customers ORDER BY create_date LIMIT 5
 </code></pre><p> </p>
 <p>The following query returns the  3rd to the 7th customers to be created</p>
-<pre tabindex=0><code>SELECT * FROM customers ORDER BY create\_date LIMIT 2,5
+<pre tabindex=0><code>SELECT * FROM customers ORDER BY create_date LIMIT 2,5
 </code></pre><h3 id=regex-column-specification>REGEX Column Specification</h3>
 <p>A SELECT statement can take regex-based column specification in Hive releases prior to 0.13.0, or in 0.13.0 and later releases if the configuration property <code>[hive.support.quoted.identifiers](#hive-support-quoted-identifiers)</code> is set to <code>none</code>. </p>
 <ul>
diff --git a/docs/latest/languagemanual-sortby_27362045/index.html b/docs/latest/languagemanual-sortby_27362045/index.html
index b905d83..79b44bb 100644
--- a/docs/latest/languagemanual-sortby_27362045/index.html
+++ b/docs/latest/languagemanual-sortby_27362045/index.html
@@ -223,15 +223,15 @@ x4
 SELECT col1, col2 FROM t1 DISTRIBUTE BY col1 SORT BY col1 ASC, col2 DESC
 
 </code></pre><pre tabindex=0><code>  FROM (
-    FROM pv\_users
-    MAP ( pv\_users.userid, pv\_users.date )
-    USING 'map\_script'
+    FROM pv_users
+    MAP ( pv_users.userid, pv_users.date )
+    USING 'map_script'
     AS c1, c2, c3
     DISTRIBUTE BY c2
-    SORT BY c2, c1) map\_output
-  INSERT OVERWRITE TABLE pv\_users\_reduced
-    REDUCE ( map\_output.c1, map\_output.c2, map\_output.c3 )
-    USING 'reduce\_script'
+    SORT BY c2, c1) map_output
+  INSERT OVERWRITE TABLE pv_users_reduced
+    REDUCE ( map_output.c1, map_output.c2, map_output.c3 )
+    USING 'reduce_script'
     AS date, count;
 
 </code></pre><p>Note that columns are specified by name, not by position number. However in <a href=https://issues.apache.org/jira/browse/HIVE-28572>HIVE-28572</a> and later, columns can be specified by position when configured as follows:</p>
diff --git a/docs/latest/languagemanual-transform_27362047/index.html b/docs/latest/languagemanual-transform_27362047/index.html
index e9810e6..649a0a3 100644
--- a/docs/latest/languagemanual-transform_27362047/index.html
+++ b/docs/latest/languagemanual-transform_27362047/index.html
@@ -130,7 +130,7 @@ ASF
 <p>By default, columns will be transformed to <em>STRING</em> and delimited by TAB before feeding to the user script; similarly, all NULL values will be converted to the literal string <strong>\N</strong> in order to differentiate NULL values from empty strings. The standard output of the user script will be treated as TAB-separated <em>STRING</em> columns, any cell containing only <strong>\N</strong> will be re-interpreted as a NULL, and then the resulting STRING column will be cast to  [...]
 <p>In windows, use &ldquo;cmd /c your_script&rdquo; instead of just &ldquo;your_script&rdquo;</p>
 <p>Warning</p>
-<p>It is your responsibility to sanitize any STRING columns prior to transformation. If your STRING column contains tabs, an identity transformer will not give you back what you started with! To help with this, see <a href=#regexp\_replace>REGEXP_REPLACE</a> and replace the tabs with some other character on their way into the TRANSFORM() call.</p>
+<p>It is your responsibility to sanitize any STRING columns prior to transformation. If your STRING column contains tabs, an identity transformer will not give you back what you started with! To help with this, see <a href=#regexp_replace>REGEXP_REPLACE</a> and replace the tabs with some other character on their way into the TRANSFORM() call.</p>
 <p>Warning</p>
 <p>Formally, <em>MAP &mldr;</em> and <em>REDUCE &mldr;</em> are syntactic transformations of <em>SELECT TRANSFORM ( &mldr; )</em>. In other words, they serve as comments or notes to the reader of the query. BEWARE: Use of these keywords may be <strong>dangerous</strong> as (e.g.) typing &ldquo;REDUCE&rdquo; does not force a reduce phase to occur and typing &ldquo;MAP&rdquo; does not force a new map phase!</p>
 <p>Please also see <a href=https://hive.apache.org/docs/latest/languagemanual-sortby_27362045/>Sort By / Cluster By / Distribute By</a> and Larry Ogrodnek&rsquo;s <a href=http://dev.bizo.com/2009/10/hive-map-reduce-in-java.html>blog post</a>.</p>
@@ -146,9 +146,9 @@ rowFormat
                [ESCAPED BY char]
                [LINES SEPARATED BY char]
      | 
-     SERDE serde\_name [WITH SERDEPROPERTIES 
-                            property\_name=property\_value, 
-                            property\_name=property\_value, ...])
+     SERDE serde_name [WITH SERDEPROPERTIES 
+                            property_name=property_value, 
+                            property_name=property_value, ...])
 
 outRowFormat : rowFormat
 inRowFormat : rowFormat
@@ -159,14 +159,14 @@ query:
     FROM src
     MAP expression (',' expression)*
     (inRowFormat)?
-    USING 'my\_map\_script'
+    USING 'my_map_script'
     ( AS colName (',' colName)* )?
     (outRowFormat)? (outRecordReader)?
-    ( clusterBy? | distributeBy? sortBy? ) src\_alias
+    ( clusterBy? | distributeBy? sortBy? ) src_alias
   )
   REDUCE expression (',' expression)*
     (inRowFormat)?
-    USING 'my\_reduce\_script'
+    USING 'my_reduce_script'
     ( AS colName (',' colName)* )?
     (outRowFormat)? (outRecordReader)?
 
@@ -174,14 +174,14 @@ query:
     FROM src
     SELECT TRANSFORM '(' expression (',' expression)* ')'
     (inRowFormat)?
-    USING 'my\_map\_script'
+    USING 'my_map_script'
     ( AS colName (',' colName)* )?
     (outRowFormat)? (outRecordReader)?
-    ( clusterBy? | distributeBy? sortBy? ) src\_alias
+    ( clusterBy? | distributeBy? sortBy? ) src_alias
   )
   SELECT TRANSFORM '(' expression (',' expression)* ')'
     (inRowFormat)? 
-    USING 'my\_reduce\_script'
+    USING 'my_reduce_script'
     ( AS colName (',' colName)* )?
     (outRowFormat)? (outRecordReader)?
 
@@ -190,24 +190,24 @@ query:
 <h4 id=transform-examples>TRANSFORM Examples</h4>
 <p>Example #1:</p>
 <pre tabindex=0><code>  FROM (
-    FROM pv\_users
-    MAP pv\_users.userid, pv\_users.date
-    USING 'map\_script'
+    FROM pv_users
+    MAP pv_users.userid, pv_users.date
+    USING 'map_script'
     AS dt, uid
-    CLUSTER BY dt) map\_output
-  INSERT OVERWRITE TABLE pv\_users\_reduced
-    REDUCE map\_output.dt, map\_output.uid
-    USING 'reduce\_script'
+    CLUSTER BY dt) map_output
+  INSERT OVERWRITE TABLE pv_users_reduced
+    REDUCE map_output.dt, map_output.uid
+    USING 'reduce_script'
     AS date, count;
   FROM (
-    FROM pv\_users
-    SELECT TRANSFORM(pv\_users.userid, pv\_users.date)
-    USING 'map\_script'
+    FROM pv_users
+    SELECT TRANSFORM(pv_users.userid, pv_users.date)
+    USING 'map_script'
     AS dt, uid
-    CLUSTER BY dt) map\_output
-  INSERT OVERWRITE TABLE pv\_users\_reduced
-    SELECT TRANSFORM(map\_output.dt, map\_output.uid)
-    USING 'reduce\_script'
+    CLUSTER BY dt) map_output
+  INSERT OVERWRITE TABLE pv_users_reduced
+    SELECT TRANSFORM(map_output.dt, map_output.uid)
+    USING 'reduce_script'
     AS date, count;
 
 </code></pre><p>Example #2</p>
@@ -224,13 +224,13 @@ query:
 <p>If there is no <em>AS</em> clause after <em>USING my_script</em>, Hive assumes that the output of the script contains 2 parts: key which is before the first tab, and value which is the rest after the first tab. Note that this is different from specifying <em>AS key, value</em> because in that case, value will only contain the portion between the first tab and the second tab if there are multiple tabs.</p>
 <p>Note that we can directly do <em>CLUSTER BY key</em> without specifying the output schema of the scripts.</p>
 <pre tabindex=0><code>  FROM (
-    FROM pv\_users
-    MAP pv\_users.userid, pv\_users.date
-    USING 'map\_script'
-    CLUSTER BY key) map\_output
-  INSERT OVERWRITE TABLE pv\_users\_reduced
-    REDUCE map\_output.key, map\_output.value
-    USING 'reduce\_script'
+    FROM pv_users
+    MAP pv_users.userid, pv_users.date
+    USING 'map_script'
+    CLUSTER BY key) map_output
+  INSERT OVERWRITE TABLE pv_users_reduced
+    REDUCE map_output.key, map_output.value
+    USING 'reduce_script'
     AS date, count;
 
 </code></pre><h2 id=typing-the-output-of-transform>Typing the output of TRANSFORM</h2>
diff --git a/docs/latest/languagemanual-types_27838462/index.html b/docs/latest/languagemanual-types_27838462/index.html
index 5a65697..a76c36a 100644
--- a/docs/latest/languagemanual-types_27838462/index.html
+++ b/docs/latest/languagemanual-types_27838462/index.html
@@ -401,7 +401,7 @@ All existing datetime <a href=#udfs>UDFs</a> (month, day, year, hour, etc.) wor
 </code></pre><p>For usage, see <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=82706456#LanguageManualTypes-FloatingPointTypes">LanguageManual Types#Floating Point Types</a> in the Literals section below.</p>
 <h4 id=decimal-literals>Decimal Literals</h4>
 <p>Integral literals larger than BIGINT must be handled with Decimal(38,0). The Postfix BD is required. Example:</p>
-<pre tabindex=0><code>select CAST(18446744073709001000BD AS DECIMAL(38,0)) from my\_table limit 1;
+<pre tabindex=0><code>select CAST(18446744073709001000BD AS DECIMAL(38,0)) from my_table limit 1;
 </code></pre><h4 id=decimal-type-incompatibilities-between-hive-0120-and-0130>Decimal Type Incompatibilities between Hive 0.12.0 and 0.13.0</h4>
 <p>With the changes in the Decimal data type in Hive 0.13.0, the pre-Hive 0.13.0 columns (of type &ldquo;decimal&rdquo;) will be treated as being of type decimal(10,0).  What this means is that existing data being read from these tables will be treated as 10-digit integer values, and data being written to these tables will be converted to 10-digit integer values before being written. To avoid these issues, Hive users on 0.12 or earlier with tables containing Decimal columns will be requi [...]
 <h5 id=upgrading-pre-hive-0130-decimal-columns>Upgrading Pre-Hive 0.13.0 Decimal Columns</h5>
@@ -410,7 +410,7 @@ All existing datetime <a href=#udfs>UDFs</a> (month, day, year, hour, etc.) wor
 <li>Determine what precision/scale you would like to set for the decimal column in the table.</li>
 <li>For each decimal column in the table, update the column definition to the desired precision/scale using the <a href=#alter-table>ALTER TABLE</a> command:</li>
 </ol>
-<pre tabindex=0><code>ALTER TABLE foo CHANGE COLUMN dec\_column\_name dec\_column\_name DECIMAL(38,18);
+<pre tabindex=0><code>ALTER TABLE foo CHANGE COLUMN dec_column_name dec_column_name DECIMAL(38,18);
 </code></pre><p>If the table is not a partitioned table, then you are done.  If the table has partitions, then go on to step 3.
 3. If the table is a partitioned table, then find the list of partitions for the table:</p>
 <pre tabindex=0><code>SHOW PARTITIONS foo;
@@ -426,18 +426,18 @@ ds=2008-04-08/hr=12
  
 -- hive.exec.dynamic.partition needs to be set to true to enable dynamic partitioning with ALTER PARTITION
 -- This will alter all existing partitions of the table - be sure you know what you are doing!
-ALTER TABLE foo PARTITION (ds, hr) CHANGE COLUMN dec\_column\_name dec\_column\_name DECIMAL(38,18);
+ALTER TABLE foo PARTITION (ds, hr) CHANGE COLUMN dec_column_name dec_column_name DECIMAL(38,18);
 </code></pre><p>Alternatively, this can be done one partition at a time using ALTER TABLE CHANGE COLUMN, by specifying one partition per statement (This is available in Hive 0.14 or later, with <a href=https://issues.apache.org/jira/browse/HIVE-7971>HIVE-7971</a>.):</p>
-<pre tabindex=0><code>ALTER TABLE foo PARTITION (ds='2008-04-08', hr=11) CHANGE COLUMN dec\_column\_name dec\_column\_name DECIMAL(38,18);
-ALTER TABLE foo PARTITION (ds='2008-04-08', hr=12) CHANGE COLUMN dec\_column\_name dec\_column\_name DECIMAL(38,18);
+<pre tabindex=0><code>ALTER TABLE foo PARTITION (ds='2008-04-08', hr=11) CHANGE COLUMN dec_column_name dec_column_name DECIMAL(38,18);
+ALTER TABLE foo PARTITION (ds='2008-04-08', hr=12) CHANGE COLUMN dec_column_name dec_column_name DECIMAL(38,18);
 ...
 </code></pre><p>The Decimal datatype is discussed further in <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=27838462#LanguageManualTypes-FloatingPointTypes">Floating Point Types</a> below.</p>
 <h3 id=union-types>Union Types</h3>
 <p>UNIONTYPE support is incomplete</p>
 <p>The UNIONTYPE datatype was introduced in Hive 0.7.0 (<a href=https://issues.apache.org/jira/browse/HIVE-537>HIVE-537</a>), but full support for this type in Hive remains incomplete. Queries that reference UNIONTYPE fields in JOIN (<a href=https://issues.apache.org/jira/browse/HIVE-2508>HIVE-2508</a>), WHERE, and GROUP BY clauses will fail, and Hive does not define syntax to extract the tag or value fields of a UNIONTYPE. This means that UNIONTYPEs are effectively pass-through-only.</p>
 <p>Union types can at any one point hold exactly one of their specified data types. You can create an instance of this type using the <code>create_union</code> UDF:</p>
-<pre tabindex=0><code>CREATE TABLE union\_test(foo UNIONTYPE&lt;int, double, array&lt;string&gt;, struct&lt;a:int,b:string&gt;&gt;);
-SELECT foo FROM union\_test;
+<pre tabindex=0><code>CREATE TABLE union_test(foo UNIONTYPE&lt;int, double, array&lt;string&gt;, struct&lt;a:int,b:string&gt;&gt;);
+SELECT foo FROM union_test;
 
 {0:1}
 {1:2.0}
@@ -450,9 +450,9 @@ SELECT foo FROM union\_test;
 
 </code></pre><p>The first part in the deserialized union is the <em>tag</em> which lets us know which part of the union is being used. In this example <code>0</code> means the first data_type from the definition which is an <code>int</code> and so on.</p>
 <p>To create a union you have to provide this tag to the <code>create_union</code> UDF:</p>
-<pre tabindex=0><code>SELECT create\_union(0, key), create\_union(if(key&lt;100, 0, 1), 2.0, value), create\_union(1, &quot;a&quot;, struct(2, &quot;b&quot;)) FROM src LIMIT 2;
+<pre tabindex=0><code>SELECT create_union(0, key), create_union(if(key&lt;100, 0, 1), 2.0, value), create_union(1, &quot;a&quot;, struct(2, &quot;b&quot;)) FROM src LIMIT 2;
 
-{0:&quot;238&quot;}	{1:&quot;val\_238&quot;}	{1:{&quot;col1&quot;:2,&quot;col2&quot;:&quot;b&quot;}}
+{0:&quot;238&quot;}	{1:&quot;val_238&quot;}	{1:{&quot;col1&quot;:2,&quot;col2&quot;:&quot;b&quot;}}
 {0:&quot;86&quot;}	{0:2.0}	{1:{&quot;col1&quot;:2,&quot;col2&quot;:&quot;b&quot;}}
 
 </code></pre><h2 id=literals>Literals</h2>
@@ -467,17 +467,17 @@ SELECT foo FROM union\_test;
 <p>The precision of a Decimal type is limited to 38 digits in Hive. See <a href=https://issues.apache.org/jira/browse/HIVE-4271>HIVE-4271</a> and <a href=https://issues.apache.org/jira/browse/HIVE-4320>HIVE-4320</a> for comments about the reasons for choosing this limit.</p>
 <h5 id=using-decimal-types>Using Decimal Types</h5>
 <p>You can create a table in Hive that uses the Decimal type with the following syntax:</p>
-<pre tabindex=0><code>create table decimal\_1 (t decimal);
+<pre tabindex=0><code>create table decimal_1 (t decimal);
 
 </code></pre><p>The table <code>decimal_1</code> is a table having one field of type decimal which is basically a Decimal value.</p>
 <p>You can read and write values in such a table using either the LazySimpleSerDe or the LazyBinarySerDe. For example:</p>
-<pre tabindex=0><code>alter table decimal\_1 set serde 'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe';
+<pre tabindex=0><code>alter table decimal_1 set serde 'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe';
 
 </code></pre><p>or:</p>
-<pre tabindex=0><code>alter table decimal\_1 set serde 'org.apache.hadoop.hive.serde2.lazy.LazyBinarySerDe';
+<pre tabindex=0><code>alter table decimal_1 set serde 'org.apache.hadoop.hive.serde2.lazy.LazyBinarySerDe';
 
 </code></pre><p>You can use a cast to convert a Decimal value to any other primitive type such as a BOOLEAN. For example:</p>
-<pre tabindex=0><code>select cast(t as boolean) from decimal\_2;
+<pre tabindex=0><code>select cast(t as boolean) from decimal_2;
 
 </code></pre><h5 id=mathematical-udfs>Mathematical UDFs</h5>
 <p>Decimal also supports many <a href=#arithmetic-operators>arithmetic operators</a>, <a href=#mathematical-udfs>mathematical UDFs</a> and <a href=#udafs>UDAFs</a> with the same syntax as used in the case of DOUBLE.</p>
diff --git a/docs/latest/languagemanual-udf_27362046/index.html b/docs/latest/languagemanual-udf_27362046/index.html
index 85e2c22..df97b3c 100644
--- a/docs/latest/languagemanual-udf_27362046/index.html
+++ b/docs/latest/languagemanual-udf_27362046/index.html
@@ -180,8 +180,8 @@ ASF
 <p>All Hive keywords are case-insensitive, including the names of Hive operators and functions.</p>
 <p>In <a href=#beeline>Beeline</a> or the <a href=https://hive.apache.org/docs/latest/languagemanual-cli_27362033/>CLI</a>, use the commands below to show the latest documentation:</p>
 <pre tabindex=0><code>SHOW FUNCTIONS;
-DESCRIBE FUNCTION &lt;function\_name&gt;;
-DESCRIBE FUNCTION EXTENDED &lt;function\_name&gt;;
+DESCRIBE FUNCTION &lt;function_name&gt;;
+DESCRIBE FUNCTION EXTENDED &lt;function_name&gt;;
 
 </code></pre><p>Bug for expression caching when UDF nested in UDF or function</p>
 <p>When <a href=#hive-cache-expr-evaluation>hive.cache.expr.evaluation</a> is set to true (which is the default) a UDF can give incorrect results if it is nested in another UDF or a Hive function. This bug affects releases 0.12.0, 0.13.0, and 0.13.1. Release 0.14.0 fixed the bug (<a href=https://issues.apache.org/jira/browse/HIVE-7314>HIVE-7314</a>).</p>
@@ -1504,19 +1504,19 @@ Closed</p>
   {&quot;fruit&quot;:\[{&quot;weight&quot;:8,&quot;type&quot;:&quot;apple&quot;},{&quot;weight&quot;:9,&quot;type&quot;:&quot;pear&quot;}],
    &quot;bicycle&quot;:{&quot;price&quot;:19.95,&quot;color&quot;:&quot;red&quot;}
   },
- &quot;email&quot;:&quot;amy@only\_for\_json\_udf\_test.net&quot;,
+ &quot;email&quot;:&quot;amy@only_for_json_udf_test.net&quot;,
  &quot;owner&quot;:&quot;amy&quot;
 }
 +----+
 
 </code></pre><p>The fields of the json object can be extracted using these queries:</p>
-<pre tabindex=0><code>hive&gt; SELECT get\_json\_object(src\_json.json, '$.owner') FROM src\_json;
+<pre tabindex=0><code>hive&gt; SELECT get_json_object(src_json.json, '$.owner') FROM src_json;
 amy
 
-hive&gt; SELECT get\_json\_object(src\_json.json, '$.store.fruit\[0]') FROM src\_json;
+hive&gt; SELECT get_json_object(src_json.json, '$.store.fruit\[0]') FROM src_json;
 {&quot;weight&quot;:8,&quot;type&quot;:&quot;apple&quot;}
 
-hive&gt; SELECT get\_json\_object(src\_json.json, '$.non\_exist\_key') FROM src\_json;
+hive&gt; SELECT get_json_object(src_json.json, '$.non_exist_key') FROM src_json;
 NULL
 
 </code></pre><h2 id=built-in-aggregate-functions-udaf>Built-in Aggregate Functions (UDAF)</h2>
@@ -1890,31 +1890,31 @@ select tf.* from (select 0) t lateral view stack(2,'A',10,date '2015-01-01','B',
 <h3 id=json_tuple>json_tuple</h3>
 <p>A new json_tuple() UDTF is introduced in Hive 0.7. It takes a set of names (keys) and a JSON string, and returns a tuple of values using one function. This is much more efficient than calling GET_JSON_OBJECT to retrieve more than one key from a single JSON string. In any case where a single JSON string would be parsed more than once, your query will be more efficient if you parse it once, which is what JSON_TUPLE is for. As JSON_TUPLE is a UDTF, you will need to use the <a href=https: [...]
 <p>For example,</p>
-<pre tabindex=0><code>select a.timestamp, get\_json\_object(a.appevents, '$.eventid'), get\_json\_object(a.appenvets, '$.eventname') from log a;
+<pre tabindex=0><code>select a.timestamp, get_json_object(a.appevents, '$.eventid'), get_json_object(a.appenvets, '$.eventname') from log a;
 
 </code></pre><p>should be changed to:</p>
 <pre tabindex=0><code>select a.timestamp, b.*
-from log a lateral view json\_tuple(a.appevent, 'eventid', 'eventname') b as f1, f2;
+from log a lateral view json_tuple(a.appevent, 'eventid', 'eventname') b as f1, f2;
 
 </code></pre><h3 id=parse_url_tuple>parse_url_tuple</h3>
 <p>The parse_url_tuple() UDTF is similar to parse_url(), but can extract multiple parts of a given URL, returning the data in a tuple. Values for a particular key in QUERY can be extracted by appending a colon and the key to the partToExtract argument, for example, parse_url_tuple(&lsquo;<a href="http://facebook.com/path1/p.php?k1=v1&k2=v2#Ref1'">http://facebook.com/path1/p.php?k1=v1&k2=v2#Ref1'</a>, &lsquo;QUERY:k1&rsquo;, &lsquo;QUERY:k2&rsquo;) returns a tuple with values of &lsquo;v1 [...]
 <pre tabindex=0><code>SELECT b.*
-FROM src LATERAL VIEW parse\_url\_tuple(fullurl, 'HOST', 'PATH', 'QUERY', 'QUERY:id') b as host, path, query, query\_id LIMIT 1;
+FROM src LATERAL VIEW parse_url_tuple(fullurl, 'HOST', 'PATH', 'QUERY', 'QUERY:id') b as host, path, query, query_id LIMIT 1;
 
 </code></pre><h2 id=grouping-and-sorting-on-fcolumn>GROUPing and SORTing on f(column)</h2>
 <p>A typical OLAP pattern is that you have a timestamp column and you want to group by daily or other less granular date windows than by second. So you might want to select concat(year(dt),month(dt)) and then group on that concat(). But if you attempt to GROUP BY or SORT BY a column on which you&rsquo;ve applied a function and alias, like this:</p>
-<pre tabindex=0><code>select f(col) as fc, count(*) from table\_name group by fc;
+<pre tabindex=0><code>select f(col) as fc, count(*) from table_name group by fc;
 
 </code></pre><p>you will get an error:</p>
 <pre tabindex=0><code>FAILED: Error in semantic analysis: line 1:69 Invalid Table Alias or Column Reference fc
 
 </code></pre><p>because you are not able to GROUP BY or SORT BY a column alias on which a function has been applied. There are two workarounds. First, you can reformulate this query with subqueries, which is somewhat complicated:</p>
 <pre tabindex=0><code>select sq.fc,col1,col2,...,colN,count(*) from
-  (select f(col) as fc,col1,col2,...,colN from table\_name) sq
+  (select f(col) as fc,col1,col2,...,colN from table_name) sq
  group by sq.fc,col1,col2,...,colN;
 
 </code></pre><p>Or you can make sure not to use a column alias, which is simpler:</p>
-<pre tabindex=0><code>select f(col) as fc, count(*) from table\_name group by f(col);
+<pre tabindex=0><code>select f(col) as fc, count(*) from table_name group by f(col);
 
 </code></pre><p>Contact Tim Ellis (tellis) at RiotGames dot com if you would like to discuss this in further detail.</p>
 <h2 id=utility-functions>Utility Functions</h2>
@@ -1944,12 +1944,12 @@ FROM src LATERAL VIEW parse\_url\_tuple(fullurl, 'HOST', 'PATH', 'QUERY', 'QUERY
 </table>
 <h2 id=udf-internals>UDF internals</h2>
 <p>The context of a UDF&rsquo;s evaluate method is one row at a time. A simple invocation of a UDF like</p>
-<pre tabindex=0><code>SELECT length(string\_col) FROM table\_name;
+<pre tabindex=0><code>SELECT length(string_col) FROM table_name;
 
 </code></pre><p>would evaluate the length of each of the string_col&rsquo;s values in the map portion of the job. The side effect of the UDF being evaluated on the map-side is that you can&rsquo;t control the order of rows which get sent to the mapper. It is the same order in which the file split sent to the mapper gets deserialized. Any reduce side operation (such as SORT BY, ORDER BY, regular JOIN, etc.) would apply to the UDFs output as if it is just another column of the table. This  [...]
 <p>If you would like to control which rows get sent to the same UDF (and possibly in what order), you will have the urge to make the UDF evaluate during the reduce phase. This is achievable by making use of <a href=https://hive.apache.org/docs/latest/languagemanual-sortby_27362045/>DISTRIBUTE BY, DISTRIBUTE BY + SORT BY, CLUSTER BY</a>. An example query would be:</p>
-<pre tabindex=0><code>SELECT reducer\_udf(my\_col, distribute\_col, sort\_col) FROM
-(SELECT my\_col, distribute\_col, sort\_col FROM table\_name DISTRIBUTE BY distribute\_col SORT BY distribute\_col, sort\_col) t
+<pre tabindex=0><code>SELECT reducer_udf(my_col, distribute_col, sort_col) FROM
+(SELECT my_col, distribute_col, sort_col FROM table_name DISTRIBUTE BY distribute_col SORT BY distribute_col, sort_col) t
 
 </code></pre><p>However, one could argue that the very premise of your requirement to control the set of rows sent to the same UDF is to do aggregation in that UDF. In such a case, using a User Defined Aggregate Function (UDAF) is a better choice. You can read more about writing a UDAF <a href=https://hive.apache.org/docs/latest/genericudafcasestudy_27362093/>here</a>. Alternatively, you can user a custom reduce script to accomplish the same using <a href=https://hive.apache.org/docs/lat [...]
 <h2 id=creating-custom-udfs>Creating Custom UDFs</h2>
diff --git a/docs/latest/languagemanual-union_27362049/index.html b/docs/latest/languagemanual-union_27362049/index.html
index a94d6b6..dbe47b0 100644
--- a/docs/latest/languagemanual-union_27362049/index.html
+++ b/docs/latest/languagemanual-union_27362049/index.html
@@ -128,7 +128,7 @@ ASF
 </li>
 </ul>
 <h2 id=union-syntax>Union Syntax</h2>
-<pre tabindex=0><code>select\_statement UNION [ALL | DISTINCT] select\_statement UNION [ALL | DISTINCT] select\_statement ...
+<pre tabindex=0><code>select_statement UNION [ALL | DISTINCT] select_statement UNION [ALL | DISTINCT] select_statement ...
 
 </code></pre><p>UNION is used to combine the result from multiple SELECT statements into a single result set.</p>
 <ul>
@@ -141,20 +141,20 @@ ASF
 <p>If some additional processing has to be done on the result of the UNION, the entire statement expression can be embedded in a FROM clause like below:</p>
 <pre tabindex=0><code>SELECT *
 FROM (
-  select\_statement
+  select_statement
   UNION ALL
-  select\_statement
+  select_statement
 ) unionResult
 
 </code></pre><p>For example, if we suppose there are two different tables that track which user has published a video and which user has published a comment, the following query joins the results of a UNION ALL with the user table to create a single annotated stream for all the video publishing and comment publishing events:</p>
 <pre tabindex=0><code>    SELECT u.id, actions.date
     FROM (
         SELECT av.uid AS uid 
-        FROM action\_video av 
+        FROM action_video av 
         WHERE av.date = '2008-06-03' 
         UNION ALL 
         SELECT ac.uid AS uid 
-        FROM action\_comment ac 
+        FROM action_comment ac 
         WHERE ac.date = '2008-06-03' 
      ) actions JOIN users u ON (u.id = actions.uid) 
 
@@ -172,20 +172,20 @@ SELECT key FROM src1 
 ORDER BY key LIMIT 10
 </code></pre><h4 id=column-aliases-for-schema-matching>Column Aliases for Schema Matching</h4>
 <p>UNION expects the same schema on both sides of the expression list. As a result, the following query may fail with an error message such as &ldquo;FAILED: SemanticException 4:47 Schema of both sides of union should match.&rdquo;</p>
-<pre tabindex=0><code>INSERT OVERWRITE TABLE target\_table
-  SELECT name, id, category FROM source\_table\_1
+<pre tabindex=0><code>INSERT OVERWRITE TABLE target_table
+  SELECT name, id, category FROM source_table_1
   UNION ALL
-  SELECT name, id, &quot;Category159&quot; FROM source\_table\_2
+  SELECT name, id, &quot;Category159&quot; FROM source_table_2
 </code></pre><p>In such cases, column aliases can be used to force equal schemas:</p>
-<pre tabindex=0><code>INSERT OVERWRITE TABLE target\_table
-  SELECT name, id, category FROM source\_table\_1
+<pre tabindex=0><code>INSERT OVERWRITE TABLE target_table
+  SELECT name, id, category FROM source_table_1
   UNION ALL
-  SELECT name, id, &quot;Category159&quot; as category FROM source\_table\_2
+  SELECT name, id, &quot;Category159&quot; as category FROM source_table_2
 </code></pre><h4 id=column-type-conversion>Column Type Conversion</h4>
 <p>Before <a href=https://issues.apache.org/jira/browse/HIVE-14251>HIVE-14251</a> in release 2.2.0, Hive tries to perform implicit conversion across Hive type groups. With the change of <a href=https://issues.apache.org/jira/browse/HIVE-14251>HIVE-14251</a>, Hive will only perform implicit conversion within each type group including string group, number group or date group, not across groups. In order to union the types from different groups such as a string type and a date type, an expl [...]
-<pre tabindex=0><code>  SELECT name, id, cast('2001-01-01' as date) d FROM source\_table\_1
+<pre tabindex=0><code>  SELECT name, id, cast('2001-01-01' as date) d FROM source_table_1
   UNION ALL
-  SELECT name, id, hiredate as d FROM source\_table\_2
+  SELECT name, id, hiredate as d FROM source_table_2
 </code></pre><p> </p>
 <h4 id=version-information>Version Information</h4>
 <p>Version information</p>
diff --git a/docs/latest/languagemanual-variablesubstitution_30754722/index.html b/docs/latest/languagemanual-variablesubstitution_30754722/index.html
index 6ac64d8..a40711d 100644
--- a/docs/latest/languagemanual-variablesubstitution_30754722/index.html
+++ b/docs/latest/languagemanual-variablesubstitution_30754722/index.html
@@ -137,7 +137,7 @@ $ hive -e &quot; describe $a &quot;
 create table if not exists b (col int); describe ${hiveconf:a}'
 
 </code></pre><p>results in:</p>
-<pre tabindex=0><code>Hive history file=/tmp/edward/hive\_job\_log\_edward\_201011240906\_1463048967.txt
+<pre tabindex=0><code>Hive history file=/tmp/edward/hive_job_log_edward_201011240906_1463048967.txt
 a=b
 hiveconf:a=b
 OK
diff --git a/docs/latest/languagemanual-windowingandanalytics_31819589/index.html b/docs/latest/languagemanual-windowingandanalytics_31819589/index.html
index 37a5219..2fce6ae 100644
--- a/docs/latest/languagemanual-windowingandanalytics_31819589/index.html
+++ b/docs/latest/languagemanual-windowingandanalytics_31819589/index.html
@@ -262,8 +262,8 @@ FROM T;
 <p>Aliases can be used as well, with or without the keyword AS:</p>
 <pre tabindex=0><code>SELECT 
  a,
- COUNT(b) OVER (PARTITION BY c) AS b\_count,
- SUM(b) OVER (PARTITION BY c) b\_sum
+ COUNT(b) OVER (PARTITION BY c) AS b_count,
+ SUM(b) OVER (PARTITION BY c) b_sum
 FROM T;
 </code></pre><h4 id=window-clause>WINDOW clause</h4>
 <pre tabindex=0><code>SELECT a, SUM(b) OVER w
diff --git a/docs/latest/languagemanual-xpathudf_27362051/index.html b/docs/latest/languagemanual-xpathudf_27362051/index.html
index 857d713..4a6a881 100644
--- a/docs/latest/languagemanual-xpathudf_27362051/index.html
+++ b/docs/latest/languagemanual-xpathudf_27362051/index.html
@@ -170,53 +170,53 @@ ASF
 <p>The <code>xpath_string()</code> function returns the text of the first matching node.</p>
 <p>Get the text for node &lsquo;a/b&rsquo;:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_string ('&lt;a&gt;&lt;b&gt;bb&lt;/b&gt;&lt;c&gt;cc&lt;/c&gt;&lt;/a&gt;', 'a/b') FROM src LIMIT 1 ;
+&gt; SELECT xpath_string ('&lt;a&gt;&lt;b&gt;bb&lt;/b&gt;&lt;c&gt;cc&lt;/c&gt;&lt;/a&gt;', 'a/b') FROM src LIMIT 1 ;
 bb
 
 </code></pre><p>Get the text for node &lsquo;a&rsquo;. Because &lsquo;a&rsquo; has children nodes with text, the result is a composite of text from the children.</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_string ('&lt;a&gt;&lt;b&gt;bb&lt;/b&gt;&lt;c&gt;cc&lt;/c&gt;&lt;/a&gt;', 'a') FROM src LIMIT 1 ;
+&gt; SELECT xpath_string ('&lt;a&gt;&lt;b&gt;bb&lt;/b&gt;&lt;c&gt;cc&lt;/c&gt;&lt;/a&gt;', 'a') FROM src LIMIT 1 ;
 bbcc
 
 </code></pre><p>Non-matching expression returns an empty string:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_string ('&lt;a&gt;&lt;b&gt;bb&lt;/b&gt;&lt;c&gt;cc&lt;/c&gt;&lt;/a&gt;', 'a/d') FROM src LIMIT 1 ;
+&gt; SELECT xpath_string ('&lt;a&gt;&lt;b&gt;bb&lt;/b&gt;&lt;c&gt;cc&lt;/c&gt;&lt;/a&gt;', 'a/d') FROM src LIMIT 1 ;
 
 </code></pre><p>Gets the text of the first node that matches &lsquo;//b&rsquo;:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_string ('&lt;a&gt;&lt;b&gt;b1&lt;/b&gt;&lt;b&gt;b2&lt;/b&gt;&lt;/a&gt;', '//b') FROM src LIMIT 1 ;
+&gt; SELECT xpath_string ('&lt;a&gt;&lt;b&gt;b1&lt;/b&gt;&lt;b&gt;b2&lt;/b&gt;&lt;/a&gt;', '//b') FROM src LIMIT 1 ;
 b1
 
 </code></pre><p>Gets the second matching node:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_string ('&lt;a&gt;&lt;b&gt;b1&lt;/b&gt;&lt;b&gt;b2&lt;/b&gt;&lt;/a&gt;', 'a/b[2]') FROM src LIMIT 1 ;
+&gt; SELECT xpath_string ('&lt;a&gt;&lt;b&gt;b1&lt;/b&gt;&lt;b&gt;b2&lt;/b&gt;&lt;/a&gt;', 'a/b[2]') FROM src LIMIT 1 ;
 b2
 
 </code></pre><p>Gets the text from the first node that has an attribute &lsquo;id&rsquo; with value &lsquo;b_2&rsquo;:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_string ('&lt;a&gt;&lt;b&gt;b1&lt;/b&gt;&lt;b id=&quot;b\_2&quot;&gt;b2&lt;/b&gt;&lt;/a&gt;', 'a/b[@id=&quot;b\_2&quot;]') FROM src LIMIT 1 ;
+&gt; SELECT xpath_string ('&lt;a&gt;&lt;b&gt;b1&lt;/b&gt;&lt;b id=&quot;b_2&quot;&gt;b2&lt;/b&gt;&lt;/a&gt;', 'a/b[@id=&quot;b_2&quot;]') FROM src LIMIT 1 ;
 b2
 
 </code></pre><h4 id=xpath_boolean>xpath_boolean</h4>
 <p>Returns true if the XPath expression evaluates to true, or if a matching node is found.</p>
 <p>Match found:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_boolean ('&lt;a&gt;&lt;b&gt;b&lt;/b&gt;&lt;/a&gt;', 'a/b') FROM src LIMIT 1 ;
+&gt; SELECT xpath_boolean ('&lt;a&gt;&lt;b&gt;b&lt;/b&gt;&lt;/a&gt;', 'a/b') FROM src LIMIT 1 ;
 true
 
 </code></pre><p>No match found:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_boolean ('&lt;a&gt;&lt;b&gt;b&lt;/b&gt;&lt;/a&gt;', 'a/c') FROM src LIMIT 1 ;
+&gt; SELECT xpath_boolean ('&lt;a&gt;&lt;b&gt;b&lt;/b&gt;&lt;/a&gt;', 'a/c') FROM src LIMIT 1 ;
 false
 
 </code></pre><p>Match found:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_boolean ('&lt;a&gt;&lt;b&gt;b&lt;/b&gt;&lt;/a&gt;', 'a/b = &quot;b&quot;') FROM src LIMIT 1 ;
+&gt; SELECT xpath_boolean ('&lt;a&gt;&lt;b&gt;b&lt;/b&gt;&lt;/a&gt;', 'a/b = &quot;b&quot;') FROM src LIMIT 1 ;
 true
 
 </code></pre><p>No match found:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_boolean ('&lt;a&gt;&lt;b&gt;10&lt;/b&gt;&lt;/a&gt;', 'a/b &lt; 10') FROM src LIMIT 1 ;
+&gt; SELECT xpath_boolean ('&lt;a&gt;&lt;b&gt;10&lt;/b&gt;&lt;/a&gt;', 'a/b &lt; 10') FROM src LIMIT 1 ;
 false
 
 </code></pre><h4 id=xpath_short-xpath_int-xpath_long>xpath_short, xpath_int, xpath_long</h4>
@@ -224,28 +224,28 @@ false
 <p>Mathematical operations are supported. In cases where the value overflows the return type, then the maximum value for the type is returned.</p>
 <p>No match:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_int ('&lt;a&gt;b&lt;/a&gt;', 'a = 10') FROM src LIMIT 1 ;
+&gt; SELECT xpath_int ('&lt;a&gt;b&lt;/a&gt;', 'a = 10') FROM src LIMIT 1 ;
 0
 
 </code></pre><p>Non-numeric match:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_int ('&lt;a&gt;this is not a number&lt;/a&gt;', 'a') FROM src LIMIT 1 ;
+&gt; SELECT xpath_int ('&lt;a&gt;this is not a number&lt;/a&gt;', 'a') FROM src LIMIT 1 ;
 0
-&gt; SELECT xpath\_int ('&lt;a&gt;this 2 is not a number&lt;/a&gt;', 'a') FROM src LIMIT 1 ;
+&gt; SELECT xpath_int ('&lt;a&gt;this 2 is not a number&lt;/a&gt;', 'a') FROM src LIMIT 1 ;
 0
 
 </code></pre><p>Adding values:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_int ('&lt;a&gt;&lt;b class=&quot;odd&quot;&gt;1&lt;/b&gt;&lt;b class=&quot;even&quot;&gt;2&lt;/b&gt;&lt;b class=&quot;odd&quot;&gt;4&lt;/b&gt;&lt;c&gt;8&lt;/c&gt;&lt;/a&gt;', 'sum(a/*)') FROM src LIMIT 1 ;
+&gt; SELECT xpath_int ('&lt;a&gt;&lt;b class=&quot;odd&quot;&gt;1&lt;/b&gt;&lt;b class=&quot;even&quot;&gt;2&lt;/b&gt;&lt;b class=&quot;odd&quot;&gt;4&lt;/b&gt;&lt;c&gt;8&lt;/c&gt;&lt;/a&gt;', 'sum(a/*)') FROM src LIMIT 1 ;
 15
-&gt; SELECT xpath\_int ('&lt;a&gt;&lt;b class=&quot;odd&quot;&gt;1&lt;/b&gt;&lt;b class=&quot;even&quot;&gt;2&lt;/b&gt;&lt;b class=&quot;odd&quot;&gt;4&lt;/b&gt;&lt;c&gt;8&lt;/c&gt;&lt;/a&gt;', 'sum(a/b)') FROM src LIMIT 1 ;
+&gt; SELECT xpath_int ('&lt;a&gt;&lt;b class=&quot;odd&quot;&gt;1&lt;/b&gt;&lt;b class=&quot;even&quot;&gt;2&lt;/b&gt;&lt;b class=&quot;odd&quot;&gt;4&lt;/b&gt;&lt;c&gt;8&lt;/c&gt;&lt;/a&gt;', 'sum(a/b)') FROM src LIMIT 1 ;
 7
-&gt; SELECT xpath\_int ('&lt;a&gt;&lt;b class=&quot;odd&quot;&gt;1&lt;/b&gt;&lt;b class=&quot;even&quot;&gt;2&lt;/b&gt;&lt;b class=&quot;odd&quot;&gt;4&lt;/b&gt;&lt;c&gt;8&lt;/c&gt;&lt;/a&gt;', 'sum(a/b[@class=&quot;odd&quot;])') FROM src LIMIT 1 ;
+&gt; SELECT xpath_int ('&lt;a&gt;&lt;b class=&quot;odd&quot;&gt;1&lt;/b&gt;&lt;b class=&quot;even&quot;&gt;2&lt;/b&gt;&lt;b class=&quot;odd&quot;&gt;4&lt;/b&gt;&lt;c&gt;8&lt;/c&gt;&lt;/a&gt;', 'sum(a/b[@class=&quot;odd&quot;])') FROM src LIMIT 1 ;
 5
 
 </code></pre><p>Overflow:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_int ('&lt;a&gt;&lt;b&gt;2000000000&lt;/b&gt;&lt;c&gt;40000000000&lt;/c&gt;&lt;/a&gt;', 'a/b * a/c') FROM src LIMIT 1 ;
+&gt; SELECT xpath_int ('&lt;a&gt;&lt;b&gt;2000000000&lt;/b&gt;&lt;c&gt;40000000000&lt;/c&gt;&lt;/a&gt;', 'a/b * a/c') FROM src LIMIT 1 ;
 2147483647
 
 </code></pre><h4 id=xpath_float-xpath_double-xpath_number>xpath_float, xpath_double, xpath_number</h4>
@@ -253,17 +253,17 @@ false
 <p>non-numeric matches result in NaN. Note that <code>xpath_number()</code> is an alias for <code>xpath_double()</code>.</p>
 <p>No match:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_double ('&lt;a&gt;b&lt;/a&gt;', 'a = 10') FROM src LIMIT 1 ;
+&gt; SELECT xpath_double ('&lt;a&gt;b&lt;/a&gt;', 'a = 10') FROM src LIMIT 1 ;
 0.0
 
 </code></pre><p>Non-numeric match:</p>
 <pre tabindex=0><code>
-&gt; SELECT xpath\_double ('&lt;a&gt;this is not a number&lt;/a&gt;', 'a') FROM src LIMIT 1 ;
+&gt; SELECT xpath_double ('&lt;a&gt;this is not a number&lt;/a&gt;', 'a') FROM src LIMIT 1 ;
 NaN
 
 </code></pre><p>A very large number:</p>
 <pre tabindex=0><code>
-SELECT xpath\_double ('&lt;a&gt;&lt;b&gt;2000000000&lt;/b&gt;&lt;c&gt;40000000000&lt;/c&gt;&lt;/a&gt;', 'a/b * a/c') FROM src LIMIT 1 ;
+SELECT xpath_double ('&lt;a&gt;&lt;b&gt;2000000000&lt;/b&gt;&lt;c&gt;40000000000&lt;/c&gt;&lt;/a&gt;', 'a/b * a/c') FROM src LIMIT 1 ;
 8.0E19
 
 </code></pre><h1 id=udafs>UDAFs</h1>
diff --git a/docs/latest/llap_62689557/index.html b/docs/latest/llap_62689557/index.html
index f17472d..14fc1be 100644
--- a/docs/latest/llap_62689557/index.html
+++ b/docs/latest/llap_62689557/index.html
@@ -236,7 +236,7 @@ LLAP Peers - /peers </p>
 <h2 id=llap-status>LLAP Status</h2>
 <p><a href=https://issues.apache.org/jira/browse/AMBARI-16149>AMBARI-16149</a> introduces LLAP app status, available with HiveServer2.</p>
 <p>Example usage.</p>
-<pre tabindex=0><code>/current/hive-server2-hive2/bin/hive --service llapstatus --name {llap\_app\_name} [-f] [-w] [-i] [-t]
+<pre tabindex=0><code>/current/hive-server2-hive2/bin/hive --service llapstatus --name {llap_app_name} [-f] [-w] [-i] [-t]
 </code></pre><pre tabindex=0><code> -f,--findAppTimeout &lt;findAppTimeout&gt;                 Amount of time(s) that the tool will sleep to wait for the YARN application to start. negative values=wait
                                                       forever, 0=Do not wait. default=20s
  -H,--help                                            Print help information
diff --git a/docs/latest/managed-vs-external-tables_95654003/index.html b/docs/latest/managed-vs-external-tables_95654003/index.html
index 76125a4..c28d10e 100644
--- a/docs/latest/managed-vs-external-tables_95654003/index.html
+++ b/docs/latest/managed-vs-external-tables_95654003/index.html
@@ -124,7 +124,7 @@ ASF
 <p>This document lists some of the differences between the two but the fundamental difference is that Hive assumes that it <em>owns</em> the data for managed tables. That means that the data, its properties and data layout will and can only be changed via Hive command. The data still lives in a normal file system and nothing is stopping you from changing it without telling Hive about it. If you do though it violates invariants and expectations of Hive and you might see undefined behavior.</p>
 <p>Another consequence is that data is attached to the Hive entities. So, whenever you change an entity (e.g. drop a table) the data is also changed (in this case the data is deleted). This is very much like with traditional RDBMS where you would also not manage the data files on your own but use a SQL-based access to do so.</p>
 <p>For external tables Hive assumes that it does <em>not</em> manage the data.</p>
-<p>Managed or external tables can be identified using the <a href=#describe-formatted-table\_name>DESCRIBE FORMATTED table_name</a> command, which will display either MANAGED_TABLE or EXTERNAL_TABLE depending on table type.</p>
+<p>Managed or external tables can be identified using the <a href=#describe-formatted-table_name>DESCRIBE FORMATTED table_name</a> command, which will display either MANAGED_TABLE or EXTERNAL_TABLE depending on table type.</p>
 <p><a href=https://hive.apache.org/docs/latest/statsdev_27362062/>Statistics</a> can be managed on internal and external tables and partitions for query optimization. </p>
 <h2 id=feature-comparison>Feature comparison</h2>
 <p>This means that there are lots of features which are only available for one of the two table types but not the other. This is an incomplete list of things:</p>
@@ -140,7 +140,7 @@ ASF
 <p>A managed table is stored under the <a href=#hive-metastore-warehouse-dir>hive.metastore.warehouse.dir</a> path property, by default in a folder path similar to <code>/user/hive/warehouse/databasename.db/tablename/</code>. The default location can be overridden by the <code>location</code> property during table creation. If a managed table or partition is dropped, the data and metadata associated with that table or partition are deleted. If the PURGE option is not specified, the data  [...]
 <p>Use managed tables when Hive should manage the lifecycle of the table, or when generating temporary tables.</p>
 <h2 id=external-tables>External tables</h2>
-<p>An external table describes the metadata / schema on external files. External table files can be accessed and managed by processes outside of Hive. External tables can access data stored in sources such as Azure Storage Volumes (ASV) or remote HDFS locations. If the structure or partitioning of an external table is changed, an <a href=#msck-repair-table-table\_name>MSCK REPAIR TABLE table_name</a> statement can be used to refresh metadata information.</p>
+<p>An external table describes the metadata / schema on external files. External table files can be accessed and managed by processes outside of Hive. External tables can access data stored in sources such as Azure Storage Volumes (ASV) or remote HDFS locations. If the structure or partitioning of an external table is changed, an <a href=#msck-repair-table-table_name>MSCK REPAIR TABLE table_name</a> statement can be used to refresh metadata information.</p>
 <p>Use external tables when files are already present or in remote locations, and the files should remain even if the table is dropped.</p>
 </div>
 </div>
diff --git a/docs/latest/manual-installation_283118363/index.html b/docs/latest/manual-installation_283118363/index.html
index d611800..6ab1a15 100644
--- a/docs/latest/manual-installation_283118363/index.html
+++ b/docs/latest/manual-installation_283118363/index.html
@@ -168,9 +168,9 @@ brew untap adoptopenjdk/openjdk
 <pre tabindex=0><code>mvn -version
 Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
 Maven home: /Users/yourusername/programs/apache-maven-3.6.3
-Java version: 1.8.0\_292, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre
-Default locale: en\_HU, platform encoding: UTF-8
-OS name: &quot;mac os x&quot;, version: &quot;10.16&quot;, arch: &quot;x86\_64&quot;, family: &quot;mac&quot;
+Java version: 1.8.0_292, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre
+Default locale: en_HU, platform encoding: UTF-8
+OS name: &quot;mac os x&quot;, version: &quot;10.16&quot;, arch: &quot;x86_64&quot;, family: &quot;mac&quot;
 </code></pre><p>As you can see, even if it is an arm processor, maven thinks the architecture is Intel based.</p>
 <h3 id=protobuf>Protobuf</h3>
 <p>You have to download and compile protobuf. And also, install it into the local maven repository. Protobuf 2.5.0 is not ready for ARM. On this chipset, you will need to do some extra steps.</p>
@@ -180,9 +180,9 @@ cd protobuf-2.5.0
 ./configure
 </code></pre><p>On ARM, edit the src/google/protobuf/stubs/platform_macros.h and add arm to the part, processor architecture detection, after the last elif branch: <br>
  </p>
-<pre tabindex=0><code>#elif defined(\_\_arm64\_\_)
-#define GOOGLE\_PROTOBUF\_ARCH\_ARM 1
-#define GOOGLE\_PROTOBUF\_ARCH\_64\_BIT 1
+<pre tabindex=0><code>#elif defined(__arm64__)
+#define GOOGLE_PROTOBUF_ARCH_ARM 1
+#define GOOGLE_PROTOBUF_ARCH_64_BIT 1
 </code></pre><p>Now, you can compile and install protobuf:</p>
 <pre tabindex=0><code>make
 make check
@@ -192,7 +192,7 @@ sudo make install
 </code></pre><h3 id=hadoop>Hadoop</h3>
 <p>Firstly, move through the instructions on the official documentation, single-node, pseudo-distributed configuration: <a href=https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/SingleCluster.html#Pseudo-Distributed_Operation>https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/SingleCluster.html#Pseudo-Distributed_Operation</a>.</p>
 <p>After that, set up HADOOP_HOME:</p>
-<pre tabindex=0><code>export HADOOP\_HOME=/yourpathtohadoop/hadoop-3.3.6
+<pre tabindex=0><code>export HADOOP_HOME=/yourpathtohadoop/hadoop-3.3.6
 </code></pre><h3 id=tez>Tez</h3>
 <p>Tez will require some additional steps. Hadoop uses a tez tarball but it expects it in other compressed directory structure than it is released. So we will extract the tarball and compress again. And also, we will put the extracted jars into hdfs. After that we set the necessary environment variables.</p>
 <p>Download tez, extract and re-compress the tar: </p>
@@ -201,15 +201,15 @@ tar -xzvf apache-tez-0.10.3-bin.tar.gz
 cd apache-tez-0.10.3-bin
 tar zcvf ../apache-tez-0.10.3-bin.tar.gz * &amp;&amp; cd ..
 </code></pre><p>Add the necessary tez files to hdfs</p>
-<pre tabindex=0><code>$HADOOP\_HOME/sbin/start-dfs.sh	# start hdfs
-$HADOOP\_HOME/bin/hadoop fs -mkdir -p /apps/tez
-$HADOOP\_HOME/bin/hadoop fs -put apache-tez-0.10.3-bin.tar.gz /apps/tez # copy the tarball
-$HADOOP\_HOME/bin/hadoop fs -put apache-tez-0.10.3-bin /apps/tez # copy the whole folder
-$HADOOP\_HOME/bin/hadoop fs -ls /apps/tez # verify
-$HADOOP\_HOME/sbin/stop-all.sh # stop hdfs
+<pre tabindex=0><code>$HADOOP_HOME/sbin/start-dfs.sh	# start hdfs
+$HADOOP_HOME/bin/hadoop fs -mkdir -p /apps/tez
+$HADOOP_HOME/bin/hadoop fs -put apache-tez-0.10.3-bin.tar.gz /apps/tez # copy the tarball
+$HADOOP_HOME/bin/hadoop fs -put apache-tez-0.10.3-bin /apps/tez # copy the whole folder
+$HADOOP_HOME/bin/hadoop fs -ls /apps/tez # verify
+$HADOOP_HOME/sbin/stop-all.sh # stop hdfs
 </code></pre><p>Set up TEZ_HOME and HADOOP_CLASSPATH environment variables</p>
-<pre tabindex=0><code>export TEZ\_HOME=/yourpathtotez/apache-tez-0.10.3-bin
-export HADOOP\_CLASSPATH=$TEZ\_HOME/*:$TEZ\_HOME/conf
+<pre tabindex=0><code>export TEZ_HOME=/yourpathtotez/apache-tez-0.10.3-bin
+export HADOOP_CLASSPATH=$TEZ_HOME/*:$TEZ_HOME/conf
 </code></pre><p>Create a new config file for Tez: $TEZ_HOME/conf/tez-site.xml</p>
 <pre tabindex=0><code>&lt;configuration&gt;
     &lt;property&gt;
@@ -236,13 +236,13 @@ export HADOOP\_CLASSPATH=$TEZ\_HOME/*:$TEZ\_HOME/conf
     &lt;/property&gt;
 &lt;/configuration&gt;
 </code></pre><p>Modify $HADOOP_HOME/<strong>etc/hadoop/hadoop-env.sh</strong></p>
-<pre tabindex=0><code># JAVA\_HOME
-export JAVA\_HOME=/yourpathtojavahome/javahome
+<pre tabindex=0><code># JAVA_HOME
+export JAVA_HOME=/yourpathtojavahome/javahome
 # tez
-export TEZ\_CONF\_DIR=/yourpathtotezconf/conf
-export TEZ\_JARS=/yourpathtotez/apache-tez-0.10.3-bin
-export HADOOP\_CLASSPATH=${TEZ\_CONF\_DIR}:${TEZ\_JARS}/*:${TEZ\_JARS}/lib/*:${HADOOP\_CLASSPATH}:
-${JAVA\_JDBC\_LIBS}:${MAPREDUCE\_LIBS}
+export TEZ_CONF_DIR=/yourpathtotezconf/conf
+export TEZ_JARS=/yourpathtotez/apache-tez-0.10.3-bin
+export HADOOP_CLASSPATH=${TEZ_CONF_DIR}:${TEZ_JARS}/*:${TEZ_JARS}/lib/*:${HADOOP_CLASSPATH}:
+${JAVA_JDBC_LIBS}:${MAPREDUCE_LIBS}
 </code></pre><p>Modify $HADOOP_HOME/<strong>etc/hadoop/mapred-site.xml</strong></p>
 <pre tabindex=0><code>&lt;configuration&gt;
     &lt;property&gt;
@@ -251,7 +251,7 @@ ${JAVA\_JDBC\_LIBS}:${MAPREDUCE\_LIBS}
     &lt;/property&gt;
     &lt;property&gt;
         &lt;name&gt;mapreduce.application.classpath&lt;/name&gt;
-        &lt;value&gt;$HADOOP\_CLASSPATH:$HADOOP\_HOME/share/hadoop/mapreduce/*:$HADOOP\_MAPRED\_HOME/share/hadoop/mapreduce/lib/*&lt;/value&gt;
+        &lt;value&gt;$HADOOP_CLASSPATH:$HADOOP_HOME/share/hadoop/mapreduce/*:$HADOOP_MAPRED_HOME/share/hadoop/mapreduce/lib/*&lt;/value&gt;
     &lt;/property&gt;
 &lt;/configuration&gt;
 </code></pre><p>Modify $HADOOP_HOME/<strong>etc/hadoop/yarn-site.xml</strong></p>
@@ -259,11 +259,11 @@ ${JAVA\_JDBC\_LIBS}:${MAPREDUCE\_LIBS}
 &lt;!-- Site specific YARN configuration properties --&gt;
   &lt;property&gt;
     &lt;name&gt;yarn.nodemanager.aux-services&lt;/name&gt;
-    &lt;value&gt;mapreduce\_shuffle&lt;/value&gt;
+    &lt;value&gt;mapreduce_shuffle&lt;/value&gt;
   &lt;/property&gt;
   &lt;property&gt;
     &lt;name&gt;yarn.nodemanager.env-whitelist&lt;/name&gt;
-    &lt;value&gt;JAVA\_HOME,HADOOP\_COMMON\_HOME,HADOOP\_HDFS\_HOME,HADOOP\_CONF\_DIR,CLASSPATH\_PREPEND\_DISTCACHE,HADOOP\_YARN\_HOME,HADOOP\_HOME,PATH,LANG,TZ,HADOOP\_MAPRED\_HOME&lt;/value&gt;
+    &lt;value&gt;JAVA_HOME,HADOOP_COMMON_HOME,HADOOP_HDFS_HOME,HADOOP_CONF_DIR,CLASSPATH_PREPEND_DISTCACHE,HADOOP_YARN_HOME,HADOOP_HOME,PATH,LANG,TZ,HADOOP_MAPRED_HOME&lt;/value&gt;
   &lt;/property&gt;
     &lt;property&gt;
     &lt;name&gt;yarn.nodemanager.resource.memory-mb&lt;/name&gt;
@@ -280,9 +280,9 @@ ${JAVA\_JDBC\_LIBS}:${MAPREDUCE\_LIBS}
 &lt;/configuration&gt;
 </code></pre><p>Start hadoop</p>
 <p>If you already started hadoop before, stop it. As we configured yarn and map-reduce, we have to restart it and make sure yarn is running:</p>
-<pre tabindex=0><code>$HADOOP\_HOME/sbin/stop-all.sh
+<pre tabindex=0><code>$HADOOP_HOME/sbin/stop-all.sh
 </code></pre><p>And start hadoop:</p>
-<pre tabindex=0><code>$HADOOP\_HOME/sbin/start-all.sh
+<pre tabindex=0><code>$HADOOP_HOME/sbin/start-all.sh
 </code></pre><h2 id=installing-hive-from-a-tarball>Installing Hive from a Tarball</h2>
 <p>Start by downloading the most recent stable release of Hive from one of the Apache download mirrors (see <a href=https://hive.apache.org/downloads.html>Hive Releases</a>).</p>
 <p>Next you need to unpack the tarball. This will result in the creation of a subdirectory named <code>hive-x.y.z</code> (where <code>x.y.z</code> is the release number):</p>
@@ -290,9 +290,9 @@ ${JAVA\_JDBC\_LIBS}:${MAPREDUCE\_LIBS}
 tar -xzvf apache-hive-4.0.0-bin.tar.gz 
 </code></pre><p>Set the environment variable <code>HIVE_HOME</code> to point to the installation directory:</p>
 <pre tabindex=0><code>cd apache-hive-4.0.0-bin
-export HIVE\_HOME=/yourpathtohive/apache-hive-4.0.0-bin 
+export HIVE_HOME=/yourpathtohive/apache-hive-4.0.0-bin 
 </code></pre><p>Add <code>$HIVE_HOME/bin</code> to your <code>PATH</code>:</p>
-<pre tabindex=0><code>export PATH=$HIVE\_HOME/bin:$PATH
+<pre tabindex=0><code>export PATH=$HIVE_HOME/bin:$PATH
 </code></pre><p>Create a directory for external tables: </p>
 <pre tabindex=0><code>mkdir /yourpathtoexternaltables/warehouse
 </code></pre><p>Create a new config file for Hive: $HIVE_HOME/conf/hive-site.xml</p>
@@ -328,12 +328,12 @@ export HIVE\_HOME=/yourpathtohive/apache-hive-4.0.0-bin
     &lt;/property&gt;
 &lt;/configuration&gt;
 </code></pre><p>Initialize metastore schema. It will create a directore called metastore_db. It contains an embedded Derby database for metastore</p>
-<pre tabindex=0><code>$HIVE\_HOME/bin/schematool -dbType derby -initSchema --verbose
+<pre tabindex=0><code>$HIVE_HOME/bin/schematool -dbType derby -initSchema --verbose
 </code></pre><p>Run HiveServer2</p>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hiveserver2
+<pre tabindex=0><code>$HIVE_HOME/bin/hiveserver2
 </code></pre><p><strong>Note</strong>: you can check if it is running in Hive Server web ui: <a href=http://localhost:10002/>http://localhost:10002/</a></p>
 <p>Run beeline:</p>
-<pre tabindex=0><code>$HIVE\_HOME/bin/beeline -u 'jdbc:hive2://localhost:10000/' -n yourusername
+<pre tabindex=0><code>$HIVE_HOME/bin/beeline -u 'jdbc:hive2://localhost:10000/' -n yourusername
 </code></pre><p>As a test, create a table insert some value</p>
 <pre tabindex=0><code>create table test (message string);
 insert into test values ('Hello, from Hive!');
diff --git a/docs/latest/materialized-views_80447331/index.html b/docs/latest/materialized-views_80447331/index.html
index 6a10c5b..b7ffadb 100644
--- a/docs/latest/materialized-views_80447331/index.html
+++ b/docs/latest/materialized-views_80447331/index.html
@@ -150,18 +150,18 @@ ASF
 <p>In this section, we present the main operations that are currently present in Hive for materialized views management.</p>
 <h3 id=materialized-views-creation>Materialized views creation</h3>
 <p>The syntax to create a materialized view in Hive is very similar to the <a href=https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-CreateTableAsSelect(CTAS)>CTAS statement</a> syntax, supporting common features such as partition columns, custom storage handler, or passing table properties.</p>
-<pre tabindex=0><code>CREATE MATERIALIZED VIEW [IF NOT EXISTS] [db\_name.]materialized\_view\_name
+<pre tabindex=0><code>CREATE MATERIALIZED VIEW [IF NOT EXISTS] [db_name.]materialized_view_name
   [DISABLE REWRITE]
-  [COMMENT materialized\_view\_comment]
-  [PARTITIONED ON (col\_name, ...)]
-  [CLUSTERED ON (col\_name, ...) | DISTRIBUTED ON (col\_name, ...) SORTED ON (col\_name, ...)]
+  [COMMENT materialized_view_comment]
+  [PARTITIONED ON (col_name, ...)]
+  [CLUSTERED ON (col_name, ...) | DISTRIBUTED ON (col_name, ...) SORTED ON (col_name, ...)]
   [
-    [ROW FORMAT row\_format]
-    [STORED AS file\_format]
+    [ROW FORMAT row_format]
+    [STORED AS file_format]
       | STORED BY 'storage.handler.class.name' [WITH SERDEPROPERTIES (...)]
   ]
-  [LOCATION hdfs\_path]
-  [TBLPROPERTIES (property\_name=property\_value, ...)]
+  [LOCATION hdfs_path]
+  [TBLPROPERTIES (property_name=property_value, ...)]
 AS
 &lt;query&gt;;
 </code></pre><p>When a materialized view is created, its contents will be automatically populated by the results of executing the query in the statement. The materialized view creation statement is atomic, meaning that the materialized view is not seen by other users until all query results are populated.</p>
@@ -169,25 +169,25 @@ AS
 <p>The default values for SerDe and storage format when they are not specified in the materialized view creation statement (they are optional) are specified using the configuration properties <code>hive.materializedview.serde</code> and <code>hive.materializedview.fileformat</code>, respectively.</p>
 <p>Materialized views can be stored in external systems, e.g., <a href=https://cwiki.apache.org/confluence/display/Hive/Druid+Integration>Druid</a>, using custom storage handlers. For instance, the following statement creates a materialized view that is stored in Druid:</p>
 <p><strong>Example:</strong></p>
-<pre tabindex=0><code>CREATE MATERIALIZED VIEW druid\_wiki\_mv
+<pre tabindex=0><code>CREATE MATERIALIZED VIEW druid_wiki_mv
 STORED AS 'org.apache.hadoop.hive.druid.DruidStorageHandler'
 AS
-SELECT \_\_time, page, user, c\_added, c\_removed
+SELECT __time, page, user, c_added, c_removed
 FROM src;
 </code></pre><h3 id=other-operations-for-materialized-view-management>Other operations for materialized view management</h3>
 <p>Currently we support the following operations that aid at managing the materialized views in Hive:</p>
 <pre tabindex=0><code>-- Drops a materialized view
-DROP MATERIALIZED VIEW [db\_name.]materialized\_view\_name;
+DROP MATERIALIZED VIEW [db_name.]materialized_view_name;
 -- Shows materialized views (with optional filters)
-SHOW MATERIALIZED VIEWS [IN database\_name] ['identifier\_with\_wildcards’];
+SHOW MATERIALIZED VIEWS [IN database_name] ['identifier_with_wildcards’];
 -- Shows information about a specific materialized view
-DESCRIBE [EXTENDED | FORMATTED] [db\_name.]materialized\_view\_name;
+DESCRIBE [EXTENDED | FORMATTED] [db_name.]materialized_view_name;
 
 </code></pre><p>The functionality of these operations will be extended in the future and more operations may be added.</p>
 <h2 id=materialized-view-based-query-rewriting>Materialized view-based query rewriting</h2>
 <p>Once a materialized view has been created, the optimizer will be able to exploit its definition semantics to automatically rewrite incoming queries using materialized views, and hence, accelerate query execution. </p>
 <p>The rewriting algorithm can be enabled and disabled globally using the <code>hive.materializedview.rewriting and hive.materializedview.rewriting.sql</code> configuration properties (default value is <code>true</code>). In addition, users can selectively enable/disable materialized views for rewriting. Recall that, by default, materialized views are enabled for rewriting at creation time. To alter that behavior, the following statement can be used:</p>
-<pre tabindex=0><code>ALTER MATERIALIZED VIEW [db\_name.]materialized\_view\_name ENABLE|DISABLE REWRITE;
+<pre tabindex=0><code>ALTER MATERIALIZED VIEW [db_name.]materialized_view_name ENABLE|DISABLE REWRITE;
 </code></pre><p>Hive supports two types of rewriting algorithms:</p>
 <ul>
 <li>Algebraic: this is part of Apache Calcite and it supports queries containing TableScan, Project, Filter, Join, and Aggregate operators. More information about this rewriting coverage can be found <a href=http://calcite.apache.org/docs/materialized_views#rewriting-using-plan-structural-information>here</a>. In the following, we include a few examples that briefly illustrate different rewritings.</li>
@@ -199,7 +199,7 @@ DESCRIBE [EXTENDED | FORMATTED] [db\_name.]materialized\_view\_name;
   deptno INT,
   name VARCHAR(256),
   salary FLOAT,
-  hire\_date TIMESTAMP)
+  hire_date TIMESTAMP)
 STORED AS ORC
 TBLPROPERTIES ('transactional'='true');
 
@@ -212,160 +212,160 @@ TBLPROPERTIES ('transactional'='true');
 </code></pre><p>Assume we want to obtain frequently information about employees that were hired in different period granularities after 2016 and their departments. We may create the following materialized view:</p>
 <pre tabindex=0><code>CREATE MATERIALIZED VIEW mv1
 AS
-SELECT empid, deptname, hire\_date
+SELECT empid, deptname, hire_date
 FROM emps JOIN depts
   ON (emps.deptno = depts.deptno)
-WHERE hire\_date &gt;= '2016-01-01';
+WHERE hire_date &gt;= '2016-01-01';
 </code></pre><p>Then, the following query extracting information about employees that were hired in Q1 2018 is issued to Hive:</p>
 <pre tabindex=0><code>SELECT empid, deptname
 FROM emps
 JOIN depts
   ON (emps.deptno = depts.deptno)
-WHERE hire\_date &gt;= '2018-01-01'
-    AND hire\_date &lt;= '2018-03-31';
+WHERE hire_date &gt;= '2018-01-01'
+    AND hire_date &lt;= '2018-03-31';
 </code></pre><p>Hive will be able to rewrite the incoming query using the materialized view, including a compensation predicate on top of the scan over the materialization. Though the rewriting happens at the algebraic level, to illustrate this example, we include the SQL statement equivalent to the rewriting using the <code>mv</code> used by Hive to answer the incoming query:</p>
 <pre tabindex=0><code>SELECT empid, deptname
 FROM mv1
-WHERE hire\_date &gt;= '2018-01-01'
-    AND hire\_date &lt;= '2018-03-31';
+WHERE hire_date &gt;= '2018-01-01'
+    AND hire_date &lt;= '2018-03-31';
 </code></pre><h3 id=example-2>Example 2</h3>
 <p>For the second example, consider the star schema based on the <a href=https://www.cs.umb.edu/~poneil/StarSchemaB.PDF>SSB benchmark</a> created by the following DDL statements:</p>
 <pre tabindex=0><code>CREATE TABLE `customer`(
-  `c\_custkey` BIGINT, 
-  `c\_name` STRING, 
-  `c\_address` STRING, 
-  `c\_city` STRING, 
-  `c\_nation` STRING, 
-  `c\_region` STRING, 
-  `c\_phone` STRING, 
-  `c\_mktsegment` STRING,
-  PRIMARY KEY (`c\_custkey`) DISABLE RELY)
+  `c_custkey` BIGINT, 
+  `c_name` STRING, 
+  `c_address` STRING, 
+  `c_city` STRING, 
+  `c_nation` STRING, 
+  `c_region` STRING, 
+  `c_phone` STRING, 
+  `c_mktsegment` STRING,
+  PRIMARY KEY (`c_custkey`) DISABLE RELY)
 STORED AS ORC
 TBLPROPERTIES ('transactional'='true');
 
 CREATE TABLE `dates`(
-  `d\_datekey` BIGINT, 
-  `d\_date` STRING, 
-  `d\_dayofweek` STRING, 
-  `d\_month` STRING, 
-  `d\_year` INT, 
-  `d\_yearmonthnum` INT, 
-  `d\_yearmonth` STRING, 
-  `d\_daynuminweek` INT,
-  `d\_daynuminmonth` INT,
-  `d\_daynuminyear` INT,
-  `d\_monthnuminyear` INT,
-  `d\_weeknuminyear` INT,
-  `d\_sellingseason` STRING,
-  `d\_lastdayinweekfl` INT,
-  `d\_lastdayinmonthfl` INT,
-  `d\_holidayfl` INT,
-  `d\_weekdayfl`INT,
-  PRIMARY KEY (`d\_datekey`) DISABLE RELY)
+  `d_datekey` BIGINT, 
+  `d_date` STRING, 
+  `d_dayofweek` STRING, 
+  `d_month` STRING, 
+  `d_year` INT, 
+  `d_yearmonthnum` INT, 
+  `d_yearmonth` STRING, 
+  `d_daynuminweek` INT,
+  `d_daynuminmonth` INT,
+  `d_daynuminyear` INT,
+  `d_monthnuminyear` INT,
+  `d_weeknuminyear` INT,
+  `d_sellingseason` STRING,
+  `d_lastdayinweekfl` INT,
+  `d_lastdayinmonthfl` INT,
+  `d_holidayfl` INT,
+  `d_weekdayfl`INT,
+  PRIMARY KEY (`d_datekey`) DISABLE RELY)
 STORED AS ORC
 TBLPROPERTIES ('transactional'='true');
 
 CREATE TABLE `part`(
-  `p\_partkey` BIGINT, 
-  `p\_name` STRING, 
-  `p\_mfgr` STRING, 
-  `p\_category` STRING, 
-  `p\_brand1` STRING, 
-  `p\_color` STRING, 
-  `p\_type` STRING, 
-  `p\_size` INT, 
-  `p\_container` STRING,
-  PRIMARY KEY (`p\_partkey`) DISABLE RELY)
+  `p_partkey` BIGINT, 
+  `p_name` STRING, 
+  `p_mfgr` STRING, 
+  `p_category` STRING, 
+  `p_brand1` STRING, 
+  `p_color` STRING, 
+  `p_type` STRING, 
+  `p_size` INT, 
+  `p_container` STRING,
+  PRIMARY KEY (`p_partkey`) DISABLE RELY)
 STORED AS ORC
 TBLPROPERTIES ('transactional'='true');
 
 CREATE TABLE `supplier`(
-  `s\_suppkey` BIGINT, 
-  `s\_name` STRING, 
-  `s\_address` STRING, 
-  `s\_city` STRING, 
-  `s\_nation` STRING, 
-  `s\_region` STRING, 
-  `s\_phone` STRING,
-  PRIMARY KEY (`s\_suppkey`) DISABLE RELY)
+  `s_suppkey` BIGINT, 
+  `s_name` STRING, 
+  `s_address` STRING, 
+  `s_city` STRING, 
+  `s_nation` STRING, 
+  `s_region` STRING, 
+  `s_phone` STRING,
+  PRIMARY KEY (`s_suppkey`) DISABLE RELY)
 STORED AS ORC
 TBLPROPERTIES ('transactional'='true');
 
 CREATE TABLE `lineorder`(
-  `lo\_orderkey` BIGINT, 
-  `lo\_linenumber` int, 
-  `lo\_custkey` BIGINT not null DISABLE RELY,
-  `lo\_partkey` BIGINT not null DISABLE RELY,
-  `lo\_suppkey` BIGINT not null DISABLE RELY,
-  `lo\_orderdate` BIGINT not null DISABLE RELY,
-  `lo\_ordpriority` STRING, 
-  `lo\_shippriority` STRING, 
-  `lo\_quantity` DOUBLE, 
-  `lo\_extendedprice` DOUBLE, 
-  `lo\_ordtotalprice` DOUBLE, 
-  `lo\_discount` DOUBLE, 
-  `lo\_revenue` DOUBLE, 
-  `lo\_supplycost` DOUBLE, 
-  `lo\_tax` DOUBLE, 
-  `lo\_commitdate` BIGINT, 
-  `lo\_shipmode` STRING,
-  PRIMARY KEY (`lo\_orderkey`) DISABLE RELY,
-  CONSTRAINT fk1 FOREIGN KEY (`lo\_custkey`) REFERENCES `customer\_n1`(`c\_custkey`) DISABLE RELY,
-  CONSTRAINT fk2 FOREIGN KEY (`lo\_orderdate`) REFERENCES `dates\_n0`(`d\_datekey`) DISABLE RELY,
-  CONSTRAINT fk3 FOREIGN KEY (`lo\_partkey`) REFERENCES `ssb\_part\_n0`(`p\_partkey`) DISABLE RELY,
-  CONSTRAINT fk4 FOREIGN KEY (`lo\_suppkey`) REFERENCES `supplier\_n0`(`s\_suppkey`) DISABLE RELY)
+  `lo_orderkey` BIGINT, 
+  `lo_linenumber` int, 
+  `lo_custkey` BIGINT not null DISABLE RELY,
+  `lo_partkey` BIGINT not null DISABLE RELY,
+  `lo_suppkey` BIGINT not null DISABLE RELY,
+  `lo_orderdate` BIGINT not null DISABLE RELY,
+  `lo_ordpriority` STRING, 
+  `lo_shippriority` STRING, 
+  `lo_quantity` DOUBLE, 
+  `lo_extendedprice` DOUBLE, 
+  `lo_ordtotalprice` DOUBLE, 
+  `lo_discount` DOUBLE, 
+  `lo_revenue` DOUBLE, 
+  `lo_supplycost` DOUBLE, 
+  `lo_tax` DOUBLE, 
+  `lo_commitdate` BIGINT, 
+  `lo_shipmode` STRING,
+  PRIMARY KEY (`lo_orderkey`) DISABLE RELY,
+  CONSTRAINT fk1 FOREIGN KEY (`lo_custkey`) REFERENCES `customer_n1`(`c_custkey`) DISABLE RELY,
+  CONSTRAINT fk2 FOREIGN KEY (`lo_orderdate`) REFERENCES `dates_n0`(`d_datekey`) DISABLE RELY,
+  CONSTRAINT fk3 FOREIGN KEY (`lo_partkey`) REFERENCES `ssb_part_n0`(`p_partkey`) DISABLE RELY,
+  CONSTRAINT fk4 FOREIGN KEY (`lo_suppkey`) REFERENCES `supplier_n0`(`s_suppkey`) DISABLE RELY)
 STORED AS ORC
 TBLPROPERTIES ('transactional'='true');
 </code></pre><p>As you can observe, we declare multiple integrity constraints for the database, using the <code>RELY</code> keyword so they are visible to the optimizer. Now assume we want to create a materialization that denormalizes the database contents (consider <code>dims</code> to be the set of dimensions that we will be querying often):</p>
 <pre tabindex=0><code>CREATE MATERIALIZED VIEW mv2
 AS
 SELECT &lt;dims&gt;,
-    lo\_revenue,
-    lo\_extendedprice * lo\_discount AS d\_price,
-    lo\_revenue - lo\_supplycost
+    lo_revenue,
+    lo_extendedprice * lo_discount AS d_price,
+    lo_revenue - lo_supplycost
 FROM customer, dates, lineorder, part, supplier
-WHERE lo\_orderdate = d\_datekey
-    AND lo\_partkey = p\_partkey
-    AND lo\_suppkey = s\_suppkey
-    AND lo\_custkey = c\_custkey;
+WHERE lo_orderdate = d_datekey
+    AND lo_partkey = p_partkey
+    AND lo_suppkey = s_suppkey
+    AND lo_custkey = c_custkey;
 </code></pre><p>The materialized view above may accelerate queries that execute joins among the different tables in the database. For instance, consider the following query:</p>
-<pre tabindex=0><code>SELECT SUM(lo\_extendedprice * lo\_discount)
+<pre tabindex=0><code>SELECT SUM(lo_extendedprice * lo_discount)
 FROM lineorder, dates
-WHERE lo\_orderdate = d\_datekey
-  AND d\_year = 2013
-  AND lo\_discount between 1 and 3;
+WHERE lo_orderdate = d_datekey
+  AND d_year = 2013
+  AND lo_discount between 1 and 3;
 </code></pre><p>Though the query does not use all tables present in the materialized view, it may be answered using the materialized view because the joins in <code>mv2</code> preserve all the rows in the <code>lineorder</code> table (we know this because of the integrity constraints). Hence, the materialized view-based rewriting produced by the algorithm would be the following:</p>
-<pre tabindex=0><code>SELECT SUM(d\_price)
+<pre tabindex=0><code>SELECT SUM(d_price)
 FROM mv2
-WHERE d\_year = 2013
-  AND lo\_discount between 1 and 3;
+WHERE d_year = 2013
+  AND lo_discount between 1 and 3;
 </code></pre><h3 id=example-3>Example 3</h3>
 <p>For the third example, consider the database schema with a single table that stores the edit events produced by a given website:</p>
 <pre tabindex=0><code>CREATE TABLE `wiki` (
   `time` TIMESTAMP, 
   `page` STRING, 
   `user` STRING, 
-  `characters\_added` BIGINT,
-  `characters\_removed` BIGINT)
+  `characters_added` BIGINT,
+  `characters_removed` BIGINT)
 STORED AS ORC
 TBLPROPERTIES ('transactional'='true');
 </code></pre><p>For this example, we will use Druid to store the materialized view. Assume we want to execute queries over the table, however we are not interested on any information about the events at a higher time granularity level than a minute. We may create the following materialized view that rolls up the events by the minute:</p>
 <pre tabindex=0><code>CREATE MATERIALIZED VIEW mv3
 STORED BY 'org.apache.hadoop.hive.druid.DruidStorageHandler'
 AS
-SELECT floor(time to minute) as `\_\_time`, page,
-    SUM(characters\_added) AS c\_added,
-    SUM(characters\_removed) AS c\_removed
+SELECT floor(time to minute) as `__time`, page,
+    SUM(characters_added) AS c_added,
+    SUM(characters_removed) AS c_removed
 FROM wiki
 GROUP BY floor(time to minute), page;
 </code></pre><p>Then, assume we need to answer the following query that extracts the number of characters added per month:</p>
 <pre tabindex=0><code>SELECT floor(time to month),
-    SUM(characters\_added) AS c\_added
+    SUM(characters_added) AS c_added
 FROM wiki
 GROUP BY floor(time to month);
 </code></pre><p>Hive will be able to rewrite the incoming query using <code>mv3</code> by rolling up the data of the materialized view to month granularity and projecting the information needed for the query result:</p>
 <pre tabindex=0><code>SELECT floor(time to month),
-    SUM(c\_added)
+    SUM(c_added)
 FROM mv3
 GROUP BY floor(time to month);
 </code></pre><ul>
@@ -373,7 +373,7 @@ GROUP BY floor(time to month);
 </ul>
 <h2 id=materialized-view-maintenance>Materialized view maintenance</h2>
 <p>When data in the source tables used by a materialized view changes, e.g., new data is inserted or existing data is modified, we will need to refresh the contents of the materialized view to keep it up-to-date with those changes. Currently, the rebuild operation for a materialized view needs to be triggered by the user. In particular, the user should execute the following statement:</p>
-<pre tabindex=0><code>ALTER MATERIALIZED VIEW [db\_name.]materialized\_view\_name REBUILD;
+<pre tabindex=0><code>ALTER MATERIALIZED VIEW [db_name.]materialized_view_name REBUILD;
 </code></pre><p>Hive supports incremental view maintenance, i.e., only refresh data that was affected by the changes in the original source tables. Incremental view maintenance will decrease the rebuild step execution time. In addition, it will preserve LLAP cache for existing data in the materialized view.</p>
 <p>By default, Hive will attempt to rebuild a materialized view incrementally, falling back to full rebuild if it is not possible.</p>
 <p>Current implementation only supports incremental rebuild when there were <code>INSERT</code> operations over the source tables, while <code>UPDATE</code> and <code>DELETE</code> operations will force a full rebuild of the materialized view.</p>
diff --git a/docs/latest/outerjoinbehavior_35749927/index.html b/docs/latest/outerjoinbehavior_35749927/index.html
index a9309a5..b5974f1 100644
--- a/docs/latest/outerjoinbehavior_35749927/index.html
+++ b/docs/latest/outerjoinbehavior_35749927/index.html
@@ -235,20 +235,20 @@ STAGE PLANS:
 	  condition map:
 	       Left Outer Join0 to 1
 	  condition expressions:
-	    0 {VALUE.\_col0}
-	    1 {VALUE.\_col0}
+	    0 {VALUE._col0}
+	    1 {VALUE._col0}
 	  filter predicates:
-	    0 {(VALUE.\_col0 &gt; '2')}
+	    0 {(VALUE._col0 &gt; '2')}
 	    1
 	  handleSkewJoin: false
-	  outputColumnNames: \_col0, \_col4
+	  outputColumnNames: _col0, _col4
 	  Select Operator
 	    expressions:
-		  expr: \_col0
+		  expr: _col0
 		  type: string
-		  expr: \_col4
+		  expr: _col4
 		  type: string
-	    outputColumnNames: \_col0, \_col1
+	    outputColumnNames: _col0, _col1
 	    File Output Operator
 	      compressed: false
 	      GlobalTableId: 0
@@ -297,17 +297,17 @@ STAGE PLANS:
 	  condition map:
 	       Left Outer Join0 to 1
 	  condition expressions:
-	    0 {VALUE.\_col0}
-	    1 {VALUE.\_col0}
+	    0 {VALUE._col0}
+	    1 {VALUE._col0}
 	  handleSkewJoin: false
-	  outputColumnNames: \_col0, \_col4
+	  outputColumnNames: _col0, _col4
 	  Select Operator
 	    expressions:
-		  expr: \_col0
+		  expr: _col0
 		  type: string
-		  expr: \_col4
+		  expr: _col4
 		  type: string
-	    outputColumnNames: \_col0, \_col1
+	    outputColumnNames: _col0, _col1
 	    File Output Operator
 	      compressed: false
 	      GlobalTableId: 0
@@ -357,17 +357,17 @@ STAGE PLANS:
 	  condition map:
 	       Left Outer Join0 to 1
 	  condition expressions:
-	    0 {VALUE.\_col0}
-	    1 {VALUE.\_col0}
+	    0 {VALUE._col0}
+	    1 {VALUE._col0}
 	  handleSkewJoin: false
-	  outputColumnNames: \_col0, \_col4
+	  outputColumnNames: _col0, _col4
 	  Select Operator
 	    expressions:
-		  expr: \_col0
+		  expr: _col0
 		  type: string
-		  expr: \_col4
+		  expr: _col4
 		  type: string
-	    outputColumnNames: \_col0, \_col1
+	    outputColumnNames: _col0, _col1
 	    File Output Operator
 	      compressed: false
 	      GlobalTableId: 0
@@ -413,21 +413,21 @@ STAGE PLANS:
 	  condition map:
 	       Left Outer Join0 to 1
 	  condition expressions:
-	    0 {VALUE.\_col0}
-	    1 {VALUE.\_col0}
+	    0 {VALUE._col0}
+	    1 {VALUE._col0}
 	  handleSkewJoin: false
-	  outputColumnNames: \_col0, \_col4
+	  outputColumnNames: _col0, _col4
 	  Filter Operator
 	    predicate:
-		expr: (\_col4 &gt; '2')
+		expr: (_col4 &gt; '2')
 		type: boolean
 	    Select Operator
 	      expressions:
-		    expr: \_col0
+		    expr: _col0
 		    type: string
-		    expr: \_col4
+		    expr: _col4
 		    type: string
-	      outputColumnNames: \_col0, \_col1
+	      outputColumnNames: _col0, _col1
 	      File Output Operator
 		compressed: false
 		GlobalTableId: 0
diff --git a/docs/latest/parquet_38570914/index.html b/docs/latest/parquet_38570914/index.html
index 5a1ddbe..103c4c7 100644
--- a/docs/latest/parquet_38570914/index.html
+++ b/docs/latest/parquet_38570914/index.html
@@ -174,7 +174,7 @@ ASF
 <h2 id=hiveql-syntax><strong>HiveQL Syntax</strong></h2>
 <p>A <a href=#create-table>CREATE TABLE</a> statement can specify the Parquet storage format with syntax that depends on the Hive version.</p>
 <h3 id=hive-010---012>Hive 0.10 - 0.12</h3>
-<pre tabindex=0><code>CREATE TABLE parquet\_test (
+<pre tabindex=0><code>CREATE TABLE parquet_test (
  id int,
  str string,
  mp MAP&lt;STRING,STRING&gt;,
@@ -186,7 +186,7 @@ ROW FORMAT SERDE 'parquet.hive.serde.ParquetHiveSerDe'
  INPUTFORMAT 'parquet.hive.DeprecatedParquetInputFormat'
  OUTPUTFORMAT 'parquet.hive.DeprecatedParquetOutputFormat';
 </code></pre><h3 id=hive-013-and-later>Hive 0.13 and later</h3>
-<pre tabindex=0><code>CREATE TABLE parquet\_test (
+<pre tabindex=0><code>CREATE TABLE parquet_test (
  id int,
  str string,
  mp MAP&lt;STRING,STRING&gt;,
diff --git a/docs/latest/partitionedviews_27362053/index.html b/docs/latest/partitionedviews_27362053/index.html
index 30dba91..c5c5dd0 100644
--- a/docs/latest/partitionedviews_27362053/index.html
+++ b/docs/latest/partitionedviews_27362053/index.html
@@ -141,18 +141,18 @@ ASF
 </ol>
 <h2 id=syntax>Syntax</h2>
 <pre tabindex=0><code>
-CREATE VIEW [IF NOT EXISTS] view\_name [(column\_name [COMMENT column\_comment], ...) ]
-[COMMENT table\_comment]
+CREATE VIEW [IF NOT EXISTS] view_name [(column_name [COMMENT column_comment], ...) ]
+[COMMENT table_comment]
 [PARTITIONED ON (col1, col2, ...)]
 [TBLPROPERTIES ...]
 AS SELECT ...
 
-ALTER VIEW view\_name ADD [IF NOT EXISTS] partition\_spec partition\_spec ...
+ALTER VIEW view_name ADD [IF NOT EXISTS] partition_spec partition_spec ...
 
-ALTER VIEW view\_name DROP [IF EXISTS] partition\_spec, partition\_spec, ...
+ALTER VIEW view_name DROP [IF EXISTS] partition_spec, partition_spec, ...
 
-partition\_spec:
-  : PARTITION (partition\_col = partition\_col\_value, partition\_col = partiton\_col\_value, ...)
+partition_spec:
+  : PARTITION (partition_col = partition_col_value, partition_col = partiton_col_value, ...)
 
 </code></pre><p>Notes:</p>
 <ul>
@@ -172,8 +172,8 @@ partition\_spec:
 <h1 id=hook-information>Hook Information</h1>
 <p>Although there is currently no connection between the view partition and underlying table partitions, Hive does provide dependency information as part of the hook invocation for ALTER VIEW ADD PARTITION. It does this by compiling an internal query of the form</p>
 <pre tabindex=0><code>
-SELECT * FROM view\_name
-WHERE view\_partition\_col1 = 'val1' AND view\_partition\_col=2 = 'val2' ...
+SELECT * FROM view_name
+WHERE view_partition_col1 = 'val1' AND view_partition_col=2 = 'val2' ...
 
 </code></pre><p>and then capturing the table/partition inputs for this query and passing them on to the ALTER VIEW ADD PARTITION hook results.</p>
 <p>This allows applications to track the dependencies themselves. In the future, Hive will automatically populate these dependencies into the metastore as part of <a href=https://issues.apache.org/jira/browse/HIVE-1073>HIVE-1073</a>.</p>
diff --git a/docs/latest/plugindeveloperkit_27820324/index.html b/docs/latest/plugindeveloperkit_27820324/index.html
index d3fa588..932521e 100644
--- a/docs/latest/plugindeveloperkit_27820324/index.html
+++ b/docs/latest/plugindeveloperkit_27820324/index.html
@@ -146,7 +146,7 @@ BUILD SUCCESSFUL
   &lt;property name=&quot;plugin.title&quot; value=&quot;Hive PDK Test UDF Library&quot;/&gt;
   &lt;property name=&quot;plugin.version&quot; value=&quot;0.1&quot;/&gt;
   &lt;property name=&quot;plugin.vendor&quot; value=&quot;Apache Software Foundation&quot;/&gt;
-  &lt;property name=&quot;function.sql.prefix&quot; value=&quot;tp\_&quot;/&gt;
+  &lt;property name=&quot;function.sql.prefix&quot; value=&quot;tp_&quot;/&gt;
   &lt;import file=&quot;${hive.install.dir}/scripts/pdk/build-plugin.xml&quot;/&gt;
 &lt;/project&gt;
 
@@ -187,19 +187,19 @@ import org.apache.hadoop.io.Text;
  * Example UDF for rot13 transformation.
  */
 @Description(name = &quot;rot13&quot;,
-  value = &quot;\_FUNC\_(str) - Returns str with all characters transposed via rot13&quot;,
+  value = &quot;_FUNC_(str) - Returns str with all characters transposed via rot13&quot;,
   extended = &quot;Example:\n&quot;
-  + &quot;  &gt; SELECT \_FUNC\_('Facebook') FROM src LIMIT 1;\n&quot; + &quot;  'Snprobbx'&quot;)
+  + &quot;  &gt; SELECT _FUNC_('Facebook') FROM src LIMIT 1;\n&quot; + &quot;  'Snprobbx'&quot;)
 @HivePdkUnitTests(
-    setup = &quot;create table rot13\_data(s string); &quot;
-    + &quot;insert overwrite table rot13\_data select 'Facebook' from onerow;&quot;,
-    cleanup = &quot;drop table if exists rot13\_data;&quot;,
+    setup = &quot;create table rot13_data(s string); &quot;
+    + &quot;insert overwrite table rot13_data select 'Facebook' from onerow;&quot;,
+    cleanup = &quot;drop table if exists rot13_data;&quot;,
     cases = {
       @HivePdkUnitTest(
-        query = &quot;SELECT tp\_rot13('Mixed Up!') FROM onerow;&quot;,
+        query = &quot;SELECT tp_rot13('Mixed Up!') FROM onerow;&quot;,
         result = &quot;Zvkrq Hc!&quot;),
       @HivePdkUnitTest(
-        query = &quot;SELECT tp\_rot13(s) FROM rot13\_data;&quot;,
+        query = &quot;SELECT tp_rot13(s) FROM rot13_data;&quot;,
         result = &quot;Snprobbx&quot;)
     }
   )
diff --git a/docs/latest/query-reexecution_87298873/index.html b/docs/latest/query-reexecution_87298873/index.html
index e351fa7..5b9e0cd 100644
--- a/docs/latest/query-reexecution_87298873/index.html
+++ b/docs/latest/query-reexecution_87298873/index.html
@@ -139,7 +139,7 @@ set hive.query.reexecution.strategies=overlay;
 
 create table t(a int);
 insert into t values (1);
-select assert\_true(${hiveconf:zzz} &gt; a) from t group by a;
+select assert_true(${hiveconf:zzz} &gt; a) from t group by a;
 </code></pre><p>Every hive setting which has a prefix of &ldquo;reexec.overlay&rdquo; will be set for all reexecutions.</p>
 <p>A more real life example would be to disable join auto conversion for all reexecutions:</p>
 <pre tabindex=0><code>set reexec.overlay.hive.auto.convert.join=false;
diff --git a/docs/latest/rcfilecat_30748712/index.html b/docs/latest/rcfilecat_30748712/index.html
index fd31f50..6c4597a 100644
--- a/docs/latest/rcfilecat_30748712/index.html
+++ b/docs/latest/rcfilecat_30748712/index.html
@@ -128,9 +128,9 @@ ASF
 <h2 id=data>Data</h2>
 <p>Prints out the rows stored in an RCFile, columns are tab separated and rows are newline separated.</p>
 <p>Usage:</p>
-<pre tabindex=0><code>hive --rcfilecat [--start=start\_offset] [--length=len] [--verbose] fileName
+<pre tabindex=0><code>hive --rcfilecat [--start=start_offset] [--length=len] [--verbose] fileName
 
---start=start\_offset           Start offset to begin reading in the file
+--start=start_offset           Start offset to begin reading in the file
 --length=len                   Length of data to read from the file
 --verbose                      Prints periodic stats about the data read,
                                how many records, how many bytes, scan rate
diff --git a/docs/latest/rebalance-compaction_240884502/index.html b/docs/latest/rebalance-compaction_240884502/index.html
index e3def67..347b8ad 100644
--- a/docs/latest/rebalance-compaction_240884502/index.html
+++ b/docs/latest/rebalance-compaction_240884502/index.html
@@ -121,16 +121,16 @@ ASF
 <li>Unlike other compaction types, rebalance compaction puts an <em>exclusive write lock</em> on the table.
 SQL example:</li>
 </ul>
-<pre tabindex=0><code>ALTER TABLE table\_name COMPACT 'REBALANCE';
+<pre tabindex=0><code>ALTER TABLE table_name COMPACT 'REBALANCE';
 </code></pre><h3 id=number-of-implicit-buckets>Number of implicit buckets</h3>
 <p>It is possible to set the desired number of implicit buckects during a rebalance compaction.</p>
 <p>SQL example:</p>
-<pre tabindex=0><code>ALTER TABLE table\_name COMPACT 'REBALANCE' CLUSTERED INTO n BUCKETS;
+<pre tabindex=0><code>ALTER TABLE table_name COMPACT 'REBALANCE' CLUSTERED INTO n BUCKETS;
 </code></pre><p>If the bucket number is not supplied, the number of buckets will remain the same, only the data will be redistributed among them.</p>
 <h3 id=ordering>Ordering</h3>
 <p>Optionally, an order by expression can be supplied, to be able to re-order the data during the rebalance.</p>
 <p>SQL example:</p>
-<pre tabindex=0><code>ALTER TABLE table\_name COMPACT 'REBALANCE' ORDER BY column\_name DESC;
+<pre tabindex=0><code>ALTER TABLE table_name COMPACT 'REBALANCE' ORDER BY column_name DESC;
 </code></pre><p>If the <em>order by</em> expression is not set, the ordering of the data remains the same after the compaction.</p>
 <h3 id=limitations>Limitations</h3>
 <ul>
diff --git a/docs/latest/replacing-the-implementation-of-hive-cli-using-beeline_61311909/index.html b/docs/latest/replacing-the-implementation-of-hive-cli-using-beeline_61311909/index.html
index ce00ee4..d540fac 100644
--- a/docs/latest/replacing-the-implementation-of-hive-cli-using-beeline_61311909/index.html
+++ b/docs/latest/replacing-the-implementation-of-hive-cli-using-beeline_61311909/index.html
@@ -134,7 +134,7 @@ ASF
 <p>Ideally, Hive CLI should be deprecated as the Hive community has long recommended using the Beeline plus HiveServer2 configuration; however, because of the wide use of Hive CLI, we instead are replacing Hive CLI&rsquo;s implementation with a new Hive CLI on top of Beeline plus embedded HiveServer2 (<a href=https://issues.apache.org/jira/browse/HIVE-10511>HIVE-10511</a>) so that the Hive community only needs to maintain a single code path. In this way, the new Hive CLI is just an alias [...]
 <h2 id=hive-cli-functionality-support>Hive CLI Functionality Support</h2>
 <p>We use a new Hive CLI on top of Beeline to implement the Hive CLI functionality. Since some existing Hive CLI features are not supported in the new Hive CLI, we are using the old Hive client implementation by default. Use the following command to specify the new Beeline-based Hive CLI tool:</p>
-<pre tabindex=0><code>export USE\_DEPRECATED\_CLI=false
+<pre tabindex=0><code>export USE_DEPRECATED_CLI=false
 </code></pre><p>Note that the log4j configuration file has been changed to &ldquo;beeline-log4j.properties&rdquo;. </p>
 <h3 id=hive-cli-options-support>Hive CLI Options Support</h3>
 <p>To get help, run &ldquo;<code>hive -H</code>&rdquo; or &ldquo;<code>hive --help</code>&rdquo;.</p>
@@ -156,23 +156,23 @@ ASF
 <ul>
 <li>Example of running a query from the command line</li>
 </ul>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive -e 'select a.foo from pokes a'
+<pre tabindex=0><code>$HIVE_HOME/bin/hive -e 'select a.foo from pokes a'
 </code></pre><ul>
 <li>Example of setting Hive configuration variables</li>
 </ul>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive -e 'select a.foo from pokes a' --hiveconf hive.exec.scratchdir=/opt/my/hive\_scratch --hiveconf mapred.reduce.tasks=1
+<pre tabindex=0><code>$HIVE_HOME/bin/hive -e 'select a.foo from pokes a' --hiveconf hive.exec.scratchdir=/opt/my/hive_scratch --hiveconf mapred.reduce.tasks=1
 </code></pre><ul>
 <li>Example of dumping data out from a query into a file using silent mode</li>
 </ul>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive -S -e 'select a.foo from pokes a' &gt; a.txt
+<pre tabindex=0><code>$HIVE_HOME/bin/hive -S -e 'select a.foo from pokes a' &gt; a.txt
 </code></pre><ul>
 <li>Example of running a script non-interactively from local disk</li>
 </ul>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive -f /home/my/hive-script.sql
+<pre tabindex=0><code>$HIVE_HOME/bin/hive -f /home/my/hive-script.sql
 </code></pre><ul>
 <li>Example of running a script non-interactively from a Hadoop supported filesystem (starting in <a href=https://issues.apache.org/jira/browse/HIVE-7136>Hive 0.14</a>)</li>
 </ul>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive -f hdfs://&lt;namenode&gt;:&lt;port&gt;/hive-script.sql
+<pre tabindex=0><code>$HIVE_HOME/bin/hive -f hdfs://&lt;namenode&gt;:&lt;port&gt;/hive-script.sql
 </code></pre><h3 id=hive-cli-interactive-shell-commands-support>Hive CLI Interactive Shell Commands Support</h3>
 <p>When <code>$HIVE_HOME/bin/hive</code> is run without either the <code>-e</code> or <code>-f</code> option, it enters interactive shell mode.</p>
 <p>Use &ldquo;;&rdquo; (semicolon) to terminate commands. Comments in scripts can be specified using the &ldquo;&ndash;&rdquo; prefix.</p>
@@ -278,9 +278,9 @@ drwxr-xr-x  - root supergroup  0   2015-08-12 19:43 /user
 hive&gt; select * from pokes; 
 OK
 pokes.foo   pokes.bar
-238         val\_238
-86          val\_86
-311         val\_311
+238         val_238
+86          val_86
+311         val_311
 hive&gt;source /opt/s.sql;
 </code></pre><h3 id=hive-cli-configuration-support>Hive CLI Configuration Support</h3>
 <table>
diff --git a/docs/latest/running-yetus_71012969/index.html b/docs/latest/running-yetus_71012969/index.html
index ec0ba94..fc806bc 100644
--- a/docs/latest/running-yetus_71012969/index.html
+++ b/docs/latest/running-yetus_71012969/index.html
@@ -132,7 +132,7 @@ ASF
 </ul>
 <h1 id=findbugs>Findbugs</h1>
 <p>To run findbugs checks, the findbugs binary should be installed on the computer and the FINDBUGS_HOME environment variable should be set. The binary can be downloaded <a href=http://findbugs.sourceforge.net/downloads.html>here</a>.</p>
-<pre tabindex=0><code>export FINDBUGS\_HOME=~/dev/upstream/findbugs-3.0.1/
+<pre tabindex=0><code>export FINDBUGS_HOME=~/dev/upstream/findbugs-3.0.1/
 </code></pre><h1 id=running-yetus>Running Yetus</h1>
 <p>First checkout a copy of the branch you are targeting without your commits.</p>
 <p>Then run the checks with the following command:</p>
diff --git a/docs/latest/scheduled-queries_145724128/index.html b/docs/latest/scheduled-queries_145724128/index.html
index 36d3087..5447fd2 100644
--- a/docs/latest/scheduled-queries_145724128/index.html
+++ b/docs/latest/scheduled-queries_145724128/index.html
@@ -284,10 +284,10 @@ create scheduled query sc1 cron '0 */10 * * * ? *' as insert into t values (1);
 -- it can be enabled using:
 alter scheduled query sc1 enabled;
 
--- inspect scheduled queries using the information\_schema
-select * from information\_schema.scheduled\_queries s where schedule\_name='sc1';
+-- inspect scheduled queries using the information_schema
+select * from information_schema.scheduled_queries s where schedule_name='sc1';
 +-----------------------+------------------+------------+----------------------+-------------------+---------+-----------+----------------------+
-| s.scheduled\_query\_id  | s.schedule\_name  | s.enabled  | s.cluster\_namespace  |    s.schedule     | s.user  |  s.query  |   s.next\_execution   |
+| s.scheduled_query_id  | s.schedule_name  | s.enabled  | s.cluster_namespace  |    s.schedule     | s.user  |  s.query  |   s.next_execution   |
 +-----------------------+------------------+------------+----------------------+-------------------+---------+-----------+----------------------+
 | 1                     | sc1              | true       | hive                 | 0 */10 * * * ? *  | dev     | select 1  | 2020-02-03 15:10:00  |
 +-----------------------+------------------+------------+----------------------+-------------------+---------+-----------+----------------------+
@@ -295,11 +295,11 @@ select * from information\_schema.scheduled\_queries s where schedule\_name='sc1
 -- wait 10 minutes or execute by issuing:
 alter scheduled query sc1 execute;
 
-select * from information\_schema.scheduled\_executions s where schedule\_name='sc1' order by scheduled\_execution\_id desc limit 1;
+select * from information_schema.scheduled_executions s where schedule_name='sc1' order by scheduled_execution_id desc limit 1;
 +---------------------------+------------------+----------------------------------------------------+-----------+----------------------+----------------------+------------+------------------+---------------------+
-| s.scheduled\_execution\_id  | s.schedule\_name  |                s.executor\_query\_id                 |  s.state  |     s.start\_time     |      s.end\_time      | s.elapsed  | s.error\_message  | s.last\_update\_time  |
+| s.scheduled_execution_id  | s.schedule_name  |                s.executor_query_id                 |  s.state  |     s.start_time     |      s.end_time      | s.elapsed  | s.error_message  | s.last_update_time  |
 +---------------------------+------------------+----------------------------------------------------+-----------+----------------------+----------------------+------------+------------------+---------------------+
-| 496                       | sc1              | dev\_20200203152025\_bdf3deac-0ca6-407f-b122-c637e50f99c8 | FINISHED  | 2020-02-03 15:20:23  | 2020-02-03 15:20:31  | 8          | NULL             | NULL                |
+| 496                       | sc1              | dev_20200203152025_bdf3deac-0ca6-407f-b122-c637e50f99c8 | FINISHED  | 2020-02-03 15:20:23  | 2020-02-03 15:20:31  | 8          | NULL             | NULL                |
 +---------------------------+------------------+----------------------------------------------------+-----------+----------------------+----------------------+------------+------------------+---------------------+
 
 </code></pre><h2 id=example-2-analyze-external-table-periodically>Example 2 – analyze external table periodically</h2>
@@ -325,16 +325,16 @@ desc formatted t;
 |                               | numRows                                            | 0                                                  |
 [...]
 
-create scheduled query t\_analyze cron '0 */1 * * * ? *' as analyze table t compute statistics for columns;
+create scheduled query t_analyze cron '0 */1 * * * ? *' as analyze table t compute statistics for columns;
 
 -- wait some time or execute by issuing:
-alter scheduled query t\_analyze execute;
+alter scheduled query t_analyze execute;
 
-select * from information\_schema.scheduled\_executions s where schedule\_name='ex\_analyze' order by scheduled\_execution\_id desc limit 3;
+select * from information_schema.scheduled_executions s where schedule_name='ex_analyze' order by scheduled_execution_id desc limit 3;
 +---------------------------+------------------+----------------------------------------------------+------------+----------------------+----------------------+------------+------------------+----------------------+
-| s.scheduled\_execution\_id  | s.schedule\_name  |                s.executor\_query\_id                 |  s.state   |     s.start\_time     |      s.end\_time      | s.elapsed  | s.error\_message  |  s.last\_update\_time  |
+| s.scheduled_execution_id  | s.schedule_name  |                s.executor_query_id                 |  s.state   |     s.start_time     |      s.end_time      | s.elapsed  | s.error_message  |  s.last_update_time  |
 +---------------------------+------------------+----------------------------------------------------+------------+----------------------+----------------------+------------+------------------+----------------------+
-| 498                       | t\_analyze       | dev\_20200203152640\_a59bc198-3ed3-4ef2-8f63-573607c9914e | FINISHED   | 2020-02-03 15:26:38  | 2020-02-03 15:28:01  | 83         | NULL             | NULL                 |
+| 498                       | t_analyze       | dev_20200203152640_a59bc198-3ed3-4ef2-8f63-573607c9914e | FINISHED   | 2020-02-03 15:26:38  | 2020-02-03 15:28:01  | 83         | NULL             | NULL                 |
 +---------------------------+------------------+----------------------------------------------------+------------+----------------------+----------------------+------------+------------------+----------------------+
 
 -- and the numrows have been updated
@@ -344,7 +344,7 @@ desc formatted t;
 [...]
 
 -- we don't want this running every minute anymore...
-alter scheduled query t\_analyze disable;
+alter scheduled query t_analyze disable;
 </code></pre><h2 id=example-3-materialized-view-rebuild>Example 3 – materialized view rebuild</h2>
 <pre tabindex=0><code>-- some settings...they might be there already
 set hive.support.concurrency=true;
@@ -359,7 +359,7 @@ CREATE TABLE emps (
   deptno INT,
   name VARCHAR(256),
   salary FLOAT,
-  hire\_date TIMESTAMP)
+  hire_date TIMESTAMP)
 STORED AS ORC
 TBLPROPERTIES ('transactional'='true');
  
@@ -380,24 +380,24 @@ insert into emps values (1330, 10, 'Bill', 10000, '2020-01-02');
 
 -- create mv
 CREATE MATERIALIZED VIEW mv1 AS
-  SELECT empid, deptname, hire\_date FROM emps
+  SELECT empid, deptname, hire_date FROM emps
     JOIN depts ON (emps.deptno = depts.deptno)
-    WHERE hire\_date &gt;= '2016-01-01 00:00:00';
+    WHERE hire_date &gt;= '2016-01-01 00:00:00';
 
 EXPLAIN
 SELECT empid, deptname FROM emps
 JOIN depts ON (emps.deptno = depts.deptno)
-WHERE hire\_date &gt;= '2018-01-01';
+WHERE hire_date &gt;= '2018-01-01';
 
 -- create a schedule to rebuild mv
-create scheduled query mv\_rebuild cron '0 */10 * * * ? *' defined as 
+create scheduled query mv_rebuild cron '0 */10 * * * ? *' defined as 
   alter materialized view mv1 rebuild;
 
 -- from this expalin it will be seen that the mv1 is being used
 EXPLAIN
 SELECT empid, deptname FROM emps
 JOIN depts ON (emps.deptno = depts.deptno)
-WHERE hire\_date &gt;= '2018-01-01';
+WHERE hire_date &gt;= '2018-01-01';
 
 -- insert a new record
 insert into emps values (1330, 10, 'Bill', 10000, '2020-01-02');
@@ -406,16 +406,16 @@ insert into emps values (1330, 10, 'Bill', 10000, '2020-01-02');
 EXPLAIN
 SELECT empid, deptname FROM emps
 JOIN depts ON (emps.deptno = depts.deptno)
-WHERE hire\_date &gt;= '2018-01-01';
+WHERE hire_date &gt;= '2018-01-01';
 
 -- wait 10 minutes or execute
-alter scheduled query mv\_rebuild execute;
+alter scheduled query mv_rebuild execute;
 
 -- run it again...the view should be rebuilt
 EXPLAIN
 SELECT empid, deptname FROM emps
 JOIN depts ON (emps.deptno = depts.deptno)
-WHERE hire\_date &gt;= '2018-01-01';
+WHERE hire_date &gt;= '2018-01-01';
 
 </code></pre><h2 id=example-4-ingestion>Example 4 – Ingestion</h2>
 <pre tabindex=0><code>drop table if exists t;
@@ -427,24 +427,24 @@ create table s(id integer, cnt integer);
 
 -- create an internal table and an offset table
 create table t(id integer, cnt integer);
-create table t\_offset(offset integer);
-insert into t\_offset values(0);
+create table t_offset(offset integer);
+insert into t_offset values(0);
 
 -- pretend that data is added to s
 insert into s values(1,1);
 
 -- run an ingestion...
 from (select id==offset as first,* from s
-join t\_offset on id&gt;=offset) s1
+join t_offset on id&gt;=offset) s1
 insert into t select id,cnt where first = false
-insert overwrite table t\_offset select max(s1.id);
+insert overwrite table t_offset select max(s1.id);
 
 -- configure to run ingestion every 10 minutes
 create scheduled query ingest every 10 minutes defined as
 from (select id==offset as first,* from s
-join t\_offset on id&gt;=offset) s1
+join t_offset on id&gt;=offset) s1
 insert into t select id,cnt where first = false
-insert overwrite table t\_offset select max(s1.id);
+insert overwrite table t_offset select max(s1.id);
 
 -- add some new values
 insert into s values(2,2),(3,3);
diff --git a/docs/latest/setting-up-hive-with-docker_282102281/index.html b/docs/latest/setting-up-hive-with-docker_282102281/index.html
index e405c79..5ea8fbe 100644
--- a/docs/latest/setting-up-hive-with-docker_282102281/index.html
+++ b/docs/latest/setting-up-hive-with-docker_282102281/index.html
@@ -145,17 +145,17 @@ ASF
 
 </code></pre><p>Everything would be lost when the service is down. In order to save the Hive table&rsquo;s schema and data, start the container with an external Postgres and Volume to keep them,</p>
 <pre tabindex=0><code>docker run -d -p 9083:9083 --env SERVICE_NAME=metastore --env DB_DRIVER=postgres \  
-     --env SERVICE_OPTS=&quot;-Djavax.jdo.option.ConnectionDriverName=org.postgresql.Driver -Djavax.jdo.option.ConnectionURL=jdbc:postgresql://postgres:5432/metastore\_db -Djavax.jdo.option.ConnectionUserName=hive -Djavax.jdo.option.ConnectionPassword=password&quot; \  
+     --env SERVICE_OPTS=&quot;-Djavax.jdo.option.ConnectionDriverName=org.postgresql.Driver -Djavax.jdo.option.ConnectionURL=jdbc:postgresql://postgres:5432/metastore_db -Djavax.jdo.option.ConnectionUserName=hive -Djavax.jdo.option.ConnectionPassword=password&quot; \  
      --mount source=warehouse,target=/opt/hive/data/warehouse \  
      --mount type=bind,source=`mvn help:evaluate -Dexpression=settings.localRepository -q -DforceStdout`/org/postgresql/postgresql/42.5.1/postgresql-42.5.1.jar,target=/opt/hive/lib/postgres.jar \  
      --name metastore-standalone apache/hive:4.0.0
 </code></pre><p>If you want to use your own <code>hdfs-site.xml</code> or <code>yarn-site.xml</code> for the service, you can provide the environment variable <code>HIVE_CUSTOM_CONF_DIR</code> for the command. For instance, put the custom configuration file under the directory <code>/opt/hive/conf</code>, then run,</p>
-<pre tabindex=0><code>docker run -d -p 9083:9083 --env SERVICE\_NAME=metastore --env DB\_DRIVER=postgres \
-     -v /opt/hive/conf:/hive\_custom\_conf --env HIVE\_CUSTOM\_CONF\_DIR=/hive\_custom\_conf \
+<pre tabindex=0><code>docker run -d -p 9083:9083 --env SERVICE_NAME=metastore --env DB_DRIVER=postgres \
+     -v /opt/hive/conf:/hive_custom_conf --env HIVE_CUSTOM_CONF_DIR=/hive_custom_conf \
      --mount type=bind,source=`mvn help:evaluate -Dexpression=settings.localRepository -q -DforceStdout`/org/postgresql/postgresql/42.5.1/postgresql-42.5.1.jar,target=/opt/hive/lib/postgres.jar \
      --name metastore apache/hive:4.0.0  
   
-For Hive releases before 4.0, if you want to upgrade the existing external Metastore schema to the target version, then add --env SCHEMA\_COMMAND=upgradeSchema to the command.  
+For Hive releases before 4.0, if you want to upgrade the existing external Metastore schema to the target version, then add --env SCHEMA_COMMAND=upgradeSchema to the command.  
 To skip schematool initialisation or upgrade for metastore use --env `IS_RESUME=&quot;true&quot;`, and for verbose logging set --env `VERBOSE=&quot;true&quot;.`
 </code></pre><h5 id=--hiveserver2><strong>- HiveServer2</strong></h5>
 <p>Launch the HiveServer2 with an embedded Metastore,</p>
@@ -176,10 +176,10 @@ To skip schematool initialisation or upgrade for metastore use --env `IS_RESUME=
 
 </code></pre><h5 id=--hiveserver2-metastore><strong>- HiveServer2, Metastore</strong></h5>
 <p>To get a quick overview of both HiveServer2 and Metastore, there is a <code>docker-compose.yml</code> placed under <code>packaging/src/docker</code> for this purpose, specify the <code>POSTGRES_LOCAL_PATH</code> first:</p>
-<pre tabindex=0><code>export POSTGRES\_LOCAL\_PATH=your\_local\_path\_to\_postgres\_driver
+<pre tabindex=0><code>export POSTGRES_LOCAL_PATH=your_local_path_to_postgres_driver
 </code></pre><p>Example:</p>
 <pre tabindex=0><code>mvn dependency:copy -Dartifact=&quot;org.postgresql:postgresql:42.5.1&quot; &amp;&amp; \
-export POSTGRES\_LOCAL\_PATH=`mvn help:evaluate -Dexpression=settings.localRepository -q -DforceStdout`/org/postgresql/postgresql/42.5.1/postgresql-42.5.1.jar 
+export POSTGRES_LOCAL_PATH=`mvn help:evaluate -Dexpression=settings.localRepository -q -DforceStdout`/org/postgresql/postgresql/42.5.1/postgresql-42.5.1.jar 
 </code></pre><p>If you don&rsquo;t install maven or have problem in resolving the postgres driver, you can always download this jar yourself, change the <code>POSTGRES_LOCAL_PATH</code> to the path of the downloaded jar.</p>
 <p>Then,</p>
 <pre tabindex=0><code>docker compose up -d
diff --git a/docs/latest/setting-up-hiveserver2_30758712/index.html b/docs/latest/setting-up-hiveserver2_30758712/index.html
index 85429cf..082da6f 100644
--- a/docs/latest/setting-up-hiveserver2_30758712/index.html
+++ b/docs/latest/setting-up-hiveserver2_30758712/index.html
@@ -233,14 +233,14 @@ HIVE_SERVER2_THRIFT_PORT – Optional TCP port number to listen on, default 1000
 <li><a href=#hive-server2-logging-operation-level>hive.server2.logging.operation.level</a> (Hive 1.2 onward)</li>
 </ul>
 <h2 id=how-to-start>How to Start</h2>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hiveserver2
+<pre tabindex=0><code>$HIVE_HOME/bin/hiveserver2
 
 </code></pre><p>OR</p>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive --service hiveserver2
+<pre tabindex=0><code>$HIVE_HOME/bin/hive --service hiveserver2
 
 </code></pre><h4 id=usage-message><strong>Usage Message</strong></h4>
 <p>The <code>-H</code> or <code>--help</code> option displays a usage message, for example:</p>
-<pre tabindex=0><code>$HIVE\_HOME/bin/hive --service hiveserver2 -H
+<pre tabindex=0><code>$HIVE_HOME/bin/hive --service hiveserver2 -H
 Starting HiveServer2
 usage: hiveserver2
  -H,--help                        Print help information
diff --git a/docs/latest/sql-standard-based-hive-authorization_40509928/index.html b/docs/latest/sql-standard-based-hive-authorization_40509928/index.html
index fdda22f..92e30c4 100644
--- a/docs/latest/sql-standard-based-hive-authorization_40509928/index.html
+++ b/docs/latest/sql-standard-based-hive-authorization_40509928/index.html
@@ -203,11 +203,11 @@ They have privileges for running additional commands such as &ldquo;<code>create
 <p>As of <a href=https://issues.apache.org/jira/browse/HIVE-8083>Hive 0.14</a>, user may be optionally surrounded by backtick characters (<code>) irrespective of the </code><a href=https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.support.quoted.identifiers>hive.support.quoted.identifiers</a>` setting.</p>
 <h3 id=role-management-commands><strong>Role Management Commands</strong></h3>
 <h4 id=create-role>Create Role</h4>
-<pre tabindex=0><code>CREATE ROLE role\_name;
+<pre tabindex=0><code>CREATE ROLE role_name;
 </code></pre><p>Creates a new role. Only the <strong>admin</strong> role has privilege for this.</p>
 <p>The role names ALL, DEFAULT and NONE are reserved.</p>
 <h4 id=drop-role>Drop Role</h4>
-<pre tabindex=0><code>DROP ROLE role\_name;
+<pre tabindex=0><code>DROP ROLE role_name;
 </code></pre><p>Drops the given role. Only the <strong>admin</strong> role has privilege for this.</p>
 <h4 id=show-current-roles>Show Current Roles</h4>
 <pre tabindex=0><code>SHOW CURRENT ROLES;
@@ -215,7 +215,7 @@ They have privileges for running additional commands such as &ldquo;<code>create
 <p>The default current roles has all roles for the user except for the <strong>admin</strong> role (even if the user belongs to the <strong>admin</strong> role as well).</p>
 <p>Any user can run this command.</p>
 <h4 id=set-role>Set Role</h4>
-<pre tabindex=0><code>SET ROLE (role\_name|ALL|NONE);
+<pre tabindex=0><code>SET ROLE (role_name|ALL|NONE);
 </code></pre><p>If a role_name is specified, then that role becomes the only role in current roles.</p>
 <p>Setting role_name to ALL refreshes the list of current roles (in case new roles were granted to the user) and sets them to the default list of roles.</p>
 <p>Setting role_name to NONE will remove all current roles from the current user. (It&rsquo;s introduced in <a href=https://issues.apache.org/jira/browse/HIVE-11780>HIVE-11780</a> and will be included in the upcoming versions 1.3.0 and 1.2.2.)</p>
@@ -225,27 +225,27 @@ They have privileges for running additional commands such as &ldquo;<code>create
 </code></pre><p>List all currently existing roles.</p>
 <p>Only the <strong>admin</strong> role has privilege for this.</p>
 <h4 id=grant-role>Grant Role</h4>
-<pre tabindex=0><code>GRANT role\_name [, role\_name] ...
-TO principal\_specification [, principal\_specification] ... 
+<pre tabindex=0><code>GRANT role_name [, role_name] ...
+TO principal_specification [, principal_specification] ... 
 [ WITH ADMIN OPTION ];
 
-principal\_specification
+principal_specification
   : USER user
   | ROLE role
 </code></pre><p>Grant one or more roles to other roles or users.</p>
 <p>If “WITH ADMIN OPTION” is specified, then the user gets privileges to grant the role to other users/roles.</p>
 <p>If the grant statement ends up creating a cycling relationship between roles, the command will fail with an error.</p>
 <h4 id=revoke-role>Revoke Role</h4>
-<pre tabindex=0><code>REVOKE [ADMIN OPTION FOR] role\_name [, role\_name] ...
-FROM principal\_specification [, principal\_specification] ... ;
+<pre tabindex=0><code>REVOKE [ADMIN OPTION FOR] role_name [, role_name] ...
+FROM principal_specification [, principal_specification] ... ;
 
-principal\_specification
+principal_specification
   : USER user
   | ROLE role
 </code></pre><p>Revokes the membership of the roles from the user/roles in the FROM clause.</p>
 <p>As of Hive 0.14.0, revoking just the ADMIN OPTION is possible with the use of REVOKE ADMIN OPTION FOR (<a href=https://issues.apache.org/jira/browse/HIVE-6252>HIVE-6252</a>).</p>
 <h4 id=show-role-grant>Show Role Grant</h4>
-<pre tabindex=0><code>SHOW ROLE GRANT (USER|ROLE) principal\_name;
+<pre tabindex=0><code>SHOW ROLE GRANT (USER|ROLE) principal_name;
 </code></pre><p>where <code>principal_name</code> is the name of a user or role.</p>
 <p>Lists all roles the given user or role has been granted.</p>
 <p>Currently any user can run this command. But this is likely to change in future to allow users to see only their own role grants, and additional privileges would be needed to see role grants of other users.</p>
@@ -255,19 +255,19 @@ No rows affected (0.058 seconds)
 
 0: jdbc:hive2://localhost:10000&gt; SHOW ROLE GRANT USER user1;
 +---------+---------------+----------------+----------+
-|  role   | grant\_option  |   grant\_time   | grantor  |
+|  role   | grant_option  |   grant_time   | grantor  |
 +---------+---------------+----------------+----------+
 | public  | false         | 0              |          |
 | role1   | false         | 1398284083000  | uadmin   |
 +---------+---------------+----------------+----------+
 </code></pre><h4 id=show-principals>Show Principals</h4>
-<pre tabindex=0><code>SHOW PRINCIPALS role\_name;
+<pre tabindex=0><code>SHOW PRINCIPALS role_name;
 </code></pre><p>Lists all roles and users who belong to this role.</p>
 <p>Only the <strong>admin</strong> role has privilege for this.</p>
 <h5 id=example-of-show-principals>Example of Show Principals</h5>
 <pre tabindex=0><code>0: jdbc:hive2://localhost:10000&gt; SHOW PRINCIPALS role1;
 +-----------------+-----------------+---------------+----------+---------------+----------------+
-| principal\_name  | principal\_type  | grant\_option  | grantor  | grantor\_type  |   grant\_time   |
+| principal_name  | principal_type  | grant_option  | grantor  | grantor_type  |   grant_time   |
 +-----------------+-----------------+---------------+----------+---------------+----------------+
 | role2           | ROLE            | false         | uadmin   | USER          | 1398285926000  |
 | role3           | ROLE            | true          | uadmin   | USER          | 1398285946000  |
@@ -277,35 +277,35 @@ No rows affected (0.058 seconds)
 <h3 id=object-privilege-commands>Object Privilege Commands</h3>
 <h4 id=grant>Grant</h4>
 <pre tabindex=0><code>GRANT
-    priv\_type [, priv\_type ] ...
-    ON table\_or\_view\_name
-    TO principal\_specification [, principal\_specification] ...
+    priv_type [, priv_type ] ...
+    ON table_or_view_name
+    TO principal_specification [, principal_specification] ...
     [WITH GRANT OPTION];
 </code></pre><h4 id=revoke>Revoke</h4>
 <pre tabindex=0><code>REVOKE [GRANT OPTION FOR]
-    priv\_type [, priv\_type ] ...
-    ON table\_or\_view\_name
-    FROM principal\_specification [, principal\_specification] ... ;
+    priv_type [, priv_type ] ...
+    ON table_or_view_name
+    FROM principal_specification [, principal_specification] ... ;
 
-principal\_specification
+principal_specification
   : USER user
   | ROLE role
  
-priv\_type
+priv_type
   : INSERT | SELECT | UPDATE | DELETE | ALL
 </code></pre><p>If a user is granted a privilege WITH GRANT OPTION on a table or view, then the user can also grant/revoke privileges of other users and roles on those objects. As of Hive 0.14.0, the grant option for a privilege can be removed while still keeping the privilege by using REVOKE GRANT OPTION FOR (<a href=https://issues.apache.org/jira/browse/HIVE-7404>HIVE-7404</a>).</p>
 <p>Note that in case of the REVOKE statement, the DROP-BEHAVIOR option of CASCADE is not currently supported (which is in SQL standard). As a result, the revoke statement will not drop any dependent privileges. For details on CASCADE behavior, you can check the <a href=http://www.postgresql.org/docs/8.4/static/sql-revoke.html>Postgres revoke documentation</a>.</p>
 <p>Examples:</p>
-<pre tabindex=0><code>0: jdbc:hive2://localhost:10000/default&gt; grant select on table secured\_table to role my\_role;
+<pre tabindex=0><code>0: jdbc:hive2://localhost:10000/default&gt; grant select on table secured_table to role my_role;
 No rows affected (0.046 seconds)
 
-0: jdbc:hive2://localhost:10000/default&gt; revoke update, select on table secured\_table from role my\_role;
+0: jdbc:hive2://localhost:10000/default&gt; revoke update, select on table secured_table from role my_role;
 No rows affected (0.028 seconds)
 </code></pre><p>Notice that in Hive, unlike in standard SQL, USER or ROLE must be specified in the principal_specification.</p>
 <h4 id=show-grant>Show Grant</h4>
-<pre tabindex=0><code>SHOW GRANT [principal\_specification] ON (ALL | [TABLE] table\_or\_view\_name);
+<pre tabindex=0><code>SHOW GRANT [principal_specification] ON (ALL | [TABLE] table_or_view_name);
  
-principal\_specification
+principal_specification
   : USER user
   | ROLE role
 </code></pre><p>Currently any user can run this command. But this is likely to change in the future to allow users to see only their own privileges, and additional privileges would be needed to see privileges of other users.</p>
@@ -313,7 +313,7 @@ principal\_specification
 <p>Find out the privileges user ashutosh has on table hivejiratable:</p>
 <pre tabindex=0><code>0: jdbc:hive2://localhost:10000&gt; show grant user ashutosh on table hivejiratable;
 +-----------+----------------+------------+---------+-----------------+-----------------+------------+---------------+----------------+----------+
-| database  |     table      | partition  | column  | principal\_name  | principal\_type  | privilege  | grant\_option  |   grant\_time   | grantor  |
+| database  |     table      | partition  | column  | principal_name  | principal_type  | privilege  | grant_option  |   grant_time   | grantor  |
 +-----------+----------------+------------+---------+-----------------+-----------------+------------+---------------+----------------+----------+
 | default   | hivejiratable  |            |         | ashutosh        | USER            | DELETE     | false         | 1398303419000  | thejas   |
 | default   | hivejiratable  |            |         | ashutosh        | USER            | SELECT     | false         | 1398303407000  | thejas   |
@@ -322,7 +322,7 @@ principal\_specification
 <p>Find out the privileges user ashutosh has on all objects:</p>
 <pre tabindex=0><code>0: jdbc:hive2://localhost:10000&gt; show grant user ashutosh on all;                               
 +-----------+-------------------+------------+---------+-----------------+-----------------+------------+---------------+----------------+----------+
-| database  |       table       | partition  | column  | principal\_name  | principal\_type  | privilege  | grant\_option  |   grant\_time   | grantor  |
+| database  |       table       | partition  | column  | principal_name  | principal_type  | privilege  | grant_option  |   grant_time   | grantor  |
 +-----------+-------------------+------------+---------+-----------------+-----------------+------------+---------------+----------------+----------+
 | default   | hivecontributors  |            |         | ashutosh        | USER            | DELETE     | false         | 1398303576000  | thejas   |
 | default   | hivecontributors  |            |         | ashutosh        | USER            | INSERT     | false         | 1398303576000  | thejas   |
@@ -334,7 +334,7 @@ principal\_specification
 <p>Find out the privileges all users have on table hivejiratable:</p>
 <pre tabindex=0><code>0: jdbc:hive2://localhost:10000&gt; show grant on table hivejiratable;
 +-----------+----------------+------------+---------+-----------------+-----------------+------------+---------------+----------------+----------+
-| database  |     table      | partition  | column  | principal\_name  | principal\_type  | privilege  | grant\_option  |   grant\_time   | grantor  |
+| database  |     table      | partition  | column  | principal_name  | principal_type  | privilege  | grant_option  |   grant_time   | grantor  |
 +-----------+----------------+------------+---------+-----------------+-----------------+------------+---------------+----------------+----------+
 | default   | hivejiratable  |            |         | ashutosh        | USER            | DELETE     | false         | 1398303419000  | thejas   |
 | default   | hivejiratable  |            |         | ashutosh        | USER            | SELECT     | false         | 1398303407000  | thejas   |
diff --git a/docs/latest/statisticsanddatamining_27362058/index.html b/docs/latest/statisticsanddatamining_27362058/index.html
index 63b5164..c2e8380 100644
--- a/docs/latest/statisticsanddatamining_27362058/index.html
+++ b/docs/latest/statisticsanddatamining_27362058/index.html
@@ -163,17 +163,17 @@ ASF
 </ol>
 <h3 id=usage>Usage</h3>
 <pre tabindex=0><code>
-SELECT context\_ngrams(sentences(lower(tweet)), 2, 100 [, 1000]) FROM twitter;
+SELECT context_ngrams(sentences(lower(tweet)), 2, 100 [, 1000]) FROM twitter;
 
 </code></pre><p>The command above will return the top-100 bigrams (2-grams) from a hypothetical table called <code>twitter</code>. The <code>tweet</code> column is assumed to contain a string with arbitrary, possibly meaningless, text. The <code>lower()</code> UDF first converts the text to lowercase for standardization, and then <code>sentences()</code> splits up the text into arrays of words. The optional fourth argument is the <strong>precision factor</strong> that control the tradeof [...]
 <pre tabindex=0><code>
-SELECT context\_ngrams(sentences(lower(tweet)), array(&quot;i&quot;,&quot;love&quot;,null), 100, [, 1000]) FROM twitter;
+SELECT context_ngrams(sentences(lower(tweet)), array(&quot;i&quot;,&quot;love&quot;,null), 100, [, 1000]) FROM twitter;
 
 </code></pre><p>The command above will return a list of the top 100 words that follow the phrase &ldquo;i love&rdquo; in a hypothetical database of Twitter tweets. Each <code>null</code> specifies the position of an n-gram component to estimate; therefore, every query must contain at least one <code>null</code> in the context array.</p>
 <p>Note that the following two queries are identical, but <code>ngrams()</code> will be slightly faster in practice.</p>
 <pre tabindex=0><code>
 SELECT ngrams(sentences(lower(tweet)), 2, 100 [, 1000]) FROM twitter;
-SELECT context\_ngrams(sentences(lower(tweet)), array(null,null), 100, [, 1000]) FROM twitter;
+SELECT context_ngrams(sentences(lower(tweet)), array(null,null), 100, [, 1000]) FROM twitter;
 
 </code></pre><h3 id=example>Example</h3>
 <pre tabindex=0><code>
@@ -190,7 +190,7 @@ SELECT explode(ngrams(sentences(lower(val)), 2, 10)) AS x FROM kafka;
 {&quot;ngram&quot;:[it&quot;,&quot;was],&quot;estfrequency&quot;:15.0}
 
 </code></pre><pre tabindex=0><code>
-SELECT explode(context\_ngrams(sentences(lower(val)), array(&quot;he&quot;, null), 10)) AS x FROM kafka;
+SELECT explode(context_ngrams(sentences(lower(val)), array(&quot;he&quot;, null), 10)) AS x FROM kafka;
 {&quot;ngram&quot;:[was],&quot;estfrequency&quot;:17.0}
 {&quot;ngram&quot;:[had],&quot;estfrequency&quot;:16.0}
 {&quot;ngram&quot;:[thought],&quot;estfrequency&quot;:13.0}
@@ -215,7 +215,7 @@ SELECT explode(context\_ngrams(sentences(lower(val)), array(&quot;he&quot;, null
 </ol>
 <h3 id=usage-1>Usage</h3>
 <pre tabindex=0><code>
-SELECT histogram\_numeric(age) FROM users GROUP BY gender;
+SELECT histogram_numeric(age) FROM users GROUP BY gender;
 
 </code></pre><p>The command above is self-explanatory. Converting the output into a graphical display is a bit more involved. The following <a href=http://www.gnuplot.info/>Gnuplot</a> command should do it, assuming that you&rsquo;ve parsed the output from <code>histogram()</code> into a text file of (x,y) pairs called <code>data.txt</code>.</p>
 <pre tabindex=0><code>
@@ -223,7 +223,7 @@ plot 'data.txt' u 1:2 w impulses lw 5
 
 </code></pre><h3 id=example-1>Example</h3>
 <pre tabindex=0><code>
-SELECT explode(histogram\_numeric(val, 10)) AS x FROM normal;
+SELECT explode(histogram_numeric(val, 10)) AS x FROM normal;
 {&quot;x&quot;:-3.6505464999999995,&quot;y&quot;:20.0}
 {&quot;x&quot;:-2.7514727901960785,&quot;y&quot;:510.0}
 {&quot;x&quot;:-1.7956678951954481,&quot;y&quot;:8263.0}
diff --git a/docs/latest/statsdev_27362062/index.html b/docs/latest/statsdev_27362062/index.html
index ccfd209..4dc2670 100644
--- a/docs/latest/statsdev_27362062/index.html
+++ b/docs/latest/statsdev_27362062/index.html
@@ -427,7 +427,7 @@ set hive.stats.jdbcdriver=&quot;org.apache.derby.jdbc.EmbeddedDriver&quot;;
 </code></pre><p>Queries can fail to collect stats completely accurately. There is a setting <strong><a href=#hive-stats-reliable>hive.stats.reliable</a></strong> that fails queries if the stats can&rsquo;t be reliably collected. This is <code>false</code> by default.</p>
 <h3 id=existing-tables-analyze>Existing Tables – ANALYZE</h3>
 <p>For existing tables and/or partitions, the user can issue the ANALYZE command to gather statistics and write them into Hive MetaStore. The syntax for that command is described below:</p>
-<pre tabindex=0><code>ANALYZE TABLE [db\_name.]tablename [PARTITION(partcol1[=val1], partcol2[=val2], ...)]  -- (Note: Fully support qualified table name since Hive 1.2.0, see HIVE-10007.)
+<pre tabindex=0><code>ANALYZE TABLE [db_name.]tablename [PARTITION(partcol1[=val1], partcol2[=val2], ...)]  -- (Note: Fully support qualified table name since Hive 1.2.0, see HIVE-10007.)
   COMPUTE STATISTICS 
   [FOR COLUMNS]          -- (Note: Hive 0.10.0 and later.)
   [CACHE METADATA]       -- (Note: Hive 2.1.0 and later.)
@@ -497,22 +497,22 @@ set hive.stats.jdbcdriver=&quot;org.apache.derby.jdbc.EmbeddedDriver&quot;;
 <pre tabindex=0><code> ... , parameters:{numFiles=4, numRows=500, totalSize=4096, ...}, ....
 
 </code></pre><p>If you issue the command:</p>
-<pre tabindex=0><code>desc formatted concurrent\_delete\_different partition(ds='tomorrow') name;
+<pre tabindex=0><code>desc formatted concurrent_delete_different partition(ds='tomorrow') name;
 
 </code></pre><p>the output would look like this:</p>
 <pre tabindex=0><code>+-----------------+--------------------+-------+-------+------------+-----------------+--------------+--------------+------------+-------------+------------+----------+
-|    col\_name     |     data\_type      |  min  |  max  | num\_nulls  | distinct\_count  | avg\_col\_len  | max\_col\_len  | num\_trues  | num\_falses  | bitvector  | comment  |
+|    col_name     |     data_type      |  min  |  max  | num_nulls  | distinct_count  | avg_col_len  | max_col_len  | num_trues  | num_falses  | bitvector  | comment  |
 +-----------------+--------------------+-------+-------+------------+-----------------+--------------+--------------+------------+-------------+------------+----------+
-| col\_name        | name               | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
-| data\_type       | varchar(50)        | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
+| col_name        | name               | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
+| data_type       | varchar(50)        | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
 | min             |                    | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
 | max             |                    | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
-| num\_nulls       | 0                  | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
-| distinct\_count  | 2                  | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
-| avg\_col\_len     | 5.0                | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
-| max\_col\_len     | 5                  | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
-| num\_trues       |                    | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
-| num\_falses      |                    | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
+| num_nulls       | 0                  | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
+| distinct_count  | 2                  | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
+| avg_col_len     | 5.0                | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
+| max_col_len     | 5                  | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
+| num_trues       |                    | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
+| num_falses      |                    | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
 | bitVector       |                    | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
 | comment         | from deserializer  | NULL  | NULL  | NULL       | NULL            | NULL         | NULL         | NULL       | NULL        | NULL       | NULL     |
 +-----------------+--------------------+-------+-------+------------+-----------------+--------------+--------------+------------+-------------+------------+----------+
diff --git a/docs/latest/storagehandlers_27362063/index.html b/docs/latest/storagehandlers_27362063/index.html
index 38e5559..7ba8af7 100644
--- a/docs/latest/storagehandlers_27362063/index.html
+++ b/docs/latest/storagehandlers_27362063/index.html
@@ -151,26 +151,26 @@ ASF
 <p>Note that we avoid the term <em>file-based</em> in these definitions, since the form of storage used by the other system is irrelevant.</p>
 <h2 id=ddl>DDL</h2>
 <p>Storage handlers are associated with a table when it is created via the new STORED BY clause, an alternative to the existing ROW FORMAT and STORED AS clause:</p>
-<pre tabindex=0><code>CREATE [EXTERNAL] TABLE [IF NOT EXISTS] table\_name
-  [(col\_name data\_type [COMMENT col\_comment], ...)]
-  [COMMENT table\_comment]
-  [PARTITIONED BY (col\_name data\_type [col\_comment], col\_name data\_type [COMMENT col\_comment], ...)]
-  [CLUSTERED BY (col\_name, col\_name, ...) [SORTED BY (col\_name, ...)] INTO num\_buckets BUCKETS]
+<pre tabindex=0><code>CREATE [EXTERNAL] TABLE [IF NOT EXISTS] table_name
+  [(col_name data_type [COMMENT col_comment], ...)]
+  [COMMENT table_comment]
+  [PARTITIONED BY (col_name data_type [col_comment], col_name data_type [COMMENT col_comment], ...)]
+  [CLUSTERED BY (col_name, col_name, ...) [SORTED BY (col_name, ...)] INTO num_buckets BUCKETS]
   [
-   [ROW FORMAT row\_format] [STORED AS file\_format]
+   [ROW FORMAT row_format] [STORED AS file_format]
    | STORED BY 'storage.handler.class.name' [WITH SERDEPROPERTIES (...)]
   ]
-  [LOCATION hdfs\_path]
-  [AS select\_statement]
+  [LOCATION hdfs_path]
+  [AS select_statement]
 
 </code></pre><p>When STORED BY is specified, then row_format (DELIMITED or SERDE) and STORED AS cannot be specified, however starting from <a href=https://cwiki.apache.org/confluence/display/Hive/Hive-Iceberg+Integration>Hive 4.0</a>, they can coexist to create the Iceberg table, this is the only exception. Optional SERDEPROPERTIES can be specified as part of the STORED BY clause and will be passed to the serde provided by the storage handler.</p>
 <p>See <a href=#create-table>CREATE TABLE</a> and <a href=#row-format,-storage-format,-and-serde>Row Format, Storage Format, and SerDe</a> for more information.</p>
 <p>Example:</p>
-<pre tabindex=0><code>CREATE TABLE hbase\_table\_1(key int, value string) 
+<pre tabindex=0><code>CREATE TABLE hbase_table_1(key int, value string) 
 STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
 WITH SERDEPROPERTIES (
 &quot;hbase.columns.mapping&quot; = &quot;cf:string&quot;,
-&quot;hbase.table.name&quot; = &quot;hbase\_table\_0&quot;
+&quot;hbase.table.name&quot; = &quot;hbase_table_0&quot;
 );
 
 </code></pre><p>DROP TABLE works as usual, but ALTER TABLE is not yet supported for non-native tables.</p>
diff --git a/docs/latest/streaming-data-ingest-v2_85477610/index.html b/docs/latest/streaming-data-ingest-v2_85477610/index.html
index a843109..3f2df36 100644
--- a/docs/latest/streaming-data-ingest-v2_85477610/index.html
+++ b/docs/latest/streaming-data-ingest-v2_85477610/index.html
@@ -211,10 +211,10 @@ ASF
 <h2 id=io--writing-data>I/O – Writing Data</h2>
 <p>These classes and interfaces provide support for writing the data to Hive within a transaction.</p>
 <h3 id=recordwriter>RecordWriter</h3>
-<p>RecordWriter is the base interface implemented by all Writers. A Writer is responsible for taking a record in the form of a byte[] (or InputStream with configurable line delimiter) containing data in a known format (such as CSV) and writing it out in the format supported by Hive streaming. A RecordWriter with Strict implementation expects record schema to exactly match as that of table schema. A RecordWriter writing in dynamic partitioning mode expects the partition columns to be the  [...]
+<p>RecordWriter is the base interface implemented by all Writers. A Writer is responsible for taking a record in the form of a byte[] (or InputStream with configurable line delimiter) containing data in a known format (such as CSV) and writing it out in the format supported by Hive streaming. A RecordWriter with Strict implementation expects record schema to exactly match as that of table schema. A RecordWriter writing in dynamic partitioning mode expects the partition columns to be the  [...]
 <p>A RecordWriter&rsquo;s primary functions are:</p>
 <ol>
-<li>Modify input record: This may involve dropping fields from input data if they don’t have corresponding table columns, adding nulls in case of missing fields for certain columns, and adding __HIVE_DEFAULT_PARTITION__ if partition column value is null or empty. Dynamically creating partitions requires understanding of incoming data format to extract last columns to extract partition values.</li>
+<li>Modify input record: This may involve dropping fields from input data if they don’t have corresponding table columns, adding nulls in case of missing fields for certain columns, and adding <strong>HIVE_DEFAULT_PARTITION</strong> if partition column value is null or empty. Dynamically creating partitions requires understanding of incoming data format to extract last columns to extract partition values.</li>
 <li>Encode modified record: The encoding involves serialization using an appropriate <a href=https://hive.apache.org/docs/latest/serde_27362059/>Hive SerDe</a>.</li>
 <li>For bucketed tables, extract bucket column values from the record to identify the bucket where the record belongs.</li>
 <li>For partitioned tables, in dynamic partitioning mode, extract the partition column values from last N columns (where N is number of partitions) of the record to identify the partition where the record belongs.</li>
diff --git a/docs/latest/subqueries-in-select_68717850/index.html b/docs/latest/subqueries-in-select_68717850/index.html
index 3fe3215..b95c7c9 100644
--- a/docs/latest/subqueries-in-select_68717850/index.html
+++ b/docs/latest/subqueries-in-select_68717850/index.html
@@ -117,11 +117,11 @@ ASF
 <h1 id=apache-hive--subqueries-in-select>Apache Hive : Subqueries in SELECT</h1>
 <h1 id=problem>Problem</h1>
 <p>Currently Hive doesn&rsquo;t support subqueries in a SELECT statement, for example, the following query will not run on Hive:</p>
-<pre tabindex=0><code>SELECT customer.customer\_num,
-	(SELECT SUM(ship\_charge) 
+<pre tabindex=0><code>SELECT customer.customer_num,
+	(SELECT SUM(ship_charge) 
 		FROM orders
-		WHERE customer.customer\_num = orders.customer\_num
-	) AS total\_ship\_chg
+		WHERE customer.customer_num = orders.customer_num
+	) AS total_ship_chg
 FROM customer 
 </code></pre><p>Recently a lot of work has been done to extend support for subqueries (<a href=https://issues.apache.org/jira/browse/HIVE-15456>HIVE-15456</a>). But this work primarily targeted extending subquery support in WHERE and HAVING clauses. We plan to continue the work done in HIVE-15456 to support subqueries in a select list (see <a href=https://issues.apache.org/jira/browse/HIVE-16091>HIVE-16091</a>).</p>
 <h1 id=assumptions>Assumptions</h1>
@@ -131,47 +131,47 @@ FROM customer
 </ul>
 <p><strong>Not Supported</strong></p>
 <pre tabindex=0><code>-- subquery in non-simple expression
-SELECT 1 + (SELECT SUM(ship\_charge) FROM orders), customer.customer\_num FROM customer
+SELECT 1 + (SELECT SUM(ship_charge) FROM orders), customer.customer_num FROM customer
  
 -- subquery in CASE
-SELECT CASE WHEN (select count(*) from store\_sales 
-                  where ss\_quantity between 1 and 20) &gt; 409437
-            THEN (select avg(ss\_ext\_list\_price) 
-                  from store\_sales 
-                  where ss\_quantity between 1 and 20) 
-            ELSE (select avg(ss\_net\_paid\_inc\_tax)
-                  from store\_sales
-                  where ss\_quantity between 1 and 20) end bucket1
+SELECT CASE WHEN (select count(*) from store_sales 
+                  where ss_quantity between 1 and 20) &gt; 409437
+            THEN (select avg(ss_ext_list_price) 
+                  from store_sales 
+                  where ss_quantity between 1 and 20) 
+            ELSE (select avg(ss_net_paid_inc_tax)
+                  from store_sales
+                  where ss_quantity between 1 and 20) end bucket1
 FROM reason
-WHERE r\_reason\_sk = 1
+WHERE r_reason_sk = 1
 </code></pre><ul>
 <li>Scalar subqueries can only return at most one row. Hive will check for this case at runtime and throw an error if not satisfied. For example the following query is invalid:</li>
 </ul>
 <p><strong>Not Supported</strong></p>
-<pre tabindex=0><code>SELECT customer.customer\_num,
-	(SELECT ship\_charge 
+<pre tabindex=0><code>SELECT customer.customer_num,
+	(SELECT ship_charge 
 		FROM orders
-		WHERE customer.customer\_num = orders.customer\_num
-	) AS total\_ship\_chg
+		WHERE customer.customer_num = orders.customer_num
+	) AS total_ship_chg
 FROM customer 
 </code></pre><ul>
 <li>Scalar subqueries can only have one column. Hive will check for this case during compilation and throw an error. For example the following query is invalid:</li>
 </ul>
 <p><strong>Not Supported</strong></p>
-<pre tabindex=0><code>SELECT customer.customer\_num,
-	(SELECT ship\_charge, customer\_num
+<pre tabindex=0><code>SELECT customer.customer_num,
+	(SELECT ship_charge, customer_num
 		FROM orders LIMIT 1
-	) AS total\_ship\_chg
+	) AS total_ship_chg
 FROM customer
 </code></pre><ul>
 <li>Correlated variables are only permitted in a filter, that is, a WHERE or HAVING clause. For example the following query is invalid:</li>
 </ul>
 <p><strong>Not Supported</strong></p>
-<pre tabindex=0><code>SELECT customer.customer\_num,
-	(SELECT customer.customer\_num 
+<pre tabindex=0><code>SELECT customer.customer_num,
+	(SELECT customer.customer_num 
 		FROM orders
-		WHERE customer.customer\_num = orders.customer\_num
-	) AS total\_ship\_chg
+		WHERE customer.customer_num = orders.customer_num
+	) AS total_ship_chg
 FROM customer 
 </code></pre><ul>
 <li>Subqueries with DISTINCT are not allowed. Since DISTINCT will be evaluated as GROUP BY , subqueries with DISTINCT are disallowed for now.</li>
@@ -181,22 +181,22 @@ FROM customer
 <ul>
 <li>Scalar subqueries, for example: </li>
 </ul>
-<pre tabindex=0><code>SELECT customer.customer\_num,
-	(SELECT SUM(ship\_charge) 
+<pre tabindex=0><code>SELECT customer.customer_num,
+	(SELECT SUM(ship_charge) 
 		FROM orders
-		WHERE customer.customer\_num = orders.customer\_num
-	) AS total\_ship\_chg
+		WHERE customer.customer_num = orders.customer_num
+	) AS total_ship_chg
 FROM customer 
 </code></pre><ul>
 <li>IN subqueries, for example:</li>
 </ul>
-<pre tabindex=0><code>SELECT p\_size IN (
-		SELECT MAX(p\_size) FROM part)
+<pre tabindex=0><code>SELECT p_size IN (
+		SELECT MAX(p_size) FROM part)
 FROM part
 </code></pre><ul>
 <li>EXISTS subqueries, for example:</li>
 </ul>
-<pre tabindex=0><code>SELECT EXISTS(SELECT p\_size FROM part)
+<pre tabindex=0><code>SELECT EXISTS(SELECT p_size FROM part)
 FROM part
 </code></pre><p>All of the above queries could be <strong>correlated</strong> or <strong>uncorrelated</strong>.</p>
 <p>Design for this will be similar to the work done in <a href=https://issues.apache.org/jira/browse/HIVE-15456>HIVE-15456</a>.</p>
diff --git a/docs/latest/teradatabinaryserde_89068127/index.html b/docs/latest/teradatabinaryserde_89068127/index.html
index 2cdae04..8b0dfac 100644
--- a/docs/latest/teradatabinaryserde_89068127/index.html
+++ b/docs/latest/teradatabinaryserde_89068127/index.html
@@ -159,25 +159,25 @@ ASF
 <h4 id=using-tpt-fastexport>Using TPT FastExport</h4>
 <p>Here is a bash script example for how to call TPT FastExport:</p>
 <p><strong>TPT FastExport script example</strong></p>
-<pre tabindex=0><code>query\_table=foo.teradata\_binary\_table
... 2115 lines suppressed ...