You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by jr...@apache.org on 2017/11/13 23:26:51 UTC

[1/7] incubator-impala git commit: Update Impala docs for 2.10 release

Repository: incubator-impala
Updated Branches:
  refs/heads/asf-site f79399fdb -> ca9005be5


http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/impala-2.10.pdf
----------------------------------------------------------------------
diff --git a/docs/build/impala-2.10.pdf b/docs/build/impala-2.10.pdf
new file mode 100644
index 0000000..ccdcece
Binary files /dev/null and b/docs/build/impala-2.10.pdf differ

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/impala-docs.html
----------------------------------------------------------------------
diff --git a/impala-docs.html b/impala-docs.html
index c17b6fc..1b4fbfc 100644
--- a/impala-docs.html
+++ b/impala-docs.html
@@ -124,13 +124,15 @@
          preserved. -->
 
     <div class="row">
-    <div class="span12"><h3>Latest Release</h3>
-      <p>Impala 2.10
-        <ul>
-          <li><a href="docs/changelog-2.10.html">Impala 2.10 Change Log</a></li>
-        </ul>
-      </p>
-    </div>
+      <div class="span12"><h3>Latest Release</h3>
+        <p>Impala 2.10
+          <ul>
+            <li><a href="docs/changelog-2.10.html">Impala 2.10 Change Log</a></li>
+            <li><a href="docs/build/html/index.html">HTML Documentation for Impala 2.10</a></li>
+            <li><a href="docs/build/impala-2.10.pdf">PDF Documentation for Impala 2.10</a></li>
+          </ul>
+        </p>
+      </div>
     </div>
 
     <div class="row">
@@ -138,7 +140,6 @@
         <p>Impala 2.9
           <ul>
             <li><a href="docs/changelog-2.9.html">Impala 2.9 Change Log</a></li>
-            <li><a href="docs/build/html/index.html">HTML Documentation for Impala 2.9</a></li>
             <li><a href="docs/build/impala-2.9.pdf">PDF Documentation for Impala 2.9</a></li>
           </ul>
         </p>


[6/7] incubator-impala git commit: Update Impala docs for 2.10 release

Posted by jr...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_default_spillable_buffer_size.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_default_spillable_buffer_size.html b/docs/build/html/topics/impala_default_spillable_buffer_size.html
new file mode 100644
index 0000000..31e5c7e
--- /dev/null
+++ b/docs/build/html/topics/impala_default_spillable_buffer_size.html
@@ -0,0 +1,87 @@
+<!DOCTYPE html
+  SYSTEM "about:legacy-compat">
+<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_query_options.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="default_spillable_buffer_size"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>DEFAULT_SPILLABLE_BUFFER_SIZE Query Option</title></head><body id="default_spillable_buffer_size"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
+
+  <h1 class="title topictitle1" id="ariaid-title1">DEFAULT_SPILLABLE_BUFFER_SIZE Query Option</h1>
+  
+  
+
+  <div class="body conbody">
+
+    <p class="p">
+      
+      Specifies the default size for a memory buffer used when the
+      spill-to-disk mechanism is activated, for example for queries against
+      a large table with no statistics, or large join operations.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Type:</strong> integer
+      </p>
+
+
+
+    <p class="p">
+        <strong class="ph b">Default:</strong>
+      </p>
+    <p class="p">
+      <code class="ph codeph">2097152</code> (2 MB)
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Units:</strong> A numeric argument represents a size in bytes; you can also use a suffix of <code class="ph codeph">m</code>
+        or <code class="ph codeph">mb</code> for megabytes, or <code class="ph codeph">g</code> or <code class="ph codeph">gb</code> for gigabytes. If you
+        specify a value with unrecognized formats, subsequent queries fail with an error.
+      </p>
+
+    <p class="p">
+        <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.10.0</span>
+      </p>
+
+    <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+    <p class="p">
+      This query option sets an upper bound on the size of the internal
+      buffer size that can be used during spill-to-disk operations. The
+      actual size of the buffer is chosen by the query planner.
+    </p>
+    <p class="p">
+      If overall query performance is limited by the time needed for spilling,
+      consider increasing the <code class="ph codeph">DEFAULT_SPILLABLE_BUFFER_SIZE</code> setting.
+      Larger buffer sizes result in Impala issuing larger I/O requests to storage
+      devices, which might result in higher throughput, particularly on rotational
+      disks.
+    </p>
+    <p class="p">
+      The tradeoff with a large value for this setting is increased memory usage during
+      spill-to-disk operations. Reducing this value may reduce memory consumption.
+    </p>
+    <p class="p">
+      To determine if the value for this setting is having an effect by capping the
+      spillable buffer size, you can see the buffer size chosen by the query planner for
+      a particular query. <code class="ph codeph">EXPLAIN</code> the query while the setting
+      <code class="ph codeph">EXPLAIN_LEVEL=2</code> is in effect.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+
+<pre class="pre codeblock"><code>
+set default_spillable_buffer_size=4MB;
+
+</code></pre>
+
+    <p class="p">
+        <strong class="ph b">Related information:</strong>
+      </p>
+    <p class="p">
+      <a class="xref" href="impala_buffer_pool_limit.html">BUFFER_POOL_LIMIT Query Option</a>,
+      <a class="xref" href="impala_max_row_size.html">MAX_ROW_SIZE Query Option</a>,
+      <a class="xref" href="impala_min_spillable_buffer_size.html">MIN_SPILLABLE_BUFFER_SIZE Query Option</a>,
+      <a class="xref" href="impala_scalability.html">Scalability Considerations for Impala</a>
+    </p>
+
+  </div>
+<nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_query_options.html">Query Options for the SET Statement</a></div></div></nav></article></main></body></html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_exec_single_node_rows_threshold.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_exec_single_node_rows_threshold.html b/docs/build/html/topics/impala_exec_single_node_rows_threshold.html
index aa43a0c..1a9c508 100644
--- a/docs/build/html/topics/impala_exec_single_node_rows_threshold.html
+++ b/docs/build/html/topics/impala_exec_single_node_rows_threshold.html
@@ -65,7 +65,7 @@
     </p>
 
     <p class="p">
-        <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.1.0</span>
+        <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.10</span>
       </p>
 
     <p class="p">


[7/7] incubator-impala git commit: Update Impala docs for 2.10 release

Posted by jr...@apache.org.
Update Impala docs for 2.10 release

Commit hash = 40ec6d0080638efaf3260672ab54ea4674896c5e

Several new HTML files for this release.

Change-Id: Idea1f417d404b99dad9fb8255849867f1e67e767
Reviewed-on: http://gerrit.cloudera.org:8080/8511
Reviewed-by: Michael Brown <mi...@cloudera.com>
Tested-by: John Russell <jr...@cloudera.com>


Project: http://git-wip-us.apache.org/repos/asf/incubator-impala/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-impala/commit/ca9005be
Tree: http://git-wip-us.apache.org/repos/asf/incubator-impala/tree/ca9005be
Diff: http://git-wip-us.apache.org/repos/asf/incubator-impala/diff/ca9005be

Branch: refs/heads/asf-site
Commit: ca9005be57eb3151d6842dd62e740ca323014742
Parents: f79399f
Author: John Russell <jr...@cloudera.com>
Authored: Thu Nov 9 14:21:39 2017 -0800
Committer: John Russell <jr...@cloudera.com>
Committed: Mon Nov 13 23:26:01 2017 +0000

----------------------------------------------------------------------
 docs/build/html/index.html                      |    2 +-
 docs/build/html/topics/impala_adls.html         |    9 +-
 docs/build/html/topics/impala_alter_table.html  |   71 +-
 docs/build/html/topics/impala_array.html        |    2 +-
 .../html/topics/impala_buffer_pool_limit.html   |   71 +
 .../build/html/topics/impala_compute_stats.html |   32 +-
 .../html/topics/impala_config_options.html      |    5 +-
 docs/build/html/topics/impala_connecting.html   |    9 +-
 docs/build/html/topics/impala_create_table.html |   28 +-
 .../html/topics/impala_datetime_functions.html  |  310 +++-
 .../impala_default_spillable_buffer_size.html   |   87 ++
 .../impala_exec_single_node_rows_threshold.html |    2 +-
 docs/build/html/topics/impala_fixed_issues.html | 1452 +++++++++---------
 docs/build/html/topics/impala_hbase.html        |    9 +
 docs/build/html/topics/impala_hints.html        |   10 +-
 .../topics/impala_incompatible_changes.html     |  144 +-
 docs/build/html/topics/impala_joins.html        |    2 +-
 docs/build/html/topics/impala_known_issues.html |  290 ++--
 docs/build/html/topics/impala_kudu.html         |    8 +
 docs/build/html/topics/impala_logging.html      |    3 +-
 docs/build/html/topics/impala_map.html          |    2 +-
 .../html/topics/impala_math_functions.html      |  165 +-
 docs/build/html/topics/impala_max_row_size.html |  221 +++
 .../impala_min_spillable_buffer_size.html       |   87 ++
 docs/build/html/topics/impala_new_features.html |  135 +-
 docs/build/html/topics/impala_partitioning.html |  148 ++
 docs/build/html/topics/impala_perf_joins.html   |   21 +-
 docs/build/html/topics/impala_perf_stats.html   |   40 +-
 .../build/html/topics/impala_query_options.html |    4 +-
 .../html/topics/impala_reserved_words.html      |    2 +-
 docs/build/html/topics/impala_scalability.html  |  259 +++-
 docs/build/html/topics/impala_select.html       |   19 +-
 .../html/topics/impala_shell_commands.html      |   24 +
 .../topics/impala_shell_running_commands.html   |   69 +-
 docs/build/html/topics/impala_ssl.html          |   71 +
 .../html/topics/impala_string_functions.html    |  270 ++++
 docs/build/html/topics/impala_struct.html       |    2 +-
 docs/build/html/topics/impala_subqueries.html   |   16 +
 docs/build/html/topics/impala_tablesample.html  |  554 +++++++
 docs/build/html/topics/impala_upgrading.html    |    4 +-
 docs/build/html/topics/impala_views.html        |   16 +
 docs/build/impala-2.10.pdf                      |  Bin 0 -> 3847517 bytes
 impala-docs.html                                |   17 +-
 43 files changed, 3572 insertions(+), 1120 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/index.html
----------------------------------------------------------------------
diff --git a/docs/build/html/index.html b/docs/build/html/index.html
index abf79ec..829524c 100644
--- a/docs/build/html/index.html
+++ b/docs/build/html/index.html
@@ -1,3 +1,3 @@
 <!DOCTYPE html
   SYSTEM "about:legacy-compat">
-<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="map"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="impala"><link rel="stylesheet" type="text/css" href="commonltr.css"><title>Apache Impala (incubating) Guide</title></head><body id="impala"><h1 class="title topictitle1">Apache Impala (incubating) Guide</h1><nav><ul class="map"><li class="topicref"><a href="topics/impala_intro.html">Introducing Apache Impala (incubating)</a></li><li class="topicref"><a href="topics/impala_concepts.html">Concepts and Architecture</a><ul><li class="topicref"><a href="topics/impala_components.html">Components</a></li><li class="topicref"><a href="topics/impala_development.html">Developing Applications</a></li><li class="topicref"><a href="topics/impala_hadoop.html">Role in the 
 Hadoop Ecosystem</a></li></ul></li><li class="topicref"><a href="topics/impala_planning.html">Deployment Planning</a><ul><li class="topicref"><a href="topics/impala_prereqs.html#prereqs">Requirements</a></li><li class="topicref"><a href="topics/impala_cluster_sizing.html">Cluster Sizing</a></li><li class="topicref"><a href="topics/impala_schema_design.html">Designing Schemas</a></li></ul></li><li class="topicref"><a href="topics/impala_install.html#install">Installing Impala</a></li><li class="topicref"><a href="topics/impala_config.html">Managing Impala</a><ul><li class="topicref"><a href="topics/impala_config_performance.html">Post-Installation Configuration for Impala</a></li><li class="topicref"><a href="topics/impala_odbc.html">Configuring Impala to Work with ODBC</a></li><li class="topicref"><a href="topics/impala_jdbc.html">Configuring Impala to Work with JDBC</a></li></ul></li><li class="topicref"><a href="topics/impala_upgrading.html">Upgrading Impala</a></li><li class="top
 icref"><a href="topics/impala_processes.html">Starting Impala</a><ul><li class="topicref"><a href="topics/impala_config_options.html">Modifying Impala Startup Options</a></li></ul></li><li class="topicref"><a href="topics/impala_tutorial.html">Tutorials</a></li><li class="topicref"><a href="topics/impala_admin.html">Administration</a><ul><li class="topicref"><a href="topics/impala_admission.html">Admission Control and Query Queuing</a></li><li class="topicref"><a href="topics/impala_resource_management.html">Resource Management for Impala</a></li><li class="topicref"><a href="topics/impala_timeouts.html">Setting Timeouts</a></li><li class="topicref"><a href="topics/impala_proxy.html">Load-Balancing Proxy for HA</a></li><li class="topicref"><a href="topics/impala_disk_space.html">Managing Disk Space</a></li></ul></li><li class="topicref"><a href="topics/impala_security.html">Impala Security</a><ul><li class="topicref"><a href="topics/impala_security_guidelines.html">Security Guidelin
 es for Impala</a></li><li class="topicref"><a href="topics/impala_security_files.html">Securing Impala Data and Log Files</a></li><li class="topicref"><a href="topics/impala_security_install.html">Installation Considerations for Impala Security</a></li><li class="topicref"><a href="topics/impala_security_metastore.html">Securing the Hive Metastore Database</a></li><li class="topicref"><a href="topics/impala_security_webui.html">Securing the Impala Web User Interface</a></li><li class="topicref"><a href="topics/impala_ssl.html">Configuring TLS/SSL for Impala</a></li><li class="topicref"><a href="topics/impala_authorization.html">Enabling Sentry Authorization for Impala</a></li><li class="topicref"><a href="topics/impala_authentication.html">Impala Authentication</a><ul><li class="topicref"><a href="topics/impala_kerberos.html">Enabling Kerberos Authentication for Impala</a></li><li class="topicref"><a href="topics/impala_ldap.html">Enabling LDAP Authentication for Impala</a></li><li 
 class="topicref"><a href="topics/impala_mixed_security.html">Using Multiple Authentication Methods with Impala</a></li><li class="topicref"><a href="topics/impala_delegation.html">Configuring Impala Delegation for Hue and BI Tools</a></li></ul></li><li class="topicref"><a href="topics/impala_auditing.html">Auditing</a></li><li class="topicref"><a href="topics/impala_lineage.html">Viewing Lineage Info</a></li></ul></li><li class="topicref"><a href="topics/impala_langref.html">SQL Reference</a><ul><li class="topicref"><a href="topics/impala_comments.html">Comments</a></li><li class="topicref"><a href="topics/impala_datatypes.html">Data Types</a><ul><li class="topicref"><a href="topics/impala_array.html">ARRAY Complex Type (Impala 2.3 or higher only)</a></li><li class="topicref"><a href="topics/impala_bigint.html">BIGINT</a></li><li class="topicref"><a href="topics/impala_boolean.html">BOOLEAN</a></li><li class="topicref"><a href="topics/impala_char.html">CHAR</a></li><li class="topicr
 ef"><a href="topics/impala_decimal.html">DECIMAL</a></li><li class="topicref"><a href="topics/impala_double.html">DOUBLE</a></li><li class="topicref"><a href="topics/impala_float.html">FLOAT</a></li><li class="topicref"><a href="topics/impala_int.html">INT</a></li><li class="topicref"><a href="topics/impala_map.html">MAP Complex Type (Impala 2.3 or higher only)</a></li><li class="topicref"><a href="topics/impala_real.html">REAL</a></li><li class="topicref"><a href="topics/impala_smallint.html">SMALLINT</a></li><li class="topicref"><a href="topics/impala_string.html">STRING</a></li><li class="topicref"><a href="topics/impala_struct.html">STRUCT Complex Type (Impala 2.3 or higher only)</a></li><li class="topicref"><a href="topics/impala_timestamp.html">TIMESTAMP</a></li><li class="topicref"><a href="topics/impala_tinyint.html">TINYINT</a></li><li class="topicref"><a href="topics/impala_varchar.html">VARCHAR</a></li><li class="topicref"><a href="topics/impala_complex_types.html">Comple
 x Types (Impala 2.3 or higher only)</a></li></ul></li><li class="topicref"><a href="topics/impala_literals.html">Literals</a></li><li class="topicref"><a href="topics/impala_operators.html">SQL Operators</a></li><li class="topicref"><a href="topics/impala_schema_objects.html">Schema Objects and Object Names</a><ul><li class="topicref"><a href="topics/impala_aliases.html">Aliases</a></li><li class="topicref"><a href="topics/impala_databases.html">Databases</a></li><li class="topicref"><a href="topics/impala_functions_overview.html">Functions</a></li><li class="topicref"><a href="topics/impala_identifiers.html">Identifiers</a></li><li class="topicref"><a href="topics/impala_tables.html">Tables</a></li><li class="topicref"><a href="topics/impala_views.html">Views</a></li></ul></li><li class="topicref"><a href="topics/impala_langref_sql.html">SQL Statements</a><ul><li class="topicref"><a href="topics/impala_ddl.html">DDL Statements</a></li><li class="topicref"><a href="topics/impala_dml
 .html">DML Statements</a></li><li class="topicref"><a href="topics/impala_alter_table.html">ALTER TABLE</a></li><li class="topicref"><a href="topics/impala_alter_view.html">ALTER VIEW</a></li><li class="topicref"><a href="topics/impala_compute_stats.html">COMPUTE STATS</a></li><li class="topicref"><a href="topics/impala_create_database.html">CREATE DATABASE</a></li><li class="topicref"><a href="topics/impala_create_function.html">CREATE FUNCTION</a></li><li class="topicref"><a href="topics/impala_create_role.html">CREATE ROLE</a></li><li class="topicref"><a href="topics/impala_create_table.html">CREATE TABLE</a></li><li class="topicref"><a href="topics/impala_create_view.html">CREATE VIEW</a></li><li class="topicref"><a href="topics/impala_delete.html">DELETE</a></li><li class="topicref"><a href="topics/impala_describe.html">DESCRIBE</a></li><li class="topicref"><a href="topics/impala_drop_database.html">DROP DATABASE</a></li><li class="topicref"><a href="topics/impala_drop_function
 .html">DROP FUNCTION</a></li><li class="topicref"><a href="topics/impala_drop_role.html">DROP ROLE</a></li><li class="topicref"><a href="topics/impala_drop_stats.html">DROP STATS</a></li><li class="topicref"><a href="topics/impala_drop_table.html">DROP TABLE</a></li><li class="topicref"><a href="topics/impala_drop_view.html">DROP VIEW</a></li><li class="topicref"><a href="topics/impala_explain.html">EXPLAIN</a></li><li class="topicref"><a href="topics/impala_grant.html">GRANT</a></li><li class="topicref"><a href="topics/impala_insert.html">INSERT</a></li><li class="topicref"><a href="topics/impala_invalidate_metadata.html">INVALIDATE METADATA</a></li><li class="topicref"><a href="topics/impala_load_data.html">LOAD DATA</a></li><li class="topicref"><a href="topics/impala_refresh.html">REFRESH</a></li><li class="topicref"><a href="topics/impala_revoke.html">REVOKE</a></li><li class="topicref"><a href="topics/impala_select.html">SELECT</a><ul><li class="topicref"><a href="topics/impala
 _joins.html">Joins</a></li><li class="topicref"><a href="topics/impala_order_by.html">ORDER BY Clause</a></li><li class="topicref"><a href="topics/impala_group_by.html">GROUP BY Clause</a></li><li class="topicref"><a href="topics/impala_having.html">HAVING Clause</a></li><li class="topicref"><a href="topics/impala_limit.html">LIMIT Clause</a></li><li class="topicref"><a href="topics/impala_offset.html">OFFSET Clause</a></li><li class="topicref"><a href="topics/impala_union.html">UNION Clause</a></li><li class="topicref"><a href="topics/impala_subqueries.html">Subqueries</a></li><li class="topicref"><a href="topics/impala_with.html">WITH Clause</a></li><li class="topicref"><a href="topics/impala_distinct.html">DISTINCT Operator</a></li><li class="topicref"><a href="topics/impala_hints.html">Hints</a></li></ul></li><li class="topicref"><a href="topics/impala_set.html">SET</a><ul><li class="topicref"><a href="topics/impala_query_options.html">Query Options for the SET Statement</a><ul>
 <li class="topicref"><a href="topics/impala_abort_on_default_limit_exceeded.html">ABORT_ON_DEFAULT_LIMIT_EXCEEDED</a></li><li class="topicref"><a href="topics/impala_abort_on_error.html">ABORT_ON_ERROR</a></li><li class="topicref"><a href="topics/impala_allow_unsupported_formats.html">ALLOW_UNSUPPORTED_FORMATS</a></li><li class="topicref"><a href="topics/impala_appx_count_distinct.html">APPX_COUNT_DISTINCT</a></li><li class="topicref"><a href="topics/impala_batch_size.html">BATCH_SIZE</a></li><li class="topicref"><a href="topics/impala_compression_codec.html">COMPRESSION_CODEC</a></li><li class="topicref"><a href="topics/impala_debug_action.html">DEBUG_ACTION</a></li><li class="topicref"><a href="topics/impala_default_join_distribution_mode.html">DEFAULT_JOIN_DISTRIBUTION_MODE</a></li><li class="topicref"><a href="topics/impala_default_order_by_limit.html">DEFAULT_ORDER_BY_LIMIT</a></li><li class="topicref"><a href="topics/impala_disable_codegen.html">DISABLE_CODEGEN</a></li><li cla
 ss="topicref"><a href="topics/impala_decimal_v2.html">DECIMAL_V2</a></li><li class="topicref"><a href="topics/impala_disable_row_runtime_filtering.html">DISABLE_ROW_RUNTIME_FILTERING</a></li><li class="topicref"><a href="topics/impala_disable_streaming_preaggregations.html">DISABLE_STREAMING_PREAGGREGATIONS</a></li><li class="topicref"><a href="topics/impala_disable_unsafe_spills.html">DISABLE_UNSAFE_SPILLS</a></li><li class="topicref"><a href="topics/impala_exec_single_node_rows_threshold.html">EXEC_SINGLE_NODE_ROWS_THRESHOLD</a></li><li class="topicref"><a href="topics/impala_explain_level.html">EXPLAIN_LEVEL</a></li><li class="topicref"><a href="topics/impala_hbase_cache_blocks.html">HBASE_CACHE_BLOCKS</a></li><li class="topicref"><a href="topics/impala_hbase_caching.html">HBASE_CACHING</a></li><li class="topicref"><a href="topics/impala_live_progress.html">LIVE_PROGRESS</a></li><li class="topicref"><a href="topics/impala_live_summary.html">LIVE_SUMMARY</a></li><li class="topicre
 f"><a href="topics/impala_max_errors.html">MAX_ERRORS</a></li><li class="topicref"><a href="topics/impala_max_io_buffers.html">MAX_IO_BUFFERS</a></li><li class="topicref"><a href="topics/impala_max_scan_range_length.html">MAX_SCAN_RANGE_LENGTH</a></li><li class="topicref"><a href="topics/impala_max_num_runtime_filters.html">MAX_NUM_RUNTIME_FILTERS</a></li><li class="topicref"><a href="topics/impala_mem_limit.html">MEM_LIMIT</a></li><li class="topicref"><a href="topics/impala_mt_dop.html">MT_DOP</a></li><li class="topicref"><a href="topics/impala_num_nodes.html">NUM_NODES</a></li><li class="topicref"><a href="topics/impala_num_scanner_threads.html">NUM_SCANNER_THREADS</a></li><li class="topicref"><a href="topics/impala_optimize_partition_key_scans.html">OPTIMIZE_PARTITION_KEY_SCANS</a></li><li class="topicref"><a href="topics/impala_parquet_compression_codec.html">PARQUET_COMPRESSION_CODEC</a></li><li class="topicref"><a href="topics/impala_parquet_annotate_strings_utf8.html">PARQUET
 _ANNOTATE_STRINGS_UTF8</a></li><li class="topicref"><a href="topics/impala_parquet_fallback_schema_resolution.html">PARQUET_FALLBACK_SCHEMA_RESOLUTION</a></li><li class="topicref"><a href="topics/impala_parquet_file_size.html">PARQUET_FILE_SIZE</a></li><li class="topicref"><a href="topics/impala_prefetch_mode.html">PREFETCH_MODE</a></li><li class="topicref"><a href="topics/impala_query_timeout_s.html">QUERY_TIMEOUT_S</a></li><li class="topicref"><a href="topics/impala_request_pool.html">REQUEST_POOL</a></li><li class="topicref"><a href="topics/impala_replica_preference.html">REPLICA_PREFERENCE</a></li><li class="topicref"><a href="topics/impala_reservation_request_timeout.html">RESERVATION_REQUEST_TIMEOUT</a></li><li class="topicref"><a href="topics/impala_runtime_bloom_filter_size.html">RUNTIME_BLOOM_FILTER_SIZE</a></li><li class="topicref"><a href="topics/impala_runtime_filter_max_size.html">RUNTIME_FILTER_MAX_SIZE</a></li><li class="topicref"><a href="topics/impala_runtime_filter
 _min_size.html">RUNTIME_FILTER_MIN_SIZE</a></li><li class="topicref"><a href="topics/impala_runtime_filter_mode.html">RUNTIME_FILTER_MODE</a></li><li class="topicref"><a href="topics/impala_runtime_filter_wait_time_ms.html">RUNTIME_FILTER_WAIT_TIME_MS</a></li><li class="topicref"><a href="topics/impala_s3_skip_insert_staging.html">S3_SKIP_INSERT_STAGING</a></li><li class="topicref"><a href="topics/impala_scan_node_codegen_threshold.html">SCAN_NODE_CODEGEN_THRESHOLD</a></li><li class="topicref"><a href="topics/impala_scratch_limit.html">SCRATCH_LIMIT</a></li><li class="topicref"><a href="topics/impala_schedule_random_replica.html">SCHEDULE_RANDOM_REPLICA</a></li><li class="topicref"><a href="topics/impala_support_start_over.html">SUPPORT_START_OVER</a></li><li class="topicref"><a href="topics/impala_sync_ddl.html">SYNC_DDL</a></li><li class="topicref"><a href="topics/impala_v_cpu_cores.html">V_CPU_CORES</a></li></ul></li></ul></li><li class="topicref"><a href="topics/impala_show.html
 ">SHOW</a></li><li class="topicref"><a href="topics/impala_truncate_table.html">TRUNCATE TABLE</a></li><li class="topicref"><a href="topics/impala_update.html">UPDATE</a></li><li class="topicref"><a href="topics/impala_upsert.html">UPSERT</a></li><li class="topicref"><a href="topics/impala_use.html">USE</a></li></ul></li><li class="topicref"><a href="topics/impala_functions.html">Built-In Functions</a><ul><li class="topicref"><a href="topics/impala_math_functions.html">Mathematical Functions</a></li><li class="topicref"><a href="topics/impala_bit_functions.html">Bit Functions</a></li><li class="topicref"><a href="topics/impala_conversion_functions.html">Type Conversion Functions</a></li><li class="topicref"><a href="topics/impala_datetime_functions.html">Date and Time Functions</a></li><li class="topicref"><a href="topics/impala_conditional_functions.html">Conditional Functions</a></li><li class="topicref"><a href="topics/impala_string_functions.html">String Functions</a></li><li cl
 ass="topicref"><a href="topics/impala_misc_functions.html">Miscellaneous Functions</a></li><li class="topicref"><a href="topics/impala_aggregate_functions.html">Aggregate Functions</a><ul><li class="topicref"><a href="topics/impala_appx_median.html">APPX_MEDIAN</a></li><li class="topicref"><a href="topics/impala_avg.html">AVG</a></li><li class="topicref"><a href="topics/impala_count.html">COUNT</a></li><li class="topicref"><a href="topics/impala_group_concat.html">GROUP_CONCAT</a></li><li class="topicref"><a href="topics/impala_max.html">MAX</a></li><li class="topicref"><a href="topics/impala_min.html">MIN</a></li><li class="topicref"><a href="topics/impala_ndv.html">NDV</a></li><li class="topicref"><a href="topics/impala_stddev.html">STDDEV, STDDEV_SAMP, STDDEV_POP</a></li><li class="topicref"><a href="topics/impala_sum.html">SUM</a></li><li class="topicref"><a href="topics/impala_variance.html">VARIANCE, VARIANCE_SAMP, VARIANCE_POP, VAR_SAMP, VAR_POP</a></li></ul></li><li class="t
 opicref"><a href="topics/impala_analytic_functions.html">Analytic Functions</a></li><li class="topicref"><a href="topics/impala_udf.html">Impala User-Defined Functions (UDFs)</a></li></ul></li><li class="topicref"><a href="topics/impala_langref_unsupported.html">SQL Differences Between Impala and Hive</a></li><li class="topicref"><a href="topics/impala_porting.html">Porting SQL</a></li></ul></li><li class="topicref"><a href="topics/impala_impala_shell.html">The Impala Shell</a><ul><li class="topicref"><a href="topics/impala_shell_options.html">Configuration Options</a></li><li class="topicref"><a href="topics/impala_connecting.html">Connecting to impalad</a></li><li class="topicref"><a href="topics/impala_shell_running_commands.html">Running Commands and SQL Statements</a></li><li class="topicref"><a href="topics/impala_shell_commands.html">Command Reference</a></li></ul></li><li class="topicref"><a href="topics/impala_performance.html">Performance Tuning</a><ul><li class="topicref"
 ><a href="topics/impala_perf_cookbook.html">Performance Best Practices</a></li><li class="topicref"><a href="topics/impala_perf_joins.html">Join Performance</a></li><li class="topicref"><a href="topics/impala_perf_stats.html">Table and Column Statistics</a></li><li class="topicref"><a href="topics/impala_perf_benchmarking.html">Benchmarking</a></li><li class="topicref"><a href="topics/impala_perf_resources.html">Controlling Resource Usage</a></li><li class="topicref"><a href="topics/impala_runtime_filtering.html">Runtime Filtering</a></li><li class="topicref"><a href="topics/impala_perf_hdfs_caching.html">HDFS Caching</a></li><li class="topicref"><a href="topics/impala_perf_testing.html">Testing Impala Performance</a></li><li class="topicref"><a href="topics/impala_explain_plan.html">EXPLAIN Plans and Query Profiles</a></li><li class="topicref"><a href="topics/impala_perf_skew.html">HDFS Block Skew</a></li></ul></li><li class="topicref"><a href="topics/impala_scalability.html">Scala
 bility Considerations</a></li><li class="topicref"><a href="topics/impala_partitioning.html">Partitioning</a></li><li class="topicref"><a href="topics/impala_file_formats.html">File Formats</a><ul><li class="topicref"><a href="topics/impala_txtfile.html">Text Data Files</a></li><li class="topicref"><a href="topics/impala_parquet.html">Parquet Data Files</a></li><li class="topicref"><a href="topics/impala_avro.html">Avro Data Files</a></li><li class="topicref"><a href="topics/impala_rcfile.html">RCFile Data Files</a></li><li class="topicref"><a href="topics/impala_seqfile.html">SequenceFile Data Files</a></li></ul></li><li class="topicref"><a href="topics/impala_kudu.html">Using Impala to Query Kudu Tables</a></li><li class="topicref"><a href="topics/impala_hbase.html">HBase Tables</a></li><li class="topicref"><a href="topics/impala_s3.html">S3 Tables</a></li><li class="topicref"><a href="topics/impala_adls.html">ADLS Tables</a></li><li class="topicref"><a href="topics/impala_isilon.
 html">Isilon Storage</a></li><li class="topicref"><a href="topics/impala_logging.html">Logging</a></li><li class="topicref"><a href="topics/impala_troubleshooting.html">Troubleshooting Impala</a><ul><li class="topicref"><a href="topics/impala_webui.html">Web User Interface</a></li><li class="topicref"><a href="topics/impala_breakpad.html">Breakpad Minidumps</a></li></ul></li><li class="topicref"><a href="topics/impala_ports.html">Ports Used by Impala</a></li><li class="topicref"><a href="topics/impala_reserved_words.html">Impala Reserved Words</a></li><li class="topicref"><a href="topics/impala_faq.html">Impala Frequently Asked Questions</a></li><li class="topicref"><a href="topics/impala_release_notes.html">Impala Release Notes</a><ul><li class="topicref"><a href="topics/impala_relnotes.html">Impala Release Notes</a></li><li class="topicref"><a href="topics/impala_new_features.html">New Features in Apache Impala (incubating)</a></li><li class="topicref"><a href="topics/impala_incom
 patible_changes.html">Incompatible Changes and Limitations in Apache Impala (incubating)</a></li><li class="topicref"><a href="topics/impala_known_issues.html">Known Issues and Workarounds in Impala</a></li><li class="topicref"><a href="topics/impala_fixed_issues.html">Fixed Issues in Apache Impala (incubating)</a></li></ul></li></ul></nav></body></html>
\ No newline at end of file
+<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="map"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="impala"><link rel="stylesheet" type="text/css" href="commonltr.css"><title>Apache Impala (incubating) Guide</title></head><body id="impala"><h1 class="title topictitle1">Apache Impala (incubating) Guide</h1><nav><ul class="map"><li class="topicref"><a href="topics/impala_intro.html">Introducing Apache Impala (incubating)</a></li><li class="topicref"><a href="topics/impala_concepts.html">Concepts and Architecture</a><ul><li class="topicref"><a href="topics/impala_components.html">Components</a></li><li class="topicref"><a href="topics/impala_development.html">Developing Applications</a></li><li class="topicref"><a href="topics/impala_hadoop.html">Role in the 
 Hadoop Ecosystem</a></li></ul></li><li class="topicref"><a href="topics/impala_planning.html">Deployment Planning</a><ul><li class="topicref"><a href="topics/impala_prereqs.html#prereqs">Requirements</a></li><li class="topicref"><a href="topics/impala_cluster_sizing.html">Cluster Sizing</a></li><li class="topicref"><a href="topics/impala_schema_design.html">Designing Schemas</a></li></ul></li><li class="topicref"><a href="topics/impala_install.html#install">Installing Impala</a></li><li class="topicref"><a href="topics/impala_config.html">Managing Impala</a><ul><li class="topicref"><a href="topics/impala_config_performance.html">Post-Installation Configuration for Impala</a></li><li class="topicref"><a href="topics/impala_odbc.html">Configuring Impala to Work with ODBC</a></li><li class="topicref"><a href="topics/impala_jdbc.html">Configuring Impala to Work with JDBC</a></li></ul></li><li class="topicref"><a href="topics/impala_upgrading.html">Upgrading Impala</a></li><li class="top
 icref"><a href="topics/impala_processes.html">Starting Impala</a><ul><li class="topicref"><a href="topics/impala_config_options.html">Modifying Impala Startup Options</a></li></ul></li><li class="topicref"><a href="topics/impala_tutorial.html">Tutorials</a></li><li class="topicref"><a href="topics/impala_admin.html">Administration</a><ul><li class="topicref"><a href="topics/impala_admission.html">Admission Control and Query Queuing</a></li><li class="topicref"><a href="topics/impala_resource_management.html">Resource Management for Impala</a></li><li class="topicref"><a href="topics/impala_timeouts.html">Setting Timeouts</a></li><li class="topicref"><a href="topics/impala_proxy.html">Load-Balancing Proxy for HA</a></li><li class="topicref"><a href="topics/impala_disk_space.html">Managing Disk Space</a></li></ul></li><li class="topicref"><a href="topics/impala_security.html">Impala Security</a><ul><li class="topicref"><a href="topics/impala_security_guidelines.html">Security Guidelin
 es for Impala</a></li><li class="topicref"><a href="topics/impala_security_files.html">Securing Impala Data and Log Files</a></li><li class="topicref"><a href="topics/impala_security_install.html">Installation Considerations for Impala Security</a></li><li class="topicref"><a href="topics/impala_security_metastore.html">Securing the Hive Metastore Database</a></li><li class="topicref"><a href="topics/impala_security_webui.html">Securing the Impala Web User Interface</a></li><li class="topicref"><a href="topics/impala_ssl.html">Configuring TLS/SSL for Impala</a></li><li class="topicref"><a href="topics/impala_authorization.html">Enabling Sentry Authorization for Impala</a></li><li class="topicref"><a href="topics/impala_authentication.html">Impala Authentication</a><ul><li class="topicref"><a href="topics/impala_kerberos.html">Enabling Kerberos Authentication for Impala</a></li><li class="topicref"><a href="topics/impala_ldap.html">Enabling LDAP Authentication for Impala</a></li><li 
 class="topicref"><a href="topics/impala_mixed_security.html">Using Multiple Authentication Methods with Impala</a></li><li class="topicref"><a href="topics/impala_delegation.html">Configuring Impala Delegation for Hue and BI Tools</a></li></ul></li><li class="topicref"><a href="topics/impala_auditing.html">Auditing</a></li><li class="topicref"><a href="topics/impala_lineage.html">Viewing Lineage Info</a></li></ul></li><li class="topicref"><a href="topics/impala_langref.html">SQL Reference</a><ul><li class="topicref"><a href="topics/impala_comments.html">Comments</a></li><li class="topicref"><a href="topics/impala_datatypes.html">Data Types</a><ul><li class="topicref"><a href="topics/impala_array.html">ARRAY Complex Type (Impala 2.3 or higher only)</a></li><li class="topicref"><a href="topics/impala_bigint.html">BIGINT</a></li><li class="topicref"><a href="topics/impala_boolean.html">BOOLEAN</a></li><li class="topicref"><a href="topics/impala_char.html">CHAR</a></li><li class="topicr
 ef"><a href="topics/impala_decimal.html">DECIMAL</a></li><li class="topicref"><a href="topics/impala_double.html">DOUBLE</a></li><li class="topicref"><a href="topics/impala_float.html">FLOAT</a></li><li class="topicref"><a href="topics/impala_int.html">INT</a></li><li class="topicref"><a href="topics/impala_map.html">MAP Complex Type (Impala 2.3 or higher only)</a></li><li class="topicref"><a href="topics/impala_real.html">REAL</a></li><li class="topicref"><a href="topics/impala_smallint.html">SMALLINT</a></li><li class="topicref"><a href="topics/impala_string.html">STRING</a></li><li class="topicref"><a href="topics/impala_struct.html">STRUCT Complex Type (Impala 2.3 or higher only)</a></li><li class="topicref"><a href="topics/impala_timestamp.html">TIMESTAMP</a></li><li class="topicref"><a href="topics/impala_tinyint.html">TINYINT</a></li><li class="topicref"><a href="topics/impala_varchar.html">VARCHAR</a></li><li class="topicref"><a href="topics/impala_complex_types.html">Comple
 x Types (Impala 2.3 or higher only)</a></li></ul></li><li class="topicref"><a href="topics/impala_literals.html">Literals</a></li><li class="topicref"><a href="topics/impala_operators.html">SQL Operators</a></li><li class="topicref"><a href="topics/impala_schema_objects.html">Schema Objects and Object Names</a><ul><li class="topicref"><a href="topics/impala_aliases.html">Aliases</a></li><li class="topicref"><a href="topics/impala_databases.html">Databases</a></li><li class="topicref"><a href="topics/impala_functions_overview.html">Functions</a></li><li class="topicref"><a href="topics/impala_identifiers.html">Identifiers</a></li><li class="topicref"><a href="topics/impala_tables.html">Tables</a></li><li class="topicref"><a href="topics/impala_views.html">Views</a></li></ul></li><li class="topicref"><a href="topics/impala_langref_sql.html">SQL Statements</a><ul><li class="topicref"><a href="topics/impala_ddl.html">DDL Statements</a></li><li class="topicref"><a href="topics/impala_dml
 .html">DML Statements</a></li><li class="topicref"><a href="topics/impala_alter_table.html">ALTER TABLE</a></li><li class="topicref"><a href="topics/impala_alter_view.html">ALTER VIEW</a></li><li class="topicref"><a href="topics/impala_compute_stats.html">COMPUTE STATS</a></li><li class="topicref"><a href="topics/impala_create_database.html">CREATE DATABASE</a></li><li class="topicref"><a href="topics/impala_create_function.html">CREATE FUNCTION</a></li><li class="topicref"><a href="topics/impala_create_role.html">CREATE ROLE</a></li><li class="topicref"><a href="topics/impala_create_table.html">CREATE TABLE</a></li><li class="topicref"><a href="topics/impala_create_view.html">CREATE VIEW</a></li><li class="topicref"><a href="topics/impala_delete.html">DELETE</a></li><li class="topicref"><a href="topics/impala_describe.html">DESCRIBE</a></li><li class="topicref"><a href="topics/impala_drop_database.html">DROP DATABASE</a></li><li class="topicref"><a href="topics/impala_drop_function
 .html">DROP FUNCTION</a></li><li class="topicref"><a href="topics/impala_drop_role.html">DROP ROLE</a></li><li class="topicref"><a href="topics/impala_drop_stats.html">DROP STATS</a></li><li class="topicref"><a href="topics/impala_drop_table.html">DROP TABLE</a></li><li class="topicref"><a href="topics/impala_drop_view.html">DROP VIEW</a></li><li class="topicref"><a href="topics/impala_explain.html">EXPLAIN</a></li><li class="topicref"><a href="topics/impala_grant.html">GRANT</a></li><li class="topicref"><a href="topics/impala_insert.html">INSERT</a></li><li class="topicref"><a href="topics/impala_invalidate_metadata.html">INVALIDATE METADATA</a></li><li class="topicref"><a href="topics/impala_load_data.html">LOAD DATA</a></li><li class="topicref"><a href="topics/impala_refresh.html">REFRESH</a></li><li class="topicref"><a href="topics/impala_revoke.html">REVOKE</a></li><li class="topicref"><a href="topics/impala_select.html">SELECT</a><ul><li class="topicref"><a href="topics/impala
 _joins.html">Joins</a></li><li class="topicref"><a href="topics/impala_order_by.html">ORDER BY Clause</a></li><li class="topicref"><a href="topics/impala_group_by.html">GROUP BY Clause</a></li><li class="topicref"><a href="topics/impala_having.html">HAVING Clause</a></li><li class="topicref"><a href="topics/impala_limit.html">LIMIT Clause</a></li><li class="topicref"><a href="topics/impala_offset.html">OFFSET Clause</a></li><li class="topicref"><a href="topics/impala_union.html">UNION Clause</a></li><li class="topicref"><a href="topics/impala_subqueries.html">Subqueries</a></li><li class="topicref"><a href="topics/impala_tablesample.html">TABLESAMPLE Clause</a></li><li class="topicref"><a href="topics/impala_with.html">WITH Clause</a></li><li class="topicref"><a href="topics/impala_distinct.html">DISTINCT Operator</a></li><li class="topicref"><a href="topics/impala_hints.html">Hints</a></li></ul></li><li class="topicref"><a href="topics/impala_set.html">SET</a><ul><li class="topicre
 f"><a href="topics/impala_query_options.html">Query Options for the SET Statement</a><ul><li class="topicref"><a href="topics/impala_abort_on_default_limit_exceeded.html">ABORT_ON_DEFAULT_LIMIT_EXCEEDED</a></li><li class="topicref"><a href="topics/impala_abort_on_error.html">ABORT_ON_ERROR</a></li><li class="topicref"><a href="topics/impala_allow_unsupported_formats.html">ALLOW_UNSUPPORTED_FORMATS</a></li><li class="topicref"><a href="topics/impala_appx_count_distinct.html">APPX_COUNT_DISTINCT</a></li><li class="topicref"><a href="topics/impala_batch_size.html">BATCH_SIZE</a></li><li class="topicref"><a href="topics/impala_buffer_pool_limit.html">BUFFER_POOL_LIMIT</a></li><li class="topicref"><a href="topics/impala_compression_codec.html">COMPRESSION_CODEC</a></li><li class="topicref"><a href="topics/impala_debug_action.html">DEBUG_ACTION</a></li><li class="topicref"><a href="topics/impala_decimal_v2.html">DECIMAL_V2</a></li><li class="topicref"><a href="topics/impala_default_join_d
 istribution_mode.html">DEFAULT_JOIN_DISTRIBUTION_MODE</a></li><li class="topicref"><a href="topics/impala_default_order_by_limit.html">DEFAULT_ORDER_BY_LIMIT</a></li><li class="topicref"><a href="topics/impala_default_spillable_buffer_size.html">DEFAULT_SPILLABLE_BUFFER_SIZE</a></li><li class="topicref"><a href="topics/impala_disable_codegen.html">DISABLE_CODEGEN</a></li><li class="topicref"><a href="topics/impala_disable_row_runtime_filtering.html">DISABLE_ROW_RUNTIME_FILTERING</a></li><li class="topicref"><a href="topics/impala_disable_streaming_preaggregations.html">DISABLE_STREAMING_PREAGGREGATIONS</a></li><li class="topicref"><a href="topics/impala_disable_unsafe_spills.html">DISABLE_UNSAFE_SPILLS</a></li><li class="topicref"><a href="topics/impala_exec_single_node_rows_threshold.html">EXEC_SINGLE_NODE_ROWS_THRESHOLD</a></li><li class="topicref"><a href="topics/impala_explain_level.html">EXPLAIN_LEVEL</a></li><li class="topicref"><a href="topics/impala_hbase_cache_blocks.html">
 HBASE_CACHE_BLOCKS</a></li><li class="topicref"><a href="topics/impala_hbase_caching.html">HBASE_CACHING</a></li><li class="topicref"><a href="topics/impala_live_progress.html">LIVE_PROGRESS</a></li><li class="topicref"><a href="topics/impala_live_summary.html">LIVE_SUMMARY</a></li><li class="topicref"><a href="topics/impala_max_errors.html">MAX_ERRORS</a></li><li class="topicref"><a href="topics/impala_max_io_buffers.html">MAX_IO_BUFFERS</a></li><li class="topicref"><a href="topics/impala_max_row_size.html">MAX_ROW_SIZE</a></li><li class="topicref"><a href="topics/impala_max_num_runtime_filters.html">MAX_NUM_RUNTIME_FILTERS</a></li><li class="topicref"><a href="topics/impala_max_scan_range_length.html">MAX_SCAN_RANGE_LENGTH</a></li><li class="topicref"><a href="topics/impala_mem_limit.html">MEM_LIMIT</a></li><li class="topicref"><a href="topics/impala_min_spillable_buffer_size.html">MIN_SPILLABLE_BUFFER_SIZE</a></li><li class="topicref"><a href="topics/impala_mt_dop.html">MT_DOP</a
 ></li><li class="topicref"><a href="topics/impala_num_nodes.html">NUM_NODES</a></li><li class="topicref"><a href="topics/impala_num_scanner_threads.html">NUM_SCANNER_THREADS</a></li><li class="topicref"><a href="topics/impala_optimize_partition_key_scans.html">OPTIMIZE_PARTITION_KEY_SCANS</a></li><li class="topicref"><a href="topics/impala_parquet_compression_codec.html">PARQUET_COMPRESSION_CODEC</a></li><li class="topicref"><a href="topics/impala_parquet_annotate_strings_utf8.html">PARQUET_ANNOTATE_STRINGS_UTF8</a></li><li class="topicref"><a href="topics/impala_parquet_fallback_schema_resolution.html">PARQUET_FALLBACK_SCHEMA_RESOLUTION</a></li><li class="topicref"><a href="topics/impala_parquet_file_size.html">PARQUET_FILE_SIZE</a></li><li class="topicref"><a href="topics/impala_prefetch_mode.html">PREFETCH_MODE</a></li><li class="topicref"><a href="topics/impala_query_timeout_s.html">QUERY_TIMEOUT_S</a></li><li class="topicref"><a href="topics/impala_request_pool.html">REQUEST_PO
 OL</a></li><li class="topicref"><a href="topics/impala_replica_preference.html">REPLICA_PREFERENCE</a></li><li class="topicref"><a href="topics/impala_reservation_request_timeout.html">RESERVATION_REQUEST_TIMEOUT</a></li><li class="topicref"><a href="topics/impala_runtime_bloom_filter_size.html">RUNTIME_BLOOM_FILTER_SIZE</a></li><li class="topicref"><a href="topics/impala_runtime_filter_max_size.html">RUNTIME_FILTER_MAX_SIZE</a></li><li class="topicref"><a href="topics/impala_runtime_filter_min_size.html">RUNTIME_FILTER_MIN_SIZE</a></li><li class="topicref"><a href="topics/impala_runtime_filter_mode.html">RUNTIME_FILTER_MODE</a></li><li class="topicref"><a href="topics/impala_runtime_filter_wait_time_ms.html">RUNTIME_FILTER_WAIT_TIME_MS</a></li><li class="topicref"><a href="topics/impala_s3_skip_insert_staging.html">S3_SKIP_INSERT_STAGING</a></li><li class="topicref"><a href="topics/impala_scan_node_codegen_threshold.html">SCAN_NODE_CODEGEN_THRESHOLD</a></li><li class="topicref"><a 
 href="topics/impala_schedule_random_replica.html">SCHEDULE_RANDOM_REPLICA</a></li><li class="topicref"><a href="topics/impala_scratch_limit.html">SCRATCH_LIMIT</a></li><li class="topicref"><a href="topics/impala_support_start_over.html">SUPPORT_START_OVER</a></li><li class="topicref"><a href="topics/impala_sync_ddl.html">SYNC_DDL</a></li><li class="topicref"><a href="topics/impala_v_cpu_cores.html">V_CPU_CORES</a></li></ul></li></ul></li><li class="topicref"><a href="topics/impala_show.html">SHOW</a></li><li class="topicref"><a href="topics/impala_truncate_table.html">TRUNCATE TABLE</a></li><li class="topicref"><a href="topics/impala_update.html">UPDATE</a></li><li class="topicref"><a href="topics/impala_upsert.html">UPSERT</a></li><li class="topicref"><a href="topics/impala_use.html">USE</a></li></ul></li><li class="topicref"><a href="topics/impala_functions.html">Built-In Functions</a><ul><li class="topicref"><a href="topics/impala_math_functions.html">Mathematical Functions</a></
 li><li class="topicref"><a href="topics/impala_bit_functions.html">Bit Functions</a></li><li class="topicref"><a href="topics/impala_conversion_functions.html">Type Conversion Functions</a></li><li class="topicref"><a href="topics/impala_datetime_functions.html">Date and Time Functions</a></li><li class="topicref"><a href="topics/impala_conditional_functions.html">Conditional Functions</a></li><li class="topicref"><a href="topics/impala_string_functions.html">String Functions</a></li><li class="topicref"><a href="topics/impala_misc_functions.html">Miscellaneous Functions</a></li><li class="topicref"><a href="topics/impala_aggregate_functions.html">Aggregate Functions</a><ul><li class="topicref"><a href="topics/impala_appx_median.html">APPX_MEDIAN</a></li><li class="topicref"><a href="topics/impala_avg.html">AVG</a></li><li class="topicref"><a href="topics/impala_count.html">COUNT</a></li><li class="topicref"><a href="topics/impala_group_concat.html">GROUP_CONCAT</a></li><li class="t
 opicref"><a href="topics/impala_max.html">MAX</a></li><li class="topicref"><a href="topics/impala_min.html">MIN</a></li><li class="topicref"><a href="topics/impala_ndv.html">NDV</a></li><li class="topicref"><a href="topics/impala_stddev.html">STDDEV, STDDEV_SAMP, STDDEV_POP</a></li><li class="topicref"><a href="topics/impala_sum.html">SUM</a></li><li class="topicref"><a href="topics/impala_variance.html">VARIANCE, VARIANCE_SAMP, VARIANCE_POP, VAR_SAMP, VAR_POP</a></li></ul></li><li class="topicref"><a href="topics/impala_analytic_functions.html">Analytic Functions</a></li><li class="topicref"><a href="topics/impala_udf.html">Impala User-Defined Functions (UDFs)</a></li></ul></li><li class="topicref"><a href="topics/impala_langref_unsupported.html">SQL Differences Between Impala and Hive</a></li><li class="topicref"><a href="topics/impala_porting.html">Porting SQL</a></li></ul></li><li class="topicref"><a href="topics/impala_impala_shell.html">The Impala Shell</a><ul><li class="topic
 ref"><a href="topics/impala_shell_options.html">Configuration Options</a></li><li class="topicref"><a href="topics/impala_connecting.html">Connecting to impalad</a></li><li class="topicref"><a href="topics/impala_shell_running_commands.html">Running Commands and SQL Statements</a></li><li class="topicref"><a href="topics/impala_shell_commands.html">Command Reference</a></li></ul></li><li class="topicref"><a href="topics/impala_performance.html">Performance Tuning</a><ul><li class="topicref"><a href="topics/impala_perf_cookbook.html">Performance Best Practices</a></li><li class="topicref"><a href="topics/impala_perf_joins.html">Join Performance</a></li><li class="topicref"><a href="topics/impala_perf_stats.html">Table and Column Statistics</a></li><li class="topicref"><a href="topics/impala_perf_benchmarking.html">Benchmarking</a></li><li class="topicref"><a href="topics/impala_perf_resources.html">Controlling Resource Usage</a></li><li class="topicref"><a href="topics/impala_runtime
 _filtering.html">Runtime Filtering</a></li><li class="topicref"><a href="topics/impala_perf_hdfs_caching.html">HDFS Caching</a></li><li class="topicref"><a href="topics/impala_perf_testing.html">Testing Impala Performance</a></li><li class="topicref"><a href="topics/impala_explain_plan.html">EXPLAIN Plans and Query Profiles</a></li><li class="topicref"><a href="topics/impala_perf_skew.html">HDFS Block Skew</a></li></ul></li><li class="topicref"><a href="topics/impala_scalability.html">Scalability Considerations</a></li><li class="topicref"><a href="topics/impala_partitioning.html">Partitioning</a></li><li class="topicref"><a href="topics/impala_file_formats.html">File Formats</a><ul><li class="topicref"><a href="topics/impala_txtfile.html">Text Data Files</a></li><li class="topicref"><a href="topics/impala_parquet.html">Parquet Data Files</a></li><li class="topicref"><a href="topics/impala_avro.html">Avro Data Files</a></li><li class="topicref"><a href="topics/impala_rcfile.html">RC
 File Data Files</a></li><li class="topicref"><a href="topics/impala_seqfile.html">SequenceFile Data Files</a></li></ul></li><li class="topicref"><a href="topics/impala_kudu.html">Using Impala to Query Kudu Tables</a></li><li class="topicref"><a href="topics/impala_hbase.html">HBase Tables</a></li><li class="topicref"><a href="topics/impala_s3.html">S3 Tables</a></li><li class="topicref"><a href="topics/impala_adls.html">ADLS Tables</a></li><li class="topicref"><a href="topics/impala_isilon.html">Isilon Storage</a></li><li class="topicref"><a href="topics/impala_logging.html">Logging</a></li><li class="topicref"><a href="topics/impala_troubleshooting.html">Troubleshooting Impala</a><ul><li class="topicref"><a href="topics/impala_webui.html">Web User Interface</a></li><li class="topicref"><a href="topics/impala_breakpad.html">Breakpad Minidumps</a></li></ul></li><li class="topicref"><a href="topics/impala_ports.html">Ports Used by Impala</a></li><li class="topicref"><a href="topics/im
 pala_reserved_words.html">Impala Reserved Words</a></li><li class="topicref"><a href="topics/impala_faq.html">Impala Frequently Asked Questions</a></li><li class="topicref"><a href="topics/impala_release_notes.html">Impala Release Notes</a><ul><li class="topicref"><a href="topics/impala_relnotes.html">Impala Release Notes</a></li><li class="topicref"><a href="topics/impala_new_features.html">New Features in Apache Impala (incubating)</a></li><li class="topicref"><a href="topics/impala_incompatible_changes.html">Incompatible Changes and Limitations in Apache Impala (incubating)</a></li><li class="topicref"><a href="topics/impala_known_issues.html">Known Issues and Workarounds in Impala</a></li><li class="topicref"><a href="topics/impala_fixed_issues.html">Fixed Issues in Apache Impala (incubating)</a></li></ul></li></ul></nav></body></html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_adls.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_adls.html b/docs/build/html/topics/impala_adls.html
index 2f10f7f..3a68e48 100644
--- a/docs/build/html/topics/impala_adls.html
+++ b/docs/build/html/topics/impala_adls.html
@@ -8,13 +8,6 @@
 
   <div class="body conbody">
 
-    <div class="note important note_important"><span class="note__title importanttitle">Important:</span> 
-        <p class="p">
-          Currently, the ADLS support in Impala is preliminary and not
-          fully tested. Do not use Impala with ADLS in a production environment.
-        </p>
-      </div>
-
     <p class="p">
       
       You can use Impala to query data residing on the Azure Data Lake Store (ADLS) filesystem.
@@ -52,7 +45,7 @@
         </li>
         <li class="li">
           <p class="p">
-            <a class="xref" href="https://hadoop.apache.org/docs/current2/hadoop-azure-datalake/index.html" target="_blank">Hadoop Azure Data Lake Support</a>
+            <a class="xref" href="https://hadoop.apache.org/docs/current/hadoop-azure-datalake/index.html" target="_blank">Hadoop Azure Data Lake Support</a>
           </p>
         </li>
       </ul>

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_alter_table.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_alter_table.html b/docs/build/html/topics/impala_alter_table.html
index 6d01d0e..c44b6a3 100644
--- a/docs/build/html/topics/impala_alter_table.html
+++ b/docs/build/html/topics/impala_alter_table.html
@@ -29,8 +29,20 @@
 ALTER TABLE <var class="keyword varname">name</var> ADD COLUMNS (<var class="keyword varname">col_spec</var>[, <var class="keyword varname">col_spec</var> ...])
 ALTER TABLE <var class="keyword varname">name</var> DROP [COLUMN] <var class="keyword varname">column_name</var>
 ALTER TABLE <var class="keyword varname">name</var> CHANGE <var class="keyword varname">column_name</var> <var class="keyword varname">new_name</var> <var class="keyword varname">new_type</var>
+
 ALTER TABLE <var class="keyword varname">name</var> REPLACE COLUMNS (<var class="keyword varname">col_spec</var>[, <var class="keyword varname">col_spec</var> ...])
 
+<span class="ph">-- Kudu tables only.
+ALTER TABLE <var class="keyword varname">name</var> ALTER [COLUMN] <var class="keyword varname">column_name</var>
+  { SET <var class="keyword varname">kudu_storage_attr</var> <var class="keyword varname">attr_value</var>
+    | DROP DEFAULT }
+
+kudu_storage_attr ::= { DEFAULT | BLOCK_SIZE | ENCODING | COMPRESSION }</span>
+
+<span class="ph">-- Non-Kudu tables only.
+ALTER TABLE <var class="keyword varname">name</var> ALTER [COLUMN] <var class="keyword varname">column_name</var>
+  SET COMMENT '<var class="keyword varname">comment_text</var>'</span>
+
 ALTER TABLE <var class="keyword varname">name</var> ADD [IF NOT EXISTS] PARTITION (<var class="keyword varname">partition_spec</var>)
   <span class="ph">[<var class="keyword varname">location_spec</var>]</span>
   <span class="ph">[<var class="keyword varname">cache_spec</var>]</span>
@@ -994,8 +1006,14 @@ ALTER TABLE <var class="keyword varname">table_name</var> SET TBLPROPERTIES('EXT
         </li>
         <li class="li">
           <p class="p">
-            You cannot change the default value, nullability, encoding, compression, or block size
-            of existing columns in a Kudu table.
+            You cannot change the nullability of existing columns in a Kudu table.
+          </p>
+        </li>
+        <li class="li">
+          <p class="p">
+            In <span class="keyword">Impala 2.10</span>, you can change the default value, encoding,
+            compression, or block size of existing columns in a Kudu table by using the
+            <code class="ph codeph">SET</code> clause.
           </p>
         </li>
         <li class="li">
@@ -1030,6 +1048,55 @@ ALTER TABLE t1 ADD COLUMNS (a STRING NOT NULL DEFAULT '', t TIMESTAMP COMPRESSIO
 </code></pre>
 
     <p class="p">
+      The following are some examples of modifying column defaults and storage attributes for a Kudu table:
+    </p>
+
+<pre class="pre codeblock"><code>
+create table kt (x bigint primary key, s string default 'yes', t timestamp)
+  stored as kudu;
+
+-- You can change the default value for a column, which affects any rows
+-- inserted after this change is made.
+alter table kt alter column s set default 'no';
+
+-- You can remove the default value for a column, which affects any rows
+-- inserted after this change is made. If the column is nullable, any
+-- future inserts default to NULL for this column. If the column is marked
+-- NOT NULL, any future inserts must specify a value for the column.
+alter table kt alter column s drop default;
+
+insert into kt values (1, 'foo', now());
+-- Because of the DROP DEFAULT above, omitting S from the insert
+-- gives it a value of NULL.
+insert into kt (x, t) values (2, now());
+
+select * from kt;
++---+------+-------------------------------+
+| x | s    | t                             |
++---+------+-------------------------------+
+| 2 | NULL | 2017-10-02 00:03:40.652156000 |
+| 1 | foo  | 2017-10-02 00:03:04.346185000 |
++---+------+-------------------------------+
+
+-- Other storage-related attributes can also be changed for columns.
+-- These changes take effect for any newly inserted rows, or rows
+-- rearranged due to compaction after deletes or updates.
+alter table kt alter column s set encoding prefix_encoding;
+-- The COLUMN keyword is optional in the syntax.
+alter table kt alter x set block_size 2048;
+alter table kt alter column t set compression zlib;
+
+desc kt;
++------+-----------+---------+-------------+----------+---------------+-----------------+---------------------+------------+
+| name | type      | comment | primary_key | nullable | default_value | encoding        | compression         | block_size |
++------+-----------+---------+-------------+----------+---------------+-----------------+---------------------+------------+
+| x    | bigint    |         | true        | false    |               | AUTO_ENCODING   | DEFAULT_COMPRESSION | 2048       |
+| s    | string    |         | false       | true     |               | PREFIX_ENCODING | DEFAULT_COMPRESSION | 0          |
+| t    | timestamp |         | false       | true     |               | AUTO_ENCODING   | ZLIB                | 0          |
++------+-----------+---------+-------------+----------+---------------+-----------------+---------------------+------------+
+</code></pre>
+
+    <p class="p">
       Kudu tables all use an underlying partitioning mechanism. The partition syntax is different than for non-Kudu
       tables. You can use the <code class="ph codeph">ALTER TABLE</code> statement to add and drop <dfn class="term">range partitions</dfn>
       from a Kudu table. Any new range must not overlap with any existing ranges. Dropping a range removes all the associated

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_array.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_array.html b/docs/build/html/topics/impala_array.html
index 960e337..f0ebc4e 100644
--- a/docs/build/html/topics/impala_array.html
+++ b/docs/build/html/topics/impala_array.html
@@ -118,7 +118,7 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
           </p>
         </li>
         <li class="li">
-          <p class="p" id="array__d6e3003">
+          <p class="p" id="array__d6e3156">
             The maximum length of the column definition for any complex type, including declarations for any nested types,
             is 4000 characters.
           </p>

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_buffer_pool_limit.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_buffer_pool_limit.html b/docs/build/html/topics/impala_buffer_pool_limit.html
new file mode 100644
index 0000000..b1e59a8
--- /dev/null
+++ b/docs/build/html/topics/impala_buffer_pool_limit.html
@@ -0,0 +1,71 @@
+<!DOCTYPE html
+  SYSTEM "about:legacy-compat">
+<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_query_options.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="buffer_pool_limit"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>BUFFER_POOL_LIMIT Query Option</title></head><body id="buffer_pool_limit"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
+
+  <h1 class="title topictitle1" id="ariaid-title1">BUFFER_POOL_LIMIT Query Option</h1>
+  
+  
+
+  <div class="body conbody">
+
+    <p class="p">
+      
+      Defines a limit on the amount of memory that a query can allocate from the
+      internal buffer pool. The value for this limit applies to the memory on each host,
+      not the aggregate memory across the cluster. Typically not changed by users, except
+      during diagnosis of out-of-memory errors during queries.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Type:</strong> integer
+      </p>
+
+
+
+    <p class="p">
+        <strong class="ph b">Default:</strong>
+      </p>
+    <p class="p">
+      The default setting for this option is the lower of 80% of the
+      <code class="ph codeph">MEM_LIMIT</code> setting, or the <code class="ph codeph">MEM_LIMIT</code>
+      setting minus 100 MB.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.10.0</span>
+      </p>
+
+    <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+    <p class="p">
+      If queries encounter out-of-memory errors, consider decreasing the
+      <code class="ph codeph">BUFFER_POOL_LIMIT</code> setting to less than 80% of the
+      <code class="ph codeph">MEM_LIMIT setting</code>.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+
+<pre class="pre codeblock"><code>
+-- Set an absolute value.
+set buffer_pool_limit=8GB;
+
+-- Set a relative value based on the MEM_LIMIT setting.
+set buffer_pool_limit=80%;
+
+</code></pre>
+
+    <p class="p">
+        <strong class="ph b">Related information:</strong>
+      </p>
+    <p class="p">
+      <a class="xref" href="impala_default_spillable_buffer_size.html">DEFAULT_SPILLABLE_BUFFER_SIZE Query Option</a>,
+      <a class="xref" href="impala_max_row_size.html">MAX_ROW_SIZE Query Option</a>,
+      <a class="xref" href="impala_min_spillable_buffer_size.html">MIN_SPILLABLE_BUFFER_SIZE Query Option</a>,
+      <a class="xref" href="impala_scalability.html">Scalability Considerations for Impala</a>
+    </p>
+
+  </div>
+<nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_query_options.html">Query Options for the SET Statement</a></div></div></nav></article></main></body></html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_compute_stats.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_compute_stats.html b/docs/build/html/topics/impala_compute_stats.html
index a20c0b2..c816b31 100644
--- a/docs/build/html/topics/impala_compute_stats.html
+++ b/docs/build/html/topics/impala_compute_stats.html
@@ -61,6 +61,31 @@ COMPUTE INCREMENTAL STATS [<var class="keyword varname">db_name</var>.]<var clas
       for full usage details.
     </p>
 
+    <div class="note important note_important"><span class="note__title importanttitle">Important:</span> 
+      <p class="p">
+        For a particular table, use either <code class="ph codeph">COMPUTE STATS</code> or
+        <code class="ph codeph">COMPUTE INCREMENTAL STATS</code>, but never combine the two or alternate
+        between them. If you switch from <code class="ph codeph">COMPUTE STATS</code> to
+        <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> during the lifetime of a table, or vice
+        versa, drop all statistics (by running both <code class="ph codeph">DROP STATS</code> and
+        <code class="ph codeph">DROP INCREMENTAL STATS</code>) before making the switch.
+      </p>
+      <p class="p">
+        When you run <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> on a table for the first time,
+        the statistics are computed again from scratch regardless of whether the table already
+        has statistics. Therefore, expect a one-time resource-intensive operation
+        for scanning the entire table when running <code class="ph codeph">COMPUTE INCREMENTAL STATS</code>
+        for the first time on a given table.
+      </p>
+      <p class="p">
+        For a table with a huge number of partitions and many columns, the approximately 400 bytes
+        of metadata per column per partition can add up to significant memory overhead, as it must
+        be cached on the <span class="keyword cmdname">catalogd</span> host and on every <span class="keyword cmdname">impalad</span> host
+        that is eligible to be a coordinator. If this metadata for all tables combined exceeds 2 GB,
+        you might experience service downtime.
+      </p>
+    </div>
+
     <p class="p">
       <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> only applies to partitioned tables. If you use the
       <code class="ph codeph">INCREMENTAL</code> clause for an unpartitioned table, Impala automatically uses the original
@@ -330,7 +355,7 @@ Returned 2 row(s) in 0.01s</code></pre>
     </p>
 
 <pre class="pre codeblock"><code>-- Initially the table has no incremental stats, as indicated
--- by -1 under #Rows and false under Incremental stats.
+-- 'false' under Incremental stats.
 show table stats item_partitioned;
 +-------------+-------+--------+----------+--------------+---------+------------------
 | i_category  | #Rows | #Files | Size     | Bytes Cached | Format  | Incremental stats
@@ -349,7 +374,10 @@ show table stats item_partitioned;
 +-------------+-------+--------+----------+--------------+---------+------------------
 
 -- After the first COMPUTE INCREMENTAL STATS,
--- all partitions have stats.
+-- all partitions have stats. The first
+-- COMPUTE INCREMENTAL STATS scans the whole
+-- table, discarding any previous stats from
+-- a traditional COMPUTE STATS statement.
 compute incremental stats item_partitioned;
 +-------------------------------------------+
 | summary                                   |

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_config_options.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_config_options.html b/docs/build/html/topics/impala_config_options.html
index 5bf3ff2..27b332f 100644
--- a/docs/build/html/topics/impala_config_options.html
+++ b/docs/build/html/topics/impala_config_options.html
@@ -73,7 +73,6 @@ IMPALA_SERVER_ARGS=" \
 -log_dir=${IMPALA_LOG_DIR} \
 -catalog_service_host=${IMPALA_CATALOG_SERVICE_HOST} \
 -state_store_port=${IMPALA_STATE_STORE_PORT} \
--use_statestore \
 -state_store_host=${IMPALA_STATE_STORE_HOST} \
 -be_port=${IMPALA_BACKEND_PORT}"
 export ENABLE_CORE_DUMPS=${ENABLE_COREDUMPS:-false}</code></pre>
@@ -154,14 +153,14 @@ Starting Impala Catalog Server:                            [  OK  ]</code></pre>
 <pre class="pre codeblock"><code>export IMPALA_SERVER_ARGS=${IMPALA_SERVER_ARGS:- \
     -log_dir=${IMPALA_LOG_DIR} \
     -state_store_port=${IMPALA_STATE_STORE_PORT} \
-    -use_statestore -state_store_host=${IMPALA_STATE_STORE_HOST} \
+    -state_store_host=${IMPALA_STATE_STORE_HOST} \
     -be_port=${IMPALA_BACKEND_PORT}}</code></pre>
           <p class="p">
             to:
           </p>
 <pre class="pre codeblock"><code>export IMPALA_SERVER_ARGS=${IMPALA_SERVER_ARGS:- \
     -log_dir=${IMPALA_LOG_DIR} -state_store_port=${IMPALA_STATE_STORE_PORT} \
-    -use_statestore -state_store_host=${IMPALA_STATE_STORE_HOST} \
+    -state_store_host=${IMPALA_STATE_STORE_HOST} \
     -be_port=${IMPALA_BACKEND_PORT} -mem_limit=70%}</code></pre>
           <p class="p">
             You can specify the memory limit using absolute notation such as

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_connecting.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_connecting.html b/docs/build/html/topics/impala_connecting.html
index e48d850..e3d6e9e 100644
--- a/docs/build/html/topics/impala_connecting.html
+++ b/docs/build/html/topics/impala_connecting.html
@@ -59,8 +59,7 @@
         Use the <code class="ph codeph">-i</code> option to the
         <span class="keyword cmdname">impala-shell</span> interpreter to specify the connection information for
         that instance of <span class="keyword cmdname">impalad</span>:
-<pre class="pre codeblock"><code>
-# When you are logged into the same machine running impalad.
+<pre class="pre codeblock"><code># When you are logged into the same machine running impalad.
 # The prompt will reflect the current hostname.
 $ impala-shell
 
@@ -138,8 +137,7 @@ $ impala-shell -i <var class="keyword varname">some.other.hostname</var>:<var cl
         <span class="keyword cmdname">impala-shell</span> interpreter to connect and immediately
         switch to the specified database, without the need for a <code class="ph codeph">USE</code>
         statement or fully qualified names:
-<pre class="pre codeblock"><code>
-# Subsequent queries with unqualified names operate on
+<pre class="pre codeblock"><code># Subsequent queries with unqualified names operate on
 # tables, views, and so on inside the database named 'staging'.
 $ impala-shell -i localhost -d staging
 
@@ -174,8 +172,7 @@ $ impala-shell -i localhost -d parquet_gzip_compression
         the <code class="ph codeph">-f</code> option to run a sequence of statements from a file.
         The <span class="keyword cmdname">impala-shell</span> command returns immediately, without going into
         the interactive interpreter.
-<pre class="pre codeblock"><code>
-# A utility command that you might run while developing shell scripts
+<pre class="pre codeblock"><code># A utility command that you might run while developing shell scripts
 # to manipulate HDFS files.
 $ impala-shell -i localhost -d database_of_interest -q 'show tables'
 

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_create_table.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_create_table.html b/docs/build/html/topics/impala_create_table.html
index 1d890d8..1bf8327 100644
--- a/docs/build/html/topics/impala_create_table.html
+++ b/docs/build/html/topics/impala_create_table.html
@@ -160,7 +160,7 @@ data_type:
     [, ...]
     [PRIMARY KEY (<var class="keyword varname">col_name</var>[, ...])]
   )
-  <span class="ph">[PARTITION BY <var class="keyword varname">kudu_partition_clause</var></span>
+  <span class="ph">[PARTITION BY <var class="keyword varname">kudu_partition_clause</var>]</span>
   [COMMENT '<var class="keyword varname">table_comment</var>']
   STORED AS KUDU
   [TBLPROPERTIES ('<var class="keyword varname">key1</var>'='<var class="keyword varname">value1</var>', '<var class="keyword varname">key2</var>'='<var class="keyword varname">value2</var>', ...)]
@@ -181,7 +181,7 @@ data_type:
     <div class="p">
       <strong class="ph b">kudu_partition_clause:</strong>
 <pre class="pre codeblock"><code>
-kudu_partition_clause ::= PARTITION BY [<var class="keyword varname">hash_clause</var>] [, <var class="keyword varname">range_clause</var> [ , <var class="keyword varname">range_clause</var> ] ]
+kudu_partition_clause ::= [<var class="keyword varname">hash_clause</var>] [, <var class="keyword varname">range_clause</var> [ , <var class="keyword varname">range_clause</var> ] ]
 
 hash_clause ::=
   HASH [ (<var class="keyword varname">pk_col</var> [, ...]) ]
@@ -217,7 +217,7 @@ range_comparison_operator ::= { &lt; | &lt;= }
 
 <pre class="pre codeblock"><code>CREATE TABLE [IF NOT EXISTS] <var class="keyword varname">db_name</var>.]<var class="keyword varname">table_name</var>
   [PRIMARY KEY (<var class="keyword varname">col_name</var>[, ...])]
-  [PARTITION BY <var class="keyword varname">kudu_partition_clause</var>
+  [PARTITION BY <var class="keyword varname">kudu_partition_clause</var>]
   [COMMENT '<var class="keyword varname">table_comment</var>']
   STORED AS KUDU
   [TBLPROPERTIES ('<var class="keyword varname">key1</var>'='<var class="keyword varname">value1</var>', '<var class="keyword varname">key2</var>'='<var class="keyword varname">value2</var>', ...)]
@@ -337,6 +337,14 @@ AS
         tables. See the <code class="ph codeph">PARTITION BY</code> clause, rather than <code class="ph codeph">PARTITIONED
         BY</code>, for Kudu tables.
       </p>
+      <p class="p">
+        In <span class="keyword">Impala 2.10</span> and higher, the <code class="ph codeph">PARTITION BY</code>
+        clause is optional for Kudu tables. If the clause is omitted, Impala automatically
+        constructs a single partition that is not connected to any column. Because such a
+        table cannot take advantage of Kudu features for parallelized queries and
+        query optimizations, omitting the <code class="ph codeph">PARTITION BY</code> clause is only
+        appropriate for small lookup tables.
+      </p>
     </div>
 
     <p class="p">
@@ -434,9 +442,9 @@ AS
       partitioning mechanisms, the syntax associated with the <code class="ph codeph">STORED AS KUDU</code>
       clause is shown separately in the above syntax descriptions. Kudu tables have their own
       syntax for <code class="ph codeph">CREATE TABLE</code>, <code class="ph codeph">CREATE EXTERNAL TABLE</code>, and
-      <code class="ph codeph">CREATE TABLE AS SELECT</code>. All internal Kudu tables require a
-      <code class="ph codeph">PARTITION BY</code> clause, different than the <code class="ph codeph">PARTITIONED BY</code>
-      clause for HDFS-backed tables.
+      <code class="ph codeph">CREATE TABLE AS SELECT</code>. <span class="ph">Prior to <span class="keyword">Impala 2.10</span>,
+      all internal Kudu tables require a <code class="ph codeph">PARTITION BY</code> clause, different than
+      the <code class="ph codeph">PARTITIONED BY</code> clause for HDFS-backed tables.</span>
     </p>
 
     <p class="p">
@@ -444,6 +452,14 @@ AS
     </p>
 
 <pre class="pre codeblock"><code>
+<span class="ph">-- Single partition. Only for <span class="keyword">Impala 2.10</span> and higher.
+-- Only suitable for small lookup tables.
+CREATE TABLE kudu_no_partition_by_clause
+  (
+    id bigint PRIMARY KEY, s STRING, b BOOLEAN
+  )
+  STORED AS KUDU;</span>
+
 -- Single-column primary key.
 CREATE TABLE kudu_t1 (id BIGINT PRIMARY key, s STRING, b BOOLEAN)
   PARTITION BY HASH (id) PARTITIONS 20 STORED AS KUDU;

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_datetime_functions.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_datetime_functions.html b/docs/build/html/topics/impala_datetime_functions.html
index 1649c0a..b566354 100644
--- a/docs/build/html/topics/impala_datetime_functions.html
+++ b/docs/build/html/topics/impala_datetime_functions.html
@@ -769,6 +769,74 @@ select now() as right_now,
 
       
 
+        <dt class="dt dlterm" id="datetime_functions__from_timestamp">
+          <code class="ph codeph">from_timestamp(datetime timestamp, pattern string)</code>
+        </dt>
+
+        <dd class="dd">
+          
+          <strong class="ph b">Purpose:</strong> Converts a <code class="ph codeph">TIMESTAMP</code> value into a
+          string representing the same value.
+          <p class="p">
+            <strong class="ph b">Return type:</strong> <code class="ph codeph">string</code>
+          </p>
+          <p class="p">
+        <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.3.0</span>
+      </p>
+          <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+          <p class="p">
+            The <code class="ph codeph">from_timestamp()</code> function provides a flexible way to convert <code class="ph codeph">TIMESTAMP</code>
+            values into arbitrary string formats for reporting purposes.
+          </p>
+          <p class="p">
+            Because Impala implicitly converts string values into <code class="ph codeph">TIMESTAMP</code>, you can
+            pass date/time values represented as strings (in the standard <code class="ph codeph">yyyy-MM-dd HH:mm:ss.SSS</code> format)
+            to this function. The result is a string using different separator characters, order of fields, spelled-out month
+            names, or other variation of the date/time string representation.
+          </p>
+          <p class="p">
+            The allowed tokens for the pattern string are the same as for the <code class="ph codeph">from_unixtime()</code> function.
+          </p>
+          <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+          <p class="p">
+            The following examples show different ways to format a <code class="ph codeph">TIMESTAMP</code>
+            value as a string:
+          </p>
+<pre class="pre codeblock"><code>
+-- Reformat arbitrary TIMESTAMP value.
+select from_timestamp(now(), 'yyyy/MM/dd');
++-------------------------------------+
+| from_timestamp(now(), 'yyyy/mm/dd') |
++-------------------------------------+
+| 2017/10/01                          |
++-------------------------------------+
+
+-- Reformat string literal representing date/time.
+select from_timestamp('1984-09-25', 'yyyy/MM/dd');
++--------------------------------------------+
+| from_timestamp('1984-09-25', 'yyyy/mm/dd') |
++--------------------------------------------+
+| 1984/09/25                                 |
++--------------------------------------------+
+
+-- Alternative format for reporting purposes.
+select from_timestamp('1984-09-25 16:45:30.125', 'MMM dd, yyyy HH:mm:ss.SSS');
++------------------------------------------------------------------------+
+| from_timestamp('1984-09-25 16:45:30.125', 'mmm dd, yyyy hh:mm:ss.sss') |
++------------------------------------------------------------------------+
+| Sep 25, 1984 16:45:30.125                                              |
++------------------------------------------------------------------------+
+</code></pre>
+        </dd>
+
+      
+
+      
+
         <dt class="dt dlterm" id="datetime_functions__from_unixtime">
           <code class="ph codeph">from_unixtime(bigint unixtime[, string format])</code>
         </dt>
@@ -1129,6 +1197,74 @@ select int_months_between('2015-03-31', '2015-01-30');
 
       
 
+        <dt class="dt dlterm" id="datetime_functions__last_day">
+          <code class="ph codeph">last_day(timestamp t)</code>
+        </dt>
+
+        <dd class="dd">
+          
+          <strong class="ph b">Purpose:</strong> Returns a <code class="ph codeph">TIMESTAMP</code> corresponding to
+          the beginning of the last calendar day in the same month as the
+          <code class="ph codeph">TIMESTAMP</code> argument.
+          <p class="p">
+            <strong class="ph b">Return type:</strong> <code class="ph codeph">timestamp</code>
+          </p>
+          <p class="p">
+        <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.9.0</span>
+      </p>
+          <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+          <p class="p">
+            If the input argument does not represent a valid Impala <code class="ph codeph">TIMESTAMP</code>
+            including both date and time portions, the function returns <code class="ph codeph">NULL</code>.
+            For example, if the input argument is a string that cannot be implicitly cast to
+            <code class="ph codeph">TIMESTAMP</code>, does not include a date portion, or is out of the
+            allowed range for Impala <code class="ph codeph">TIMESTAMP</code> values, the function returns
+            <code class="ph codeph">NULL</code>.
+          </p>
+          <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+          <p class="p">
+            The following example shows how to examine the current date, and dates around the
+            end of the month, as <code class="ph codeph">TIMESTAMP</code> values with any time portion removed:
+          </p>
+<pre class="pre codeblock"><code>
+select
+    now() as right_now
+  , trunc(now(),'dd') as today
+  , last_day(now()) as last_day_of_month
+  , last_day(now()) + interval 1 day as first_of_next_month;
++-------------------------------+---------------------+---------------------+---------------------+
+| right_now                     | today               | last_day_of_month   | first_of_next_month |
++-------------------------------+---------------------+---------------------+---------------------+
+| 2017-08-15 15:07:58.823812000 | 2017-08-15 00:00:00 | 2017-08-31 00:00:00 | 2017-09-01 00:00:00 |
++-------------------------------+---------------------+---------------------+---------------------+
+</code></pre>
+          <p class="p">
+            The following example shows how to examine the current date and dates around the
+            end of the month as integers representing the day of the month:
+          </p>
+<pre class="pre codeblock"><code>
+select
+    now() as right_now
+  , dayofmonth(now()) as day
+  , extract(day from now()) as also_day
+  , dayofmonth(last_day(now())) as last_day
+  , extract(day from last_day(now())) as also_last_day;
++-------------------------------+-----+----------+----------+---------------+
+| right_now                     | day | also_day | last_day | also_last_day |
++-------------------------------+-----+----------+----------+---------------+
+| 2017-08-15 15:07:59.417755000 | 15  | 15       | 31       | 31            |
++-------------------------------+-----+----------+----------+---------------+
+</code></pre>
+        </dd>
+
+      
+
+      
+
         <dt class="dt dlterm" id="datetime_functions__microseconds_add">
           <code class="ph codeph">microseconds_add(timestamp date, int microseconds)</code>, <code class="ph codeph">microseconds_add(timestamp
           date, bigint microseconds)</code>
@@ -2162,6 +2298,94 @@ select now() as right_now,
 
       
 
+        <dt class="dt dlterm" id="datetime_functions__to_timestamp">
+          <code class="ph codeph">to_timestamp(bigint unixtime)</code>,
+          <code class="ph codeph">to_timestamp(string date, string pattern)</code>
+        </dt>
+
+        <dd class="dd">
+          
+          <strong class="ph b">Purpose:</strong> Converts an integer or string representing
+          a date/time value into the corresponding <code class="ph codeph">TIMESTAMP</code>
+          value.
+          <p class="p">
+            <strong class="ph b">Return type:</strong> <code class="ph codeph">timestamp</code>
+          </p>
+          <p class="p">
+        <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.3.0</span>
+      </p>
+          <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+          <p class="p">
+            An integer argument represents the number of seconds past the epoch (midnight
+            on January 1, 1970). It is the converse of the <code class="ph codeph">unix_timestamp()</code>
+            function, which produces a <code class="ph codeph">BIGINT</code> representing the number of
+            seconds past the epoch.
+          </p>
+          <p class="p">
+            A string argument, plus another string argument representing the
+            pattern, turns an arbitrary string representation of a date and time
+            into a true <code class="ph codeph">TIMESTAMP</code> value. The ability to parse
+            many kinds of date and time formats allows you to deal with temporal
+            data from diverse sources, and if desired to convert to efficient
+            <code class="ph codeph">TIMESTAMP</code> values during your ETL process. Using
+            <code class="ph codeph">TIMESTAMP</code> directly in queries and expressions lets you
+            perform date and time calculations without the overhead of extra
+            function calls and conversions each time you reference the applicable
+            columns.
+          </p>
+          <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+          <p class="p">
+            The following examples demonstrate how to convert an arbitrary string
+            representation to <code class="ph codeph">TIMESTAMP</code> based on a pattern string:
+          </p>
+<pre class="pre codeblock"><code>
+select to_timestamp('Sep 25, 1984', 'MMM dd, yyyy');
++----------------------------------------------+
+| to_timestamp('sep 25, 1984', 'mmm dd, yyyy') |
++----------------------------------------------+
+| 1984-09-25 00:00:00                          |
++----------------------------------------------+
+
+select to_timestamp('1984/09/25', 'yyyy/MM/dd');
++------------------------------------------+
+| to_timestamp('1984/09/25', 'yyyy/mm/dd') |
++------------------------------------------+
+| 1984-09-25 00:00:00                      |
++------------------------------------------+
+</code></pre>
+          <p class="p">
+            The following examples show how to convert a <code class="ph codeph">BIGINT</code>
+            representing seconds past epoch into a <code class="ph codeph">TIMESTAMP</code> value:
+          </p>
+<pre class="pre codeblock"><code>
+-- One day past the epoch.
+select to_timestamp(24 * 60 * 60);
++----------------------------+
+| to_timestamp(24 * 60 * 60) |
++----------------------------+
+| 1970-01-02 00:00:00        |
++----------------------------+
+
+-- 60 seconds in the past.
+select now() as 'current date/time',
+  unix_timestamp(now()) 'now in seconds',
+  to_timestamp(unix_timestamp(now()) - 60) as '60 seconds ago';
++-------------------------------+----------------+---------------------+
+| current date/time             | now in seconds | 60 seconds ago      |
++-------------------------------+----------------+---------------------+
+| 2017-10-01 22:03:46.885624000 | 1506895426     | 2017-10-01 22:02:46 |
++-------------------------------+----------------+---------------------+
+</code></pre>
+        </dd>
+
+      
+
+      
+
         <dt class="dt dlterm" id="datetime_functions__to_utc_timestamp">
           <code class="ph codeph">to_utc_timestamp(timestamp, string timezone)</code>
         </dt>
@@ -2232,7 +2456,7 @@ select now() as 'Current time in California USA',
 
       
 
-        <dt class="dt dlterm" id="datetime_functions__trunc">
+        <dt class="dt dlterm" id="datetime_functions__trunc_timestamp"><a id="datetime_functions__trunc"></a>
           <code class="ph codeph">trunc(timestamp, string unit)</code>
         </dt>
 
@@ -2240,7 +2464,8 @@ select now() as 'Current time in California USA',
           
           <strong class="ph b">Purpose:</strong> Strips off fields from a <code class="ph codeph">TIMESTAMP</code> value.
           <div class="p">
-            <strong class="ph b">Unit argument:</strong> The <code class="ph codeph">unit</code> argument value is case-sensitive. This argument string
+            <strong class="ph b">Unit argument:</strong> The <code class="ph codeph">unit</code> argument value for truncating
+            <code class="ph codeph">TIMESTAMP</code> values is case-sensitive. This argument string
             can be one of:
 
             <ul class="ul">
@@ -2282,13 +2507,17 @@ select now() as 'Current time in California USA',
             </ul>
           </div>
           <p class="p">
+            <strong class="ph b">Added in:</strong> The ability to truncate numeric values is new starting in
+            <span class="keyword">Impala 2.10</span>.
+          </p>
+          <p class="p">
         <strong class="ph b">Usage notes:</strong>
       </p>
           <p class="p">
-            Typically used in <code class="ph codeph">GROUP BY</code> queries to aggregate results from the
-            same hour, day, week, month, quarter, and so on. You can also use this function in an <code class="ph codeph">INSERT
-            ... SELECT</code> into a partitioned table to divide <code class="ph codeph">TIMESTAMP</code> values into the
-            correct partition.
+            The <code class="ph codeph">TIMESTAMP</code> form is typically used in <code class="ph codeph">GROUP BY</code>
+            queries to aggregate results from the same hour, day, week, month, quarter, and so on.
+            You can also use this function in an <code class="ph codeph">INSERT ... SELECT</code> into a
+            partitioned table to divide <code class="ph codeph">TIMESTAMP</code> values into the correct partition.
           </p>
           <p class="p">
             Because the return value is a <code class="ph codeph">TIMESTAMP</code>, if you cast the result of
@@ -2299,6 +2528,13 @@ select now() as 'Current time in California USA',
             original value, then run <code class="ph codeph">EXTRACT()</code> on the result.
           </p>
           <p class="p">
+            The <code class="ph codeph">trunc()</code> function also has a signature that applies to
+            <code class="ph codeph">DOUBLE</code> or <code class="ph codeph">DECIMAL</code>values. <code class="ph codeph">truncate()</code>,
+            <code class="ph codeph">trunc()</code>, and <code class="ph codeph">dtrunc()</code> are all aliased to the
+            same function. See <code class="ph codeph">truncate()</code> under <a class="xref" href="impala_math_functions.html">Impala Mathematical Functions</a>
+            for details.
+          </p>
+          <p class="p">
             <strong class="ph b">Return type:</strong> <code class="ph codeph">timestamp</code>
           </p>
           <p class="p">
@@ -2469,6 +2705,68 @@ select unix_timestamp
 
       
 
+        <dt class="dt dlterm" id="datetime_functions__utc_timestamp">
+          <code class="ph codeph">utc_timestamp()</code>
+        </dt>
+
+        <dd class="dd">
+          
+          <strong class="ph b">Purpose:</strong> Returns a <code class="ph codeph">TIMESTAMP</code> corresponding to the current
+          date and time in the UTC time zone.
+          <p class="p">
+            <strong class="ph b">Return type:</strong> <code class="ph codeph">timestamp</code>
+          </p>
+          <p class="p">
+        <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.10</span>
+      </p>
+          <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+          <p class="p">
+            Similar to the <code class="ph codeph">now()</code> or <code class="ph codeph">current_timestamp()</code> functions,
+            but does not use the local time zone as those functions do. Use <code class="ph codeph">utc_timestamp()</code>
+            to record <code class="ph codeph">TIMESTAMP</code> values that are interoperable with
+            servers around the world, in arbitrary time zones, without the need for
+            additional conversion functions to standardize the time zone of each
+            value representing a date/time.
+          </p>
+          <p class="p">
+            For working with date/time values represented as integer values, you can convert
+            back and forth between <code class="ph codeph">TIMESTAMP</code> and <code class="ph codeph">BIGINT</code>
+            with the <code class="ph codeph">unix_micros_to_utc_timestamp()</code> and
+            <code class="ph codeph">utc_to_unix_micros()</code> functions. The integer values represent
+            the number of microseconds since the Unix epoch (midnight on January 1, 1970).
+          </p>
+          <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+          <p class="p">
+            The following example shows how <code class="ph codeph">now()</code> and <code class="ph codeph">current_timestamp()</code>
+            represent the current date/time in the local time zone (in this case, UTC-7), while
+            <code class="ph codeph">utc_timestamp()</code> represents the same date/time in the standardized UTC
+            time zone:
+          </p>
+<pre class="pre codeblock"><code>
+select now(), utc_timestamp();
++-------------------------------+-------------------------------+
+| now()                         | utc_timestamp()               |
++-------------------------------+-------------------------------+
+| 2017-10-01 23:33:58.919688000 | 2017-10-02 06:33:58.919688000 |
++-------------------------------+-------------------------------+
+
+select current_timestamp(), utc_timestamp();
++-------------------------------+-------------------------------+
+| current_timestamp()           | utc_timestamp()               |
++-------------------------------+-------------------------------+
+| 2017-10-01 23:34:07.400642000 | 2017-10-02 06:34:07.400642000 |
++-------------------------------+-------------------------------+
+</code></pre>
+        </dd>
+
+      
+
+      
+
         <dt class="dt dlterm" id="datetime_functions__weekofyear">
           
           <code class="ph codeph">weekofyear(timestamp date)</code>



[4/7] incubator-impala git commit: Update Impala docs for 2.10 release

Posted by jr...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_hbase.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_hbase.html b/docs/build/html/topics/impala_hbase.html
index 7ee8bad..7112f90 100644
--- a/docs/build/html/topics/impala_hbase.html
+++ b/docs/build/html/topics/impala_hbase.html
@@ -612,6 +612,15 @@ set hbase_caching=1000;
         The <code class="ph codeph">LOAD DATA</code> statement cannot be used with HBase tables.
       </p>
         </li>
+        <li class="li">
+          <p class="p">
+        The <code class="ph codeph">TABLESAMPLE</code> clause of the <code class="ph codeph">SELECT</code>
+        statement does not apply to a table reference derived from a view, a subquery,
+        or anything other than a real base table. This clause only works for tables
+        backed by HDFS or HDFS-like data files, therefore it does not apply to Kudu or
+        HBase tables.
+      </p>
+        </li>
       </ul>
     </div>
   </article>

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_hints.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_hints.html b/docs/build/html/topics/impala_hints.html
index f2b48f0..19bd16d 100644
--- a/docs/build/html/topics/impala_hints.html
+++ b/docs/build/html/topics/impala_hints.html
@@ -111,11 +111,19 @@ INSERT <var class="keyword varname">insert_clauses</var>
 
     <p class="p">
       With both forms of hint syntax, include the <code class="ph codeph">STRAIGHT_JOIN</code>
-      keyword immediately after the <code class="ph codeph">SELECT</code> keyword to prevent Impala from
+      keyword immediately after the <code class="ph codeph">SELECT</code> and any
+      <code class="ph codeph">DISTINCT</code> or <code class="ph codeph">ALL</code> keywords to prevent Impala from
       reordering the tables in a way that makes the join-related hints ineffective.
     </p>
 
     <p class="p">
+        The <code class="ph codeph">STRAIGHT_JOIN</code> hint affects the join order of table references in the query
+        block containing the hint. It does not affect the join order of nested queries, such as views,
+        inline views, or <code class="ph codeph">WHERE</code>-clause subqueries. To use this hint for performance
+        tuning of complex queries, apply the hint to all query blocks that need a fixed join order.
+      </p>
+
+    <p class="p">
       To reduce the need to use hints, run the <code class="ph codeph">COMPUTE STATS</code> statement against all tables involved
       in joins, or used as the source tables for <code class="ph codeph">INSERT ... SELECT</code> operations where the
       destination is a partitioned Parquet table. Do this operation after loading data or making substantial

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_incompatible_changes.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_incompatible_changes.html b/docs/build/html/topics/impala_incompatible_changes.html
index 9623ba1..d968e2b 100644
--- a/docs/build/html/topics/impala_incompatible_changes.html
+++ b/docs/build/html/topics/impala_incompatible_changes.html
@@ -23,9 +23,25 @@
     <p class="p toc inpage"></p>
   </div>
 
-  <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_release_notes.html">Impala Release Notes</a></div></div></nav><article class="topic concept nested1" aria-labelledby="ariaid-title2" id="incompatible_changes__incompatible_changes_29x">
+  <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_release_notes.html">Impala Release Notes</a></div></div></nav><article class="topic concept nested1" aria-labelledby="ariaid-title2" id="incompatible_changes__incompatible_changes_210x">
 
-    <h2 class="title topictitle2" id="ariaid-title2">Incompatible Changes Introduced in Impala 2.9.x</h2>
+    <h2 class="title topictitle2" id="ariaid-title2">Incompatible Changes Introduced in Impala 2.10.x</h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        For the full list of issues closed in this release, including any that introduce
+        behavior changes or incompatibilities, see the
+        <a class="xref" href="https://impala.incubator.apache.org/docs/changelog-2.10.html" target="_blank">changelog for <span class="keyword">Impala 2.10</span></a>.
+      </p>
+
+    </div>
+
+  </article>
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title3" id="incompatible_changes__incompatible_changes_29x">
+
+    <h2 class="title topictitle2" id="ariaid-title3">Incompatible Changes Introduced in Impala 2.9.x</h2>
 
     <div class="body conbody">
 
@@ -41,9 +57,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title3" id="incompatible_changes__incompatible_changes_28x">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title4" id="incompatible_changes__incompatible_changes_28x">
 
-    <h2 class="title topictitle2" id="ariaid-title3">Incompatible Changes Introduced in Impala 2.8.x</h2>
+    <h2 class="title topictitle2" id="ariaid-title4">Incompatible Changes Introduced in Impala 2.8.x</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -134,9 +150,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title4" id="incompatible_changes__incompatible_changes_27x">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title5" id="incompatible_changes__incompatible_changes_27x">
 
-    <h2 class="title topictitle2" id="ariaid-title4">Incompatible Changes Introduced in Impala 2.7.x</h2>
+    <h2 class="title topictitle2" id="ariaid-title5">Incompatible Changes Introduced in Impala 2.7.x</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -158,9 +174,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title5" id="incompatible_changes__incompatible_changes_26x">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title6" id="incompatible_changes__incompatible_changes_26x">
 
-    <h2 class="title topictitle2" id="ariaid-title5">Incompatible Changes Introduced in Impala 2.6.x</h2>
+    <h2 class="title topictitle2" id="ariaid-title6">Incompatible Changes Introduced in Impala 2.6.x</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -307,9 +323,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title6" id="incompatible_changes__incompatible_changes_25x">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title7" id="incompatible_changes__incompatible_changes_25x">
 
-    <h2 class="title topictitle2" id="ariaid-title6">Incompatible Changes Introduced in Impala 2.5.x</h2>
+    <h2 class="title topictitle2" id="ariaid-title7">Incompatible Changes Introduced in Impala 2.5.x</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -395,9 +411,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title7" id="incompatible_changes__incompatible_changes_24x">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title8" id="incompatible_changes__incompatible_changes_24x">
 
-    <h2 class="title topictitle2" id="ariaid-title7">Incompatible Changes Introduced in Impala 2.4.x</h2>
+    <h2 class="title topictitle2" id="ariaid-title8">Incompatible Changes Introduced in Impala 2.4.x</h2>
 
     <div class="body conbody">
       <p class="p">
@@ -412,9 +428,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title8" id="incompatible_changes__incompatible_changes_23x">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title9" id="incompatible_changes__incompatible_changes_23x">
 
-    <h2 class="title topictitle2" id="ariaid-title8">Incompatible Changes Introduced in Impala 2.3.x</h2>
+    <h2 class="title topictitle2" id="ariaid-title9">Incompatible Changes Introduced in Impala 2.3.x</h2>
 
     <div class="body conbody">
 
@@ -482,9 +498,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title9" id="incompatible_changes__incompatible_changes_22x">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title10" id="incompatible_changes__incompatible_changes_22x">
 
-    <h2 class="title topictitle2" id="ariaid-title9">Incompatible Changes Introduced in Impala 2.2.x</h2>
+    <h2 class="title topictitle2" id="ariaid-title10">Incompatible Changes Introduced in Impala 2.2.x</h2>
 
     <div class="body conbody">
 
@@ -527,9 +543,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title10" id="incompatible_changes__incompatible_changes_21x">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title11" id="incompatible_changes__incompatible_changes_21x">
 
-    <h2 class="title topictitle2" id="ariaid-title10">Incompatible Changes Introduced in Impala 2.1.x</h2>
+    <h2 class="title topictitle2" id="ariaid-title11">Incompatible Changes Introduced in Impala 2.1.x</h2>
 
     <div class="body conbody">
 
@@ -572,9 +588,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title11" id="incompatible_changes__incompatible_changes_205">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title12" id="incompatible_changes__incompatible_changes_205">
 
-    <h2 class="title topictitle2" id="ariaid-title11">Incompatible Changes Introduced in Impala 2.0.5</h2>
+    <h2 class="title topictitle2" id="ariaid-title12">Incompatible Changes Introduced in Impala 2.0.5</h2>
 
     <div class="body conbody">
 
@@ -585,9 +601,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title12" id="incompatible_changes__incompatible_changes_204">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title13" id="incompatible_changes__incompatible_changes_204">
 
-    <h2 class="title topictitle2" id="ariaid-title12">Incompatible Changes Introduced in Impala 2.0.4</h2>
+    <h2 class="title topictitle2" id="ariaid-title13">Incompatible Changes Introduced in Impala 2.0.4</h2>
 
     <div class="body conbody">
 
@@ -598,18 +614,18 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title13" id="incompatible_changes__incompatible_changes_203">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title14" id="incompatible_changes__incompatible_changes_203">
 
-    <h2 class="title topictitle2" id="ariaid-title13">Incompatible Changes Introduced in Impala 2.0.3</h2>
+    <h2 class="title topictitle2" id="ariaid-title14">Incompatible Changes Introduced in Impala 2.0.3</h2>
 
     <div class="body conbody">
 
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title14" id="incompatible_changes__incompatible_changes_202">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title15" id="incompatible_changes__incompatible_changes_202">
 
-    <h2 class="title topictitle2" id="ariaid-title14">Incompatible Changes Introduced in Impala 2.0.2</h2>
+    <h2 class="title topictitle2" id="ariaid-title15">Incompatible Changes Introduced in Impala 2.0.2</h2>
 
     <div class="body conbody">
 
@@ -620,9 +636,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title15" id="incompatible_changes__incompatible_changes_201">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title16" id="incompatible_changes__incompatible_changes_201">
 
-    <h2 class="title topictitle2" id="ariaid-title15">Incompatible Changes Introduced in Impala 2.0.1</h2>
+    <h2 class="title topictitle2" id="ariaid-title16">Incompatible Changes Introduced in Impala 2.0.1</h2>
 
     <div class="body conbody">
 
@@ -659,9 +675,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title16" id="incompatible_changes__incompatible_changes_200">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title17" id="incompatible_changes__incompatible_changes_200">
 
-    <h2 class="title topictitle2" id="ariaid-title16">Incompatible Changes Introduced in Impala 2.0.0</h2>
+    <h2 class="title topictitle2" id="ariaid-title17">Incompatible Changes Introduced in Impala 2.0.0</h2>
 
     <div class="body conbody">
 
@@ -855,8 +871,8 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title17" id="incompatible_changes__incompatible_changes_144">
-    <h2 class="title topictitle2" id="ariaid-title17">Incompatible Changes Introduced in Impala 1.4.4</h2>
+  <article class="topic concept nested1" aria-labelledby="ariaid-title18" id="incompatible_changes__incompatible_changes_144">
+    <h2 class="title topictitle2" id="ariaid-title18">Incompatible Changes Introduced in Impala 1.4.4</h2>
     <div class="body conbody">
       <p class="p">
         No incompatible changes.
@@ -865,9 +881,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title18" id="incompatible_changes__incompatible_changes_143">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title19" id="incompatible_changes__incompatible_changes_143">
 
-    <h2 class="title topictitle2" id="ariaid-title18">Incompatible Changes Introduced in Impala 1.4.3</h2>
+    <h2 class="title topictitle2" id="ariaid-title19">Incompatible Changes Introduced in Impala 1.4.3</h2>
 
     <div class="body conbody">
 
@@ -879,9 +895,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title19" id="incompatible_changes__incompatible_changes_142">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title20" id="incompatible_changes__incompatible_changes_142">
 
-    <h2 class="title topictitle2" id="ariaid-title19">Incompatible Changes Introduced in Impala 1.4.2</h2>
+    <h2 class="title topictitle2" id="ariaid-title20">Incompatible Changes Introduced in Impala 1.4.2</h2>
 
     <div class="body conbody">
 
@@ -892,9 +908,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title20" id="incompatible_changes__incompatible_changes_141">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title21" id="incompatible_changes__incompatible_changes_141">
 
-    <h2 class="title topictitle2" id="ariaid-title20">Incompatible Changes Introduced in Impala 1.4.1</h2>
+    <h2 class="title topictitle2" id="ariaid-title21">Incompatible Changes Introduced in Impala 1.4.1</h2>
 
     <div class="body conbody">
 
@@ -904,9 +920,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title21" id="incompatible_changes__incompatible_changes_140">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title22" id="incompatible_changes__incompatible_changes_140">
 
-    <h2 class="title topictitle2" id="ariaid-title21">Incompatible Changes Introduced in Impala 1.4.0</h2>
+    <h2 class="title topictitle2" id="ariaid-title22">Incompatible Changes Introduced in Impala 1.4.0</h2>
   
 
     <div class="body conbody">
@@ -1004,9 +1020,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title22" id="incompatible_changes__incompatible_changes_133">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title23" id="incompatible_changes__incompatible_changes_133">
 
-    <h2 class="title topictitle2" id="ariaid-title22">Incompatible Changes Introduced in Impala 1.3.3</h2>
+    <h2 class="title topictitle2" id="ariaid-title23">Incompatible Changes Introduced in Impala 1.3.3</h2>
 
     <div class="body conbody">
 
@@ -1018,9 +1034,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title23" id="incompatible_changes__incompatible_changes_132">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title24" id="incompatible_changes__incompatible_changes_132">
 
-    <h2 class="title topictitle2" id="ariaid-title23">Incompatible Changes Introduced in Impala 1.3.2</h2>
+    <h2 class="title topictitle2" id="ariaid-title24">Incompatible Changes Introduced in Impala 1.3.2</h2>
 
     <div class="body conbody">
 
@@ -1031,9 +1047,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title24" id="incompatible_changes__incompatible_changes_131">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title25" id="incompatible_changes__incompatible_changes_131">
 
-    <h2 class="title topictitle2" id="ariaid-title24">Incompatible Changes Introduced in Impala 1.3.1</h2>
+    <h2 class="title topictitle2" id="ariaid-title25">Incompatible Changes Introduced in Impala 1.3.1</h2>
 
     <div class="body conbody">
 
@@ -1061,9 +1077,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title25" id="incompatible_changes__incompatible_changes_130">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title26" id="incompatible_changes__incompatible_changes_130">
 
-    <h2 class="title topictitle2" id="ariaid-title25">Incompatible Changes Introduced in Impala 1.3.0</h2>
+    <h2 class="title topictitle2" id="ariaid-title26">Incompatible Changes Introduced in Impala 1.3.0</h2>
 
     <div class="body conbody">
 
@@ -1148,9 +1164,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title26" id="incompatible_changes__incompatible_changes_124">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title27" id="incompatible_changes__incompatible_changes_124">
 
-    <h2 class="title topictitle2" id="ariaid-title26">Incompatible Changes Introduced in Impala 1.2.4</h2>
+    <h2 class="title topictitle2" id="ariaid-title27">Incompatible Changes Introduced in Impala 1.2.4</h2>
 
     <div class="body conbody">
 
@@ -1170,9 +1186,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title27" id="incompatible_changes__incompatible_changes_123">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title28" id="incompatible_changes__incompatible_changes_123">
 
-    <h2 class="title topictitle2" id="ariaid-title27">Incompatible Changes Introduced in Impala 1.2.3</h2>
+    <h2 class="title topictitle2" id="ariaid-title28">Incompatible Changes Introduced in Impala 1.2.3</h2>
 
     <div class="body conbody">
 
@@ -1184,9 +1200,9 @@
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title28" id="incompatible_changes__incompatible_changes_122">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title29" id="incompatible_changes__incompatible_changes_122">
 
-    <h2 class="title topictitle2" id="ariaid-title28">Incompatible Changes Introduced in Impala 1.2.2</h2>
+    <h2 class="title topictitle2" id="ariaid-title29">Incompatible Changes Introduced in Impala 1.2.2</h2>
 
     <div class="body conbody">
 
@@ -1252,9 +1268,9 @@ select * from `cross`;</code></pre>
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title29" id="incompatible_changes__incompatible_changes_121">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title30" id="incompatible_changes__incompatible_changes_121">
 
-    <h2 class="title topictitle2" id="ariaid-title29">Incompatible Changes Introduced in Impala 1.2.1</h2>
+    <h2 class="title topictitle2" id="ariaid-title30">Incompatible Changes Introduced in Impala 1.2.1</h2>
 
     <div class="body conbody">
 
@@ -1321,9 +1337,9 @@ select * from `cross`;</code></pre>
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title30" id="incompatible_changes__incompatible_changes_120">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title31" id="incompatible_changes__incompatible_changes_120">
 
-    <h2 class="title topictitle2" id="ariaid-title30">Incompatible Changes Introduced in Impala 1.2.0 (Beta)</h2>
+    <h2 class="title topictitle2" id="ariaid-title31">Incompatible Changes Introduced in Impala 1.2.0 (Beta)</h2>
 
     <div class="body conbody">
 
@@ -1377,9 +1393,9 @@ select * from `cross`;</code></pre>
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title31" id="incompatible_changes__incompatible_changes_111">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title32" id="incompatible_changes__incompatible_changes_111">
 
-    <h2 class="title topictitle2" id="ariaid-title31">Incompatible Changes Introduced in Impala 1.1.1</h2>
+    <h2 class="title topictitle2" id="ariaid-title32">Incompatible Changes Introduced in Impala 1.1.1</h2>
 
     <div class="body conbody">
 
@@ -1427,9 +1443,9 @@ ALTER TABLE <var class="keyword varname">table_name</var> SET FILEFORMAT
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title32" id="incompatible_changes__incompatible_changes_11">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title33" id="incompatible_changes__incompatible_changes_11">
 
-    <h2 class="title topictitle2" id="ariaid-title32">Incompatible Change Introduced in Impala 1.1</h2>
+    <h2 class="title topictitle2" id="ariaid-title33">Incompatible Change Introduced in Impala 1.1</h2>
 
     <div class="body conbody">
 
@@ -1454,9 +1470,9 @@ ALTER TABLE <var class="keyword varname">table_name</var> SET FILEFORMAT
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title33" id="incompatible_changes__incompatible_changes_10">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title34" id="incompatible_changes__incompatible_changes_10">
 
-    <h2 class="title topictitle2" id="ariaid-title33">Incompatible Changes Introduced in Impala 1.0</h2>
+    <h2 class="title topictitle2" id="ariaid-title34">Incompatible Changes Introduced in Impala 1.0</h2>
 
     <div class="body conbody">
 

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_joins.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_joins.html b/docs/build/html/topics/impala_joins.html
index 436f9f5..b49dd3a 100644
--- a/docs/build/html/topics/impala_joins.html
+++ b/docs/build/html/topics/impala_joins.html
@@ -25,7 +25,7 @@
         are supported in all Impala versions. The <code class="ph codeph">CROSS JOIN</code> operator is available in Impala 1.2.2
         and higher. During performance tuning, you can override the reordering of join clauses that Impala does
         internally by including the keyword <code class="ph codeph">STRAIGHT_JOIN</code> immediately after the
-        <code class="ph codeph">SELECT</code> keyword
+        <code class="ph codeph">SELECT</code> and any <code class="ph codeph">DISTINCT</code> or <code class="ph codeph">ALL</code> keywords.
       </p>
 
 <pre class="pre codeblock"><code>SELECT <var class="keyword varname">select_list</var> FROM

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_known_issues.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_known_issues.html b/docs/build/html/topics/impala_known_issues.html
index f9017d2..3b148ee 100644
--- a/docs/build/html/topics/impala_known_issues.html
+++ b/docs/build/html/topics/impala_known_issues.html
@@ -209,11 +209,37 @@
 
     </div>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title11" id="known_issues_performance__IMPALA-1480">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title11" id="known_issues_performance__IMPALA-3316">
+      <h4 class="title topictitle4" id="ariaid-title11">Slow queries for Parquet tables with convert_legacy_hive_parquet_utc_timestamps=true</h4>
+      <div class="body conbody">
+        <p class="p">
+          The configuration setting <code class="ph codeph">convert_legacy_hive_parquet_utc_timestamps=true</code>
+          uses an underlying function that can be a bottleneck on high volume, highly concurrent
+          queries due to the use of a global lock while loading time zone information. This bottleneck
+          can cause slowness when querying Parquet tables, up to 30x for scan-heavy queries. The amount
+          of slowdown depends on factors such as the number of cores and number of threads involved in the query.
+        </p>
+        <div class="note note note_note"><span class="note__title notetitle">Note:</span> 
+          <p class="p">
+            The slowdown only occurs when accessing <code class="ph codeph">TIMESTAMP</code> columns within Parquet files that
+            were generated by Hive, and therefore require the on-the-fly timezone conversion processing.
+          </p>
+        </div>
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3316" target="_blank">IMPALA-3316</a></p>
+        <p class="p"><strong class="ph b">Severity:</strong> High</p>
+        <p class="p"><strong class="ph b">Workaround:</strong> If the <code class="ph codeph">TIMESTAMP</code> values stored in the table represent dates only,
+          with no time portion, consider storing them as strings in <code class="ph codeph">yyyy-MM-dd</code> format.
+          Impala implicitly converts such string values to <code class="ph codeph">TIMESTAMP</code> in calls to date/time
+          functions.
+        </p>
+      </div>
+    </article>
+
+    <article class="topic concept nested3" aria-labelledby="ariaid-title12" id="known_issues_performance__IMPALA-1480">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title11">Slow DDL statements for tables with large number of partitions</h4>
+      <h4 class="title topictitle4" id="ariaid-title12">Slow DDL statements for tables with large number of partitions</h4>
 
       <div class="body conbody">
 
@@ -235,6 +261,33 @@
 
     </article>
 
+    <article class="topic concept nested3" aria-labelledby="ariaid-title13" id="known_issues_performance__ki_file_handle_cache">
+      <h4 class="title topictitle4" id="ariaid-title13">Interaction of File Handle Cache with HDFS Appends and Short-Circuit Reads</h4>
+      <div class="body conbody">
+        <p class="p">
+          If a data file used by Impala is being continuously appended or overwritten in place by an
+          HDFS mechanism, such as <span class="keyword cmdname">hdfs dfs -appendToFile</span>, interaction with the
+          file handle caching feature in <span class="keyword">Impala 2.10</span> and higher could cause
+          short-circuit reads to sometimes be disabled on some DataNodes. When a mismatch is detected
+          between the cached file handle and a data block that was rewritten because of an append,
+          short-circuit reads are turned off on the affected host for a 10-minute period.
+        </p>
+        <p class="p">
+          The possibility of encountering such an issue is the reason why the file handle caching
+          feature is currently turned off by default. See <a class="xref" href="impala_scalability.html">Scalability Considerations for Impala</a>
+          for information about this feature and how to enable it.
+        </p>
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/HDFS-12528" target="_blank">HDFS-12528</a></p>
+        <p class="p"><strong class="ph b">Severity:</strong> High</p>
+        
+        <p class="p"><strong class="ph b">Workaround:</strong> Verify whether your ETL process is susceptible to this issue before enabling the file handle caching feature.
+          You can set the <span class="keyword cmdname">impalad</span> configuration option <code class="ph codeph">unused_file_handle_timeout_sec</code> to a time period
+          that is shorter than the HDFS setting <code class="ph codeph">dfs.client.read.shortcircuit.streams.cache.expiry.ms</code>. (Keep in mind that
+          the HDFS setting is in milliseconds while the Impala setting is in seconds.)
+        </p>
+      </div>
+    </article>
+
   </article>
 
   <article class="topic concept nested2" aria-labelledby="known_issues_usability__ki_usability" id="known_issues_crash__known_issues_usability">
@@ -249,8 +302,8 @@
 
     </div>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title13" id="known_issues_usability__IMPALA-4570">
-      <h4 class="title topictitle4" id="ariaid-title13">Impala shell tarball is not usable on systems with setuptools versions where '0.7' is a substring of the full version string</h4>
+    <article class="topic concept nested3" aria-labelledby="ariaid-title15" id="known_issues_usability__IMPALA-4570">
+      <h4 class="title topictitle4" id="ariaid-title15">Impala shell tarball is not usable on systems with setuptools versions where '0.7' is a substring of the full version string</h4>
       <div class="body conbody">
         <p class="p">
           For example, this issue could occur on a system using setuptools version 20.7.0.
@@ -264,9 +317,9 @@
       </div>
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title14" id="known_issues_usability__IMPALA-3133">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title16" id="known_issues_usability__IMPALA-3133">
 
-      <h4 class="title topictitle4" id="ariaid-title14">Unexpected privileges in show output</h4>
+      <h4 class="title topictitle4" id="ariaid-title16">Unexpected privileges in show output</h4>
 
       <div class="body conbody">
 
@@ -294,9 +347,9 @@
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title15" id="known_issues_usability__IMPALA-1776">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title17" id="known_issues_usability__IMPALA-1776">
 
-      <h4 class="title topictitle4" id="ariaid-title15">Less than 100% progress on completed simple SELECT queries</h4>
+      <h4 class="title topictitle4" id="ariaid-title17">Less than 100% progress on completed simple SELECT queries</h4>
 
       <div class="body conbody">
 
@@ -312,9 +365,9 @@
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title16" id="known_issues_usability__concept_lmx_dk5_lx">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title18" id="known_issues_usability__concept_lmx_dk5_lx">
 
-      <h4 class="title topictitle4" id="ariaid-title16">Unexpected column overflow behavior with INT datatypes</h4>
+      <h4 class="title topictitle4" id="ariaid-title18">Unexpected column overflow behavior with INT datatypes</h4>
 
       <div class="body conbody">
 
@@ -351,11 +404,11 @@
 
     </div>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title18" id="known_issues_drivers__IMPALA-1792">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title20" id="known_issues_drivers__IMPALA-1792">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title18">ImpalaODBC: Can not get the value in the SQLGetData(m-x th column) after the SQLBindCol(m th column)</h4>
+      <h4 class="title topictitle4" id="ariaid-title20">ImpalaODBC: Can not get the value in the SQLGetData(m-x th column) after the SQLBindCol(m th column)</h4>
 
       <div class="body conbody">
 
@@ -392,11 +445,32 @@
 
     </div>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title20" id="known_issues_security__renewable_kerberos_tickets">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title22" id="known_issues_security__IMPALA-5638">
+      <h4 class="title topictitle4" id="ariaid-title22">Malicious user can gain unauthorized access to Kudu table data via Impala</h4>
+      <div class="body conbody">
+        <p class="p">
+          A malicious user with <code class="ph codeph">ALTER</code> permissions on an Impala table can access any
+          other Kudu table data by altering the table properties to make it <span class="q">"external"</span>
+          and then changing the underlying table mapping to point to other Kudu tables.
+          This violates and works around the authorization requirement that creating a
+          Kudu external table via Impala requires an <code class="ph codeph">ALL</code> privilege at the server scope.
+          This privilege requirement for <code class="ph codeph">CREATE</code> commands is enforced to precisely avoid
+          this scenario where a malicious user can change the underlying Kudu table
+          mapping. The fix is to enforce the same privilege requirement for <code class="ph codeph">ALTER</code>
+          commands that would make existing non-external Kudu tables external.
+        </p>
+        <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-5638" target="_blank">IMPALA-5638</a></p>
+        <p class="p"><strong class="ph b">Severity:</strong> High</p>
+        <p class="p"><strong class="ph b">Workaround:</strong> A temporary workaround is to revoke <code class="ph codeph">ALTER</code> permissions on Impala tables.</p>
+        <p class="p"><strong class="ph b">Resolution:</strong> Upgrade to an Impala version containing the fix for <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-5638" target="_blank">IMPALA-5638</a>.</p>
+      </div>
+    </article>
+
+    <article class="topic concept nested3" aria-labelledby="ariaid-title23" id="known_issues_security__renewable_kerberos_tickets">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title20">Kerberos tickets must be renewable</h4>
+      <h4 class="title topictitle4" id="ariaid-title23">Kerberos tickets must be renewable</h4>
 
       <div class="body conbody">
 
@@ -432,8 +506,8 @@
 
     </div>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title22" id="known_issues_resources__IMPALA-5605">
-      <h4 class="title topictitle4" id="ariaid-title22">Configuration to prevent crashes caused by thread resource limits</h4>
+    <article class="topic concept nested3" aria-labelledby="ariaid-title25" id="known_issues_resources__IMPALA-5605">
+      <h4 class="title topictitle4" id="ariaid-title25">Configuration to prevent crashes caused by thread resource limits</h4>
       <div class="body conbody">
         <p class="p">
           Impala could encounter a serious error due to resource usage under very high concurrency.
@@ -465,8 +539,8 @@ impala hard nproc 262144
       </div>
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title23" id="known_issues_resources__flatbuffers_mem_usage">
-      <h4 class="title topictitle4" id="ariaid-title23">Memory usage when compact_catalog_topic flag enabled</h4>
+    <article class="topic concept nested3" aria-labelledby="ariaid-title26" id="known_issues_resources__flatbuffers_mem_usage">
+      <h4 class="title topictitle4" id="ariaid-title26">Memory usage when compact_catalog_topic flag enabled</h4>
       <div class="body conbody">
         <p class="p">
           The efficiency improvement from <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-4029" target="_blank">IMPALA-4029</a>
@@ -491,8 +565,8 @@ impala hard nproc 262144
       </div>
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title24" id="known_issues_resources__IMPALA-2294">
-      <h4 class="title topictitle4" id="ariaid-title24">Kerberos initialization errors due to high memory usage</h4>
+    <article class="topic concept nested3" aria-labelledby="ariaid-title27" id="known_issues_resources__IMPALA-2294">
+      <h4 class="title topictitle4" id="ariaid-title27">Kerberos initialization errors due to high memory usage</h4>
       <div class="body conbody">
         <div class="p">
         On a kerberized cluster with high memory utilization, <span class="keyword cmdname">kinit</span> commands executed after
@@ -529,8 +603,8 @@ vm.overcommit_memory=1
       </div>
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title25" id="known_issues_resources__drop_table_purge_s3a">
-      <h4 class="title topictitle4" id="ariaid-title25">DROP TABLE PURGE on S3A table may not delete externally written files</h4>
+    <article class="topic concept nested3" aria-labelledby="ariaid-title28" id="known_issues_resources__drop_table_purge_s3a">
+      <h4 class="title topictitle4" id="ariaid-title28">DROP TABLE PURGE on S3A table may not delete externally written files</h4>
       <div class="body conbody">
         <p class="p">
           A <code class="ph codeph">DROP TABLE PURGE</code> statement against an S3 table could leave the data files
@@ -543,9 +617,9 @@ vm.overcommit_memory=1
       </div>
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title26" id="known_issues_resources__catalogd_heap">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title29" id="known_issues_resources__catalogd_heap">
 
-      <h4 class="title topictitle4" id="ariaid-title26">Impala catalogd heap issues when upgrading to <span class="keyword">Impala 2.5</span></h4>
+      <h4 class="title topictitle4" id="ariaid-title29">Impala catalogd heap issues when upgrading to <span class="keyword">Impala 2.5</span></h4>
 
       <div class="body conbody">
 
@@ -628,9 +702,9 @@ vm.overcommit_memory=1
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title27" id="known_issues_resources__IMPALA-3509">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title30" id="known_issues_resources__IMPALA-3509">
 
-      <h4 class="title topictitle4" id="ariaid-title27">Breakpad minidumps can be very large when the thread count is high</h4>
+      <h4 class="title topictitle4" id="ariaid-title30">Breakpad minidumps can be very large when the thread count is high</h4>
 
       <div class="body conbody">
 
@@ -659,9 +733,9 @@ vm.overcommit_memory=1
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title28" id="known_issues_resources__IMPALA-3662">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title31" id="known_issues_resources__IMPALA-3662">
 
-      <h4 class="title topictitle4" id="ariaid-title28">Parquet scanner memory increase after IMPALA-2736</h4>
+      <h4 class="title topictitle4" id="ariaid-title31">Parquet scanner memory increase after IMPALA-2736</h4>
 
       <div class="body conbody">
 
@@ -725,9 +799,9 @@ vm.overcommit_memory=1
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title29" id="known_issues_resources__IMPALA-691">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title32" id="known_issues_resources__IMPALA-691">
 
-      <h4 class="title topictitle4" id="ariaid-title29">Process mem limit does not account for the JVM's memory usage</h4>
+      <h4 class="title topictitle4" id="ariaid-title32">Process mem limit does not account for the JVM's memory usage</h4>
 
 
 
@@ -751,11 +825,11 @@ vm.overcommit_memory=1
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title30" id="known_issues_resources__IMPALA-2375">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title33" id="known_issues_resources__IMPALA-2375">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title30">Fix issues with the legacy join and agg nodes using --enable_partitioned_hash_join=false and --enable_partitioned_aggregation=false</h4>
+      <h4 class="title topictitle4" id="ariaid-title33">Fix issues with the legacy join and agg nodes using --enable_partitioned_hash_join=false and --enable_partitioned_aggregation=false</h4>
 
       <div class="body conbody">
 
@@ -789,8 +863,8 @@ vm.overcommit_memory=1
 
     </div>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title32" id="known_issues_correctness__IMPALA-4513">
-      <h4 class="title topictitle4" id="ariaid-title32">ABS(n) where n is the lowest bound for the int types returns negative values</h4>
+    <article class="topic concept nested3" aria-labelledby="ariaid-title35" id="known_issues_correctness__IMPALA-4513">
+      <h4 class="title topictitle4" id="ariaid-title35">ABS(n) where n is the lowest bound for the int types returns negative values</h4>
       <div class="body conbody">
         <p class="p">
           If the <code class="ph codeph">abs()</code> function evaluates a number that is right at the lower bound for
@@ -806,8 +880,8 @@ vm.overcommit_memory=1
       </div>
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title33" id="known_issues_correctness__IMPALA-4266">
-      <h4 class="title topictitle4" id="ariaid-title33">Java udf expression returning string in group by can give incorrect results.</h4>
+    <article class="topic concept nested3" aria-labelledby="ariaid-title36" id="known_issues_correctness__IMPALA-4266">
+      <h4 class="title topictitle4" id="ariaid-title36">Java udf expression returning string in group by can give incorrect results.</h4>
       <div class="body conbody">
         <p class="p">
           If the <code class="ph codeph">GROUP BY</code> clause included a call to a Java UDF that returned a string value,
@@ -823,9 +897,9 @@ vm.overcommit_memory=1
       </div>
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title34" id="known_issues_correctness__IMPALA-3084">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title37" id="known_issues_correctness__IMPALA-3084">
 
-      <h4 class="title topictitle4" id="ariaid-title34">Incorrect assignment of NULL checking predicate through an outer join of a nested collection.</h4>
+      <h4 class="title topictitle4" id="ariaid-title37">Incorrect assignment of NULL checking predicate through an outer join of a nested collection.</h4>
 
       <div class="body conbody">
 
@@ -849,9 +923,9 @@ vm.overcommit_memory=1
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title35" id="known_issues_correctness__IMPALA-3094">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title38" id="known_issues_correctness__IMPALA-3094">
 
-      <h4 class="title topictitle4" id="ariaid-title35">Incorrect result due to constant evaluation in query with outer join</h4>
+      <h4 class="title topictitle4" id="ariaid-title38">Incorrect result due to constant evaluation in query with outer join</h4>
 
       <div class="body conbody">
 
@@ -894,9 +968,9 @@ explain SELECT 1 FROM alltypestiny a1
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title36" id="known_issues_correctness__IMPALA-3126">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title39" id="known_issues_correctness__IMPALA-3126">
 
-      <h4 class="title topictitle4" id="ariaid-title36">Incorrect assignment of an inner join On-clause predicate through an outer join.</h4>
+      <h4 class="title topictitle4" id="ariaid-title39">Incorrect assignment of an inner join On-clause predicate through an outer join.</h4>
 
       <div class="body conbody">
 
@@ -1072,9 +1146,9 @@ where b.int_col = c.int_col
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title37" id="known_issues_correctness__IMPALA-3006">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title40" id="known_issues_correctness__IMPALA-3006">
 
-      <h4 class="title topictitle4" id="ariaid-title37">Impala may use incorrect bit order with BIT_PACKED encoding</h4>
+      <h4 class="title topictitle4" id="ariaid-title40">Impala may use incorrect bit order with BIT_PACKED encoding</h4>
 
       <div class="body conbody">
 
@@ -1095,9 +1169,9 @@ where b.int_col = c.int_col
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title38" id="known_issues_correctness__IMPALA-3082">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title41" id="known_issues_correctness__IMPALA-3082">
 
-      <h4 class="title topictitle4" id="ariaid-title38">BST between 1972 and 1995</h4>
+      <h4 class="title topictitle4" id="ariaid-title41">BST between 1972 and 1995</h4>
 
       <div class="body conbody">
 
@@ -1126,9 +1200,9 @@ select
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title39" id="known_issues_correctness__IMPALA-1170">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title42" id="known_issues_correctness__IMPALA-1170">
 
-      <h4 class="title topictitle4" id="ariaid-title39">parse_url() returns incorrect result if @ character in URL</h4>
+      <h4 class="title topictitle4" id="ariaid-title42">parse_url() returns incorrect result if @ character in URL</h4>
 
       <div class="body conbody">
 
@@ -1147,9 +1221,9 @@ select
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title40" id="known_issues_correctness__IMPALA-2422">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title43" id="known_issues_correctness__IMPALA-2422">
 
-      <h4 class="title topictitle4" id="ariaid-title40">% escaping does not work correctly when occurs at the end in a LIKE clause</h4>
+      <h4 class="title topictitle4" id="ariaid-title43">% escaping does not work correctly when occurs at the end in a LIKE clause</h4>
 
       <div class="body conbody">
 
@@ -1166,9 +1240,9 @@ select
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title41" id="known_issues_correctness__IMPALA-397">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title44" id="known_issues_correctness__IMPALA-397">
 
-      <h4 class="title topictitle4" id="ariaid-title41">ORDER BY rand() does not work.</h4>
+      <h4 class="title topictitle4" id="ariaid-title44">ORDER BY rand() does not work.</h4>
 
       <div class="body conbody">
 
@@ -1185,9 +1259,9 @@ select
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title42" id="known_issues_correctness__IMPALA-2643">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title45" id="known_issues_correctness__IMPALA-2643">
 
-      <h4 class="title topictitle4" id="ariaid-title42">Duplicated column in inline view causes dropping null slots during scan</h4>
+      <h4 class="title topictitle4" id="ariaid-title45">Duplicated column in inline view causes dropping null slots during scan</h4>
 
       <div class="body conbody">
 
@@ -1210,11 +1284,11 @@ select
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title43" id="known_issues_correctness__IMPALA-1459">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title46" id="known_issues_correctness__IMPALA-1459">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title43">Incorrect assignment of predicates through an outer join in an inline view.</h4>
+      <h4 class="title topictitle4" id="ariaid-title46">Incorrect assignment of predicates through an outer join in an inline view.</h4>
 
       <div class="body conbody">
 
@@ -1233,9 +1307,9 @@ select
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title44" id="known_issues_correctness__IMPALA-2603">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title47" id="known_issues_correctness__IMPALA-2603">
 
-      <h4 class="title topictitle4" id="ariaid-title44">Crash: impala::Coordinator::ValidateCollectionSlots</h4>
+      <h4 class="title topictitle4" id="ariaid-title47">Crash: impala::Coordinator::ValidateCollectionSlots</h4>
 
       <div class="body conbody">
 
@@ -1252,9 +1326,9 @@ select
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title45" id="known_issues_correctness__IMPALA-2665">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title48" id="known_issues_correctness__IMPALA-2665">
 
-      <h4 class="title topictitle4" id="ariaid-title45">Incorrect assignment of On-clause predicate inside inline view with an outer join.</h4>
+      <h4 class="title topictitle4" id="ariaid-title48">Incorrect assignment of On-clause predicate inside inline view with an outer join.</h4>
 
       <div class="body conbody">
 
@@ -1287,9 +1361,9 @@ select
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title46" id="known_issues_correctness__IMPALA-2144">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title49" id="known_issues_correctness__IMPALA-2144">
 
-      <h4 class="title topictitle4" id="ariaid-title46">Wrong assignment of having clause predicate across outer join</h4>
+      <h4 class="title topictitle4" id="ariaid-title49">Wrong assignment of having clause predicate across outer join</h4>
 
       <div class="body conbody">
 
@@ -1308,9 +1382,9 @@ select
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title47" id="known_issues_correctness__IMPALA-2093">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title50" id="known_issues_correctness__IMPALA-2093">
 
-      <h4 class="title topictitle4" id="ariaid-title47">Wrong plan of NOT IN aggregate subquery when a constant is used in subquery predicate</h4>
+      <h4 class="title topictitle4" id="ariaid-title50">Wrong plan of NOT IN aggregate subquery when a constant is used in subquery predicate</h4>
 
       <div class="body conbody">
 
@@ -1344,9 +1418,9 @@ select
 
     </div>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title49" id="known_issues_metadata__IMPALA-2648">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title52" id="known_issues_metadata__IMPALA-2648">
 
-      <h4 class="title topictitle4" id="ariaid-title49">Catalogd may crash when loading metadata for tables with many partitions, many columns and with incremental stats</h4>
+      <h4 class="title topictitle4" id="ariaid-title52">Catalogd may crash when loading metadata for tables with many partitions, many columns and with incremental stats</h4>
 
       <div class="body conbody">
 
@@ -1371,11 +1445,11 @@ select
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title50" id="known_issues_metadata__IMPALA-1420">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title53" id="known_issues_metadata__IMPALA-1420">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title50">Can't update stats manually via alter table after upgrading to <span class="keyword">Impala 2.0</span></h4>
+      <h4 class="title topictitle4" id="ariaid-title53">Can't update stats manually via alter table after upgrading to <span class="keyword">Impala 2.0</span></h4>
 
       <div class="body conbody">
 
@@ -1420,9 +1494,9 @@ select
 
 
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title52" id="known_issues_interop__describe_formatted_avro">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title55" id="known_issues_interop__describe_formatted_avro">
 
-      <h4 class="title topictitle4" id="ariaid-title52">DESCRIBE FORMATTED gives error on Avro table</h4>
+      <h4 class="title topictitle4" id="ariaid-title55">DESCRIBE FORMATTED gives error on Avro table</h4>
 
       <div class="body conbody">
 
@@ -1454,11 +1528,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title53" id="known_issues_interop__IMP-469">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title56" id="known_issues_interop__IMP-469">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title53">Deviation from Hive behavior: Impala does not do implicit casts between string and numeric and boolean types.</h4>
+      <h4 class="title topictitle4" id="ariaid-title56">Deviation from Hive behavior: Impala does not do implicit casts between string and numeric and boolean types.</h4>
 
       <div class="body conbody">
 
@@ -1474,11 +1548,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title54" id="known_issues_interop__IMP-175">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title57" id="known_issues_interop__IMP-175">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title54">Deviation from Hive behavior: Out of range values float/double values are returned as maximum allowed value of type (Hive returns NULL)</h4>
+      <h4 class="title topictitle4" id="ariaid-title57">Deviation from Hive behavior: Out of range values float/double values are returned as maximum allowed value of type (Hive returns NULL)</h4>
 
       <div class="body conbody">
 
@@ -1495,11 +1569,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title55" id="known_issues_interop__flume_writeformat_text">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title58" id="known_issues_interop__flume_writeformat_text">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title55">Configuration needed for Flume to be compatible with Impala</h4>
+      <h4 class="title topictitle4" id="ariaid-title58">Configuration needed for Flume to be compatible with Impala</h4>
 
       <div class="body conbody">
 
@@ -1518,11 +1592,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title56" id="known_issues_interop__IMPALA-635">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title59" id="known_issues_interop__IMPALA-635">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title56">Avro Scanner fails to parse some schemas</h4>
+      <h4 class="title topictitle4" id="ariaid-title59">Avro Scanner fails to parse some schemas</h4>
 
       <div class="body conbody">
 
@@ -1548,11 +1622,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title57" id="known_issues_interop__IMPALA-1024">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title60" id="known_issues_interop__IMPALA-1024">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title57">Impala BE cannot parse Avro schema that contains a trailing semi-colon</h4>
+      <h4 class="title topictitle4" id="ariaid-title60">Impala BE cannot parse Avro schema that contains a trailing semi-colon</h4>
 
       <div class="body conbody">
 
@@ -1572,11 +1646,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title58" id="known_issues_interop__IMPALA-2154">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title61" id="known_issues_interop__IMPALA-2154">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title58">Fix decompressor to allow parsing gzips with multiple streams</h4>
+      <h4 class="title topictitle4" id="ariaid-title61">Fix decompressor to allow parsing gzips with multiple streams</h4>
 
       <div class="body conbody">
 
@@ -1599,11 +1673,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title59" id="known_issues_interop__IMPALA-1578">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title62" id="known_issues_interop__IMPALA-1578">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title59">Impala incorrectly handles text data when the new line character \n\r is split between different HDFS block</h4>
+      <h4 class="title topictitle4" id="ariaid-title62">Impala incorrectly handles text data when the new line character \n\r is split between different HDFS block</h4>
 
       <div class="body conbody">
 
@@ -1626,11 +1700,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title60" id="known_issues_interop__IMPALA-1862">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title63" id="known_issues_interop__IMPALA-1862">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title60">Invalid bool value not reported as a scanner error</h4>
+      <h4 class="title topictitle4" id="ariaid-title63">Invalid bool value not reported as a scanner error</h4>
 
       <div class="body conbody">
 
@@ -1648,11 +1722,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title61" id="known_issues_interop__IMPALA-1652">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title64" id="known_issues_interop__IMPALA-1652">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title61">Incorrect results with basic predicate on CHAR typed column.</h4>
+      <h4 class="title topictitle4" id="ariaid-title64">Incorrect results with basic predicate on CHAR typed column.</h4>
 
       <div class="body conbody">
 
@@ -1676,9 +1750,9 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
   </article>
 
-  <article class="topic concept nested2" aria-labelledby="ariaid-title62" id="known_issues_crash__known_issues_limitations">
+  <article class="topic concept nested2" aria-labelledby="ariaid-title65" id="known_issues_crash__known_issues_limitations">
 
-    <h3 class="title topictitle3" id="ariaid-title62">Impala Known Issues: Limitations</h3>
+    <h3 class="title topictitle3" id="ariaid-title65">Impala Known Issues: Limitations</h3>
 
     <div class="body conbody">
 
@@ -1689,8 +1763,8 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </div>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title63" id="known_issues_limitations__IMPALA-4551">
-      <h4 class="title topictitle4" id="ariaid-title63">Set limits on size of expression trees</h4>
+    <article class="topic concept nested3" aria-labelledby="ariaid-title66" id="known_issues_limitations__IMPALA-4551">
+      <h4 class="title topictitle4" id="ariaid-title66">Set limits on size of expression trees</h4>
       <div class="body conbody">
         <p class="p">
           Very deeply nested expressions within queries can exceed internal Impala limits,
@@ -1704,11 +1778,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
       </div>
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title64" id="known_issues_limitations__IMPALA-77">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title67" id="known_issues_limitations__IMPALA-77">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title64">Impala does not support running on clusters with federated namespaces</h4>
+      <h4 class="title topictitle4" id="ariaid-title67">Impala does not support running on clusters with federated namespaces</h4>
 
       <div class="body conbody">
 
@@ -1735,9 +1809,9 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
   </article>
 
-  <article class="topic concept nested2" aria-labelledby="ariaid-title65" id="known_issues_crash__known_issues_misc">
+  <article class="topic concept nested2" aria-labelledby="ariaid-title68" id="known_issues_crash__known_issues_misc">
 
-    <h3 class="title topictitle3" id="ariaid-title65">Impala Known Issues: Miscellaneous / Older Issues</h3>
+    <h3 class="title topictitle3" id="ariaid-title68">Impala Known Issues: Miscellaneous / Older Issues</h3>
 
     <div class="body conbody">
 
@@ -1747,11 +1821,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </div>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title66" id="known_issues_misc__IMPALA-2005">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title69" id="known_issues_misc__IMPALA-2005">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title66">A failed CTAS does not drop the table if the insert fails.</h4>
+      <h4 class="title topictitle4" id="ariaid-title69">A failed CTAS does not drop the table if the insert fails.</h4>
 
       <div class="body conbody">
 
@@ -1772,11 +1846,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title67" id="known_issues_misc__IMPALA-1821">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title70" id="known_issues_misc__IMPALA-1821">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title67">Casting scenarios with invalid/inconsistent results</h4>
+      <h4 class="title topictitle4" id="ariaid-title70">Casting scenarios with invalid/inconsistent results</h4>
 
       <div class="body conbody">
 
@@ -1796,11 +1870,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title68" id="known_issues_misc__IMPALA-1619">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title71" id="known_issues_misc__IMPALA-1619">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title68">Support individual memory allocations larger than 1 GB</h4>
+      <h4 class="title topictitle4" id="ariaid-title71">Support individual memory allocations larger than 1 GB</h4>
 
       <div class="body conbody">
 
@@ -1820,11 +1894,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title69" id="known_issues_misc__IMPALA-941">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title72" id="known_issues_misc__IMPALA-941">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title69">Impala Parser issue when using fully qualified table names that start with a number.</h4>
+      <h4 class="title topictitle4" id="ariaid-title72">Impala Parser issue when using fully qualified table names that start with a number.</h4>
 
       <div class="body conbody">
 
@@ -1845,11 +1919,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title70" id="known_issues_misc__IMPALA-532">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title73" id="known_issues_misc__IMPALA-532">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title70">Impala should tolerate bad locale settings</h4>
+      <h4 class="title topictitle4" id="ariaid-title73">Impala should tolerate bad locale settings</h4>
 
       <div class="body conbody">
 
@@ -1874,11 +1948,11 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </article>
 
-    <article class="topic concept nested3" aria-labelledby="ariaid-title71" id="known_issues_misc__IMP-1203">
+    <article class="topic concept nested3" aria-labelledby="ariaid-title74" id="known_issues_misc__IMP-1203">
 
 
 
-      <h4 class="title topictitle4" id="ariaid-title71">Log Level 3 Not Recommended for Impala</h4>
+      <h4 class="title topictitle4" id="ariaid-title74">Log Level 3 Not Recommended for Impala</h4>
 
       <div class="body conbody">
 

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_kudu.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_kudu.html b/docs/build/html/topics/impala_kudu.html
index 1ede7b6..d610595 100644
--- a/docs/build/html/topics/impala_kudu.html
+++ b/docs/build/html/topics/impala_kudu.html
@@ -1389,6 +1389,14 @@ kudu.table_name  | impala::some_database.table_name_demo
         the predicate pushdown for a specific query against a Kudu table.
       </p>
 
+      <p class="p">
+        The <code class="ph codeph">TABLESAMPLE</code> clause of the <code class="ph codeph">SELECT</code>
+        statement does not apply to a table reference derived from a view, a subquery,
+        or anything other than a real base table. This clause only works for tables
+        backed by HDFS or HDFS-like data files, therefore it does not apply to Kudu or
+        HBase tables.
+      </p>
+
       
       
 

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_logging.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_logging.html b/docs/build/html/topics/impala_logging.html
index 1882468..995c817 100644
--- a/docs/build/html/topics/impala_logging.html
+++ b/docs/build/html/topics/impala_logging.html
@@ -341,8 +341,7 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we
       <p class="p">
         For more information on how to configure GLOG, including how to set variable logging levels for different
         system components, see
-        <a class="xref" href="http://google-glog.googlecode.com/svn/trunk/doc/glog.html" target="_blank">How
-        To Use Google Logging Library (glog)</a>.
+        <a class="xref" href="https://github.com/google/glog" target="_blank">documentation for the glog project on github</a>.
       </p>
 
       <section class="section" id="log_levels__loglevels_details"><h3 class="title sectiontitle">Understanding What is Logged at Different Logging Levels</h3>

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_map.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_map.html b/docs/build/html/topics/impala_map.html
index 96cd2e8..17a1c25 100644
--- a/docs/build/html/topics/impala_map.html
+++ b/docs/build/html/topics/impala_map.html
@@ -102,7 +102,7 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
           </p>
         </li>
         <li class="li">
-          <p class="p" id="map__d6e3003">
+          <p class="p" id="map__d6e3156">
             The maximum length of the column definition for any complex type, including declarations for any nested types,
             is 4000 characters.
           </p>

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_math_functions.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_math_functions.html b/docs/build/html/topics/impala_math_functions.html
index 431e6c3..ce10a98 100644
--- a/docs/build/html/topics/impala_math_functions.html
+++ b/docs/build/html/topics/impala_math_functions.html
@@ -1413,66 +1413,209 @@ select x, unix_timestamp(now()), rand(unix_timestamp(now()))
 
         <dt class="dt dlterm" id="math_functions__truncate">
           <code class="ph codeph">truncate(double_or_decimal a[, digits_to_leave])</code>,
-          <span class="ph" id="math_functions__dtrunc"><code class="ph codeph">dtrunc(double_or_decimal a[, digits_to_leave])</code></span>
+          <span class="ph" id="math_functions__dtrunc"><code class="ph codeph">dtrunc(double_or_decimal a[, digits_to_leave])</code></span>,
+          <span class="ph" id="math_functions__trunc_number"><code class="ph codeph">trunc(double_or_decimal a[, digits_to_leave])</code></span>
         </dt>
 
         <dd class="dd">
           
           
+          
           <strong class="ph b">Purpose:</strong> Removes some or all fractional digits from a numeric value.
-          With no argument, removes all fractional digits, leaving an integer value.
-          The optional argument specifies the number of fractional digits to include
-          in the return value, and only applies with the argument type is <code class="ph codeph">DECIMAL</code>.
-          <code class="ph codeph">truncate()</code> and <code class="ph codeph">dtrunc()</code> are aliases for the same function.
+          <p class="p">
+            <strong class="ph b">Arguments:</strong>
+            With a single floating-point argument, removes all fractional digits, leaving an
+            integer value. The optional second argument specifies the number of fractional digits
+            to include in the return value, and only applies when the argument type is
+            <code class="ph codeph">DECIMAL</code>. A second argument of 0 truncates to a whole integer value.
+            A second argument of negative N sets N digits to 0 on the left side of the decimal
+          </p>
+          <p class="p">
+            <strong class="ph b">Scale argument:</strong> The scale argument applies only when truncating
+            <code class="ph codeph">DECIMAL</code> values. It is an integer specifying how many
+            significant digits to leave to the right of the decimal point.
+            A scale argument of 0 truncates to a whole integer value. A scale
+            argument of negative N sets N digits to 0 on the left side of the decimal
+            point.
+          </p>
+          <p class="p">
+            <code class="ph codeph">truncate()</code>, <code class="ph codeph">dtrunc()</code>,
+            <span class="ph">and <code class="ph codeph">trunc()</code></span> are aliases for the
+            same function.
+          </p>
           <p class="p">
             <strong class="ph b">Return type:</strong> <code class="ph codeph">decimal</code> for <code class="ph codeph">DECIMAL</code> arguments;
             <code class="ph codeph">bigint</code> for <code class="ph codeph">DOUBLE</code> arguments
           </p>
           <p class="p">
+            <strong class="ph b">Added in:</strong> The <code class="ph codeph">trunc()</code> alias was added in
+            <span class="keyword">Impala 2.10</span>.
+          </p>
+          <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+          <p class="p">
+            You can also pass a <code class="ph codeph">DOUBLE</code> argument, or <code class="ph codeph">DECIMAL</code>
+            argument with optional scale, to the <code class="ph codeph">dtrunc()</code> or
+            <code class="ph codeph">truncate</code> functions. Using the <code class="ph codeph">trunc()</code>
+            function for numeric values is common with other industry-standard database
+            systems, so you might find such <code class="ph codeph">trunc()</code> calls in code that you
+            are porting to Impala.
+          </p>
+          <p class="p">
+            The <code class="ph codeph">trunc()</code> function also has a signature that applies to
+            <code class="ph codeph">TIMESTAMP</code> values. See <a class="xref" href="impala_datetime_functions.html">Impala Date and Time Functions</a>
+            for details.
+          </p>
+          <p class="p">
         <strong class="ph b">Examples:</strong>
       </p>
-<pre class="pre codeblock"><code>select truncate(3.45)
+          <p class="p">
+            The following examples demonstrate the <code class="ph codeph">truncate()</code>
+            and <code class="ph codeph">dtrunc()</code> signatures for this function:
+          </p>
+<pre class="pre codeblock"><code>select truncate(3.45);
 +----------------+
 | truncate(3.45) |
 +----------------+
 | 3              |
 +----------------+
 
-select truncate(-3.45)
+select truncate(-3.45);
 +-----------------+
 | truncate(-3.45) |
 +-----------------+
 | -3              |
 +-----------------+
 
-select truncate(3.456,1)
+select truncate(3.456,1);
 +--------------------+
 | truncate(3.456, 1) |
 +--------------------+
 | 3.4                |
 +--------------------+
 
-select dtrunc(3.456,1)
+select dtrunc(3.456,1);
 +------------------+
 | dtrunc(3.456, 1) |
 +------------------+
 | 3.4              |
 +------------------+
 
-select truncate(3.456,2)
+select truncate(3.456,2);
 +--------------------+
 | truncate(3.456, 2) |
 +--------------------+
 | 3.45               |
 +--------------------+
 
-select truncate(3.456,7)
+select truncate(3.456,7);
 +--------------------+
 | truncate(3.456, 7) |
 +--------------------+
 | 3.4560000          |
 +--------------------+
 </code></pre>
+          <p class="p">
+            The following examples demonstrate using <code class="ph codeph">trunc()</code> with
+            <code class="ph codeph">DECIMAL</code> or <code class="ph codeph">DOUBLE</code> values, and with
+            an optional scale argument for <code class="ph codeph">DECIMAL</code> values.
+            (The behavior is the same for the <code class="ph codeph">truncate()</code> and
+            <code class="ph codeph">dtrunc()</code> aliases also.)
+          </p>
+<pre class="pre codeblock"><code>
+create table t1 (d decimal(20,7));
+
+-- By default, no digits to the right of the decimal point.
+insert into t1 values (1.1), (2.22), (3.333), (4.4444), (5.55555);
+select trunc(d) from t1 order by d;
++----------+
+| trunc(d) |
++----------+
+| 1        |
+| 2        |
+| 3        |
+| 4        |
+| 5        |
++----------+
+
+-- 1 digit to the right of the decimal point.
+select trunc(d,1) from t1 order by d;
++-------------+
+| trunc(d, 1) |
++-------------+
+| 1.1         |
+| 2.2         |
+| 3.3         |
+| 4.4         |
+| 5.5         |
++-------------+
+
+-- 2 digits to the right of the decimal point,
+-- including trailing zeroes if needed.
+select trunc(d,2) from t1 order by d;
++-------------+
+| trunc(d, 2) |
++-------------+
+| 1.10        |
+| 2.22        |
+| 3.33        |
+| 4.44        |
+| 5.55        |
++-------------+
+
+insert into t1 values (9999.9999), (8888.8888);
+
+-- Negative scale truncates digits to the left
+-- of the decimal point.
+select trunc(d,-2) from t1 where d &gt; 100 order by d;
++--------------+
+| trunc(d, -2) |
++--------------+
+| 8800         |
+| 9900         |
++--------------+
+
+-- The scale of the result is adjusted to match the
+-- scale argument.
+select trunc(d,2),
+  precision(trunc(d,2)) as p,
+  scale(trunc(d,2)) as s
+from t1 order by d;
++-------------+----+---+
+| trunc(d, 2) | p  | s |
++-------------+----+---+
+| 1.10        | 15 | 2 |
+| 2.22        | 15 | 2 |
+| 3.33        | 15 | 2 |
+| 4.44        | 15 | 2 |
+| 5.55        | 15 | 2 |
+| 8888.88     | 15 | 2 |
+| 9999.99     | 15 | 2 |
++-------------+----+---+
+</code></pre>
+
+<pre class="pre codeblock"><code>
+create table dbl (d double);
+
+insert into dbl values
+  (1.1), (2.22), (3.333), (4.4444), (5.55555),
+  (8888.8888), (9999.9999);
+
+-- With double values, there is no optional scale argument.
+select trunc(d) from dbl order by d;
++----------+
+| trunc(d) |
++----------+
+| 1        |
+| 2        |
+| 3        |
+| 4        |
+| 5        |
+| 8888     |
+| 9999     |
++----------+
+</code></pre>
         </dd>
 
       

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_max_row_size.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_max_row_size.html b/docs/build/html/topics/impala_max_row_size.html
new file mode 100644
index 0000000..49b3198
--- /dev/null
+++ b/docs/build/html/topics/impala_max_row_size.html
@@ -0,0 +1,221 @@
+<!DOCTYPE html
+  SYSTEM "about:legacy-compat">
+<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_query_options.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="max_row_size"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>MAX_ROW_SIZE Query Option</title></head><body id="max_row_size"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
+
+  <h1 class="title topictitle1" id="ariaid-title1">MAX_ROW_SIZE Query Option</h1>
+  
+  
+
+  <div class="body conbody">
+
+    <p class="p">
+      
+      Ensures that Impala can process rows of at least the specified size. (Larger
+      rows might be successfully processed, but that is not guaranteed.) Applies when
+      constructing intermediate or final rows in the result set. This setting prevents
+      out-of-control memory use when accessing columns containing huge strings.
+    </p>
+
+
+
+    <p class="p">
+        <strong class="ph b">Type:</strong> integer
+      </p>
+
+    <p class="p">
+        <strong class="ph b">Default:</strong>
+      </p>
+    <p class="p">
+      <code class="ph codeph">524288</code> (512 KB)
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Units:</strong> A numeric argument represents a size in bytes; you can also use a suffix of <code class="ph codeph">m</code>
+        or <code class="ph codeph">mb</code> for megabytes, or <code class="ph codeph">g</code> or <code class="ph codeph">gb</code> for gigabytes. If you
+        specify a value with unrecognized formats, subsequent queries fail with an error.
+      </p>
+
+    <p class="p">
+        <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.10.0</span>
+      </p>
+
+    <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+    <p class="p">
+      If a query fails because it involves rows with long strings and/or
+      many columns, causing the total row size to exceed <code class="ph codeph">MAX_ROW_SIZE</code>
+      bytes, increase the <code class="ph codeph">MAX_ROW_SIZE</code> setting to accommodate
+      the total bytes stored in the largest row. Examine the error messages for any
+      failed queries to see the size of the row that caused the problem.
+    </p>
+    <p class="p">
+      Impala attempts to handle rows that exceed the <code class="ph codeph">MAX_ROW_SIZE</code>
+      value where practical, so in many cases, queries succeed despite having rows
+      that are larger than this setting.
+    </p>
+    <p class="p">
+      Specifying a value that is substantially higher than actually needed can cause
+      Impala to reserve more memory than is necessary to execute the query.
+    </p>
+    <p class="p">
+      In a Hadoop cluster with highly concurrent workloads and queries that process
+      high volumes of data, traditional SQL tuning advice about minimizing wasted memory
+      is worth remembering. For example, if a table has <code class="ph codeph">STRING</code> columns
+      where a single value might be multiple megabytes, make sure that the
+      <code class="ph codeph">SELECT</code> lists in queries only refer to columns that are actually
+      needed in the result set, instead of using the <code class="ph codeph">SELECT *</code> shorthand.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+
+    <p class="p">
+      The following examples show the kinds of situations where it is necessary to
+      adjust the <code class="ph codeph">MAX_ROW_SIZE</code> setting. First, we create a table
+      containing some very long values in <code class="ph codeph">STRING</code> columns:
+    </p>
+
+<pre class="pre codeblock"><code>
+create table big_strings (s1 string, s2 string, s3 string) stored as parquet;
+
+-- Turn off compression to more easily reason about data volume by doing SHOW TABLE STATS.
+-- Does not actually affect query success or failure, because MAX_ROW_SIZE applies when
+-- column values are materialized in memory.
+set compression_codec=none;
+set;
+...
+  MAX_ROW_SIZE: [524288]
+...
+
+-- A very small row.
+insert into big_strings values ('one', 'two', 'three');
+-- A row right around the default MAX_ROW_SIZE limit: a 500 KiB string and a 30 KiB string.
+insert into big_strings values (repeat('12345',100000), 'short', repeat('123',10000));
+-- A row that is too big if the query has to materialize both S1 and S3.
+insert into big_strings values (repeat('12345',100000), 'short', repeat('12345',100000));
+
+</code></pre>
+
+    <p class="p">
+      With the default <code class="ph codeph">MAX_ROW_SIZE</code> setting, different queries succeed
+      or fail based on which column values have to be materialized during query processing:
+    </p>
+
+<pre class="pre codeblock"><code>
+-- All the S1 values can be materialized within the 512 KB MAX_ROW_SIZE buffer.
+select count(distinct s1) from big_strings;
++--------------------+
+| count(distinct s1) |
++--------------------+
+| 2                  |
++--------------------+
+
+-- A row where even the S1 value is too large to materialize within MAX_ROW_SIZE.
+insert into big_strings values (repeat('12345',1000000), 'short', repeat('12345',1000000));
+
+-- The 5 MiB string is too large to materialize. The message explains the size of the result
+-- set row the query is attempting to materialize.
+select count(distinct(s1)) from big_strings;
+WARNINGS: Row of size 4.77 MB could not be materialized in plan node with id 1.
+  Increase the max_row_size query option (currently 512.00 KB) to process larger rows.
+
+-- If more columns are involved, the result set row being materialized is bigger.
+select count(distinct s1, s2, s3) from big_strings;
+WARNINGS: Row of size 9.54 MB could not be materialized in plan node with id 1.
+  Increase the max_row_size query option (currently 512.00 KB) to process larger rows.
+
+-- Column S2, containing only short strings, can still be examined.
+select count(distinct(s2)) from big_strings;
++----------------------+
+| count(distinct (s2)) |
++----------------------+
+| 2                    |
++----------------------+
+
+-- Queries that do not materialize the big column values are OK.
+select count(*) from big_strings;
++----------+
+| count(*) |
++----------+
+| 4        |
++----------+
+
+</code></pre>
+
+    <p class="p">
+      The following examples show how adjusting <code class="ph codeph">MAX_ROW_SIZE</code> upward
+      allows queries involving the long string columns to succeed:
+    </p>
+
+<pre class="pre codeblock"><code>
+-- Boosting MAX_ROW_SIZE moderately allows all S1 values to be materialized.
+set max_row_size=7mb;
+
+select count(distinct s1) from big_strings;
++--------------------+
+| count(distinct s1) |
++--------------------+
+| 3                  |
++--------------------+
+
+-- But the combination of S1 + S3 strings is still too large.
+select count(distinct s1, s2, s3) from big_strings;
+WARNINGS: Row of size 9.54 MB could not be materialized in plan node with id 1. Increase the max_row_size query option (currently 7.00 MB) to process larger rows.
+
+-- Boosting MAX_ROW_SIZE to larger than the largest row in the table allows
+-- all queries to complete successfully.
+set max_row_size=12mb;
+
+select count(distinct s1, s2, s3) from big_strings;
++----------------------------+
+| count(distinct s1, s2, s3) |
++----------------------------+
+| 4                          |
++----------------------------+
+
+</code></pre>
+
+    <p class="p">
+      The following examples show how to reason about appropriate values for
+      <code class="ph codeph">MAX_ROW_SIZE</code>, based on the characteristics of the
+      columns containing the long values:
+    </p>
+
+<pre class="pre codeblock"><code>
+-- With a large MAX_ROW_SIZE in place, we can examine the columns to
+-- understand the practical lower limit for MAX_ROW_SIZE based on the
+-- table structure and column values.
+select max(length(s1) + length(s2) + length(s3)) / 1e6 as megabytes from big_strings;
++-----------+
+| megabytes |
++-----------+
+| 10.000005 |
++-----------+
+
+-- We can also examine the 'Max Size' for each column after computing stats.
+compute stats big_strings;
+show column stats big_strings;
++--------+--------+------------------+--------+----------+-----------+
+| Column | Type   | #Distinct Values | #Nulls | Max Size | Avg Size  |
++--------+--------+------------------+--------+----------+-----------+
+| s1     | STRING | 2                | -1     | 5000000  | 2500002.5 |
+| s2     | STRING | 2                | -1     | 10       | 7.5       |
+| s3     | STRING | 2                | -1     | 5000000  | 2500005   |
++--------+--------+------------------+--------+----------+-----------+
+
+</code></pre>
+
+    <p class="p">
+        <strong class="ph b">Related information:</strong>
+      </p>
+    <p class="p">
+      <a class="xref" href="impala_buffer_pool_limit.html">BUFFER_POOL_LIMIT Query Option</a>,
+      <a class="xref" href="impala_default_spillable_buffer_size.html">DEFAULT_SPILLABLE_BUFFER_SIZE Query Option</a>,
+      <a class="xref" href="impala_min_spillable_buffer_size.html">MIN_SPILLABLE_BUFFER_SIZE Query Option</a>,
+      <a class="xref" href="impala_scalability.html">Scalability Considerations for Impala</a>
+    </p>
+
+  </div>
+<nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_query_options.html">Query Options for the SET Statement</a></div></div></nav></article></main></body></html>
\ No newline at end of file


[2/7] incubator-impala git commit: Update Impala docs for 2.10 release

Posted by jr...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_scalability.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_scalability.html b/docs/build/html/topics/impala_scalability.html
index 41e1d10..e361005 100644
--- a/docs/build/html/topics/impala_scalability.html
+++ b/docs/build/html/topics/impala_scalability.html
@@ -1,6 +1,6 @@
 <!DOCTYPE html
   SYSTEM "about:legacy-compat">
-<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x">
 <meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="scalability"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>Scalability Considerations for Impala</title></head><body id="scalability"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
+<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name
 ="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="scalability"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>Scalability Considerations for Impala</title></head><body id="scalability"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
 
   <h1 class="title topictitle1" id="ariaid-title1">Scalability Considerations for Impala</h1>
   
@@ -319,13 +319,45 @@
     </div>
   </article>
 
+  <article class="topic concept nested1" aria-labelledby="ariaid-title5" id="scalability__scalability_buffer_pool">
+    <h2 class="title topictitle2" id="ariaid-title5">Effect of Buffer Pool on Memory Usage (<span class="keyword">Impala 2.10</span> and higher)</h2>
+    <div class="body conbody">
+      <p class="p">
+        The buffer pool feature, available in <span class="keyword">Impala 2.10</span> and higher, changes the
+        way Impala allocates memory during a query. Most of the memory needed is reserved at the
+        beginning of the query, avoiding cases where a query might run for a long time before failing
+        with an out-of-memory error. The actual memory estimates and memory buffers are typically
+        smaller than before, so that more queries can run concurrently or process larger volumes
+        of data than previously.
+      </p>
+      <p class="p">
+        The buffer pool feature includes some query options that you can fine-tune:
+        <a class="xref" href="impala_buffer_pool_limit.html">BUFFER_POOL_LIMIT Query Option</a>,
+        <a class="xref" href="impala_default_spillable_buffer_size.html">DEFAULT_SPILLABLE_BUFFER_SIZE Query Option</a>,
+        <a class="xref" href="impala_max_row_size.html">MAX_ROW_SIZE Query Option</a>, and
+        <a class="xref" href="impala_min_spillable_buffer_size.html">MIN_SPILLABLE_BUFFER_SIZE Query Option</a>.
+      </p>
+      <p class="p">
+        Most of the effects of the buffer pool are transparent to you as an Impala user.
+        Memory use during spilling is now steadier and more predictable, instead of
+        increasing rapidly as more data is spilled to disk. The main change from a user
+        perspective is the need to increase the <code class="ph codeph">MAX_ROW_SIZE</code> query option
+        setting when querying tables with columns containing long strings, many columns,
+        or other combinations of factors that produce very large rows. If Impala encounters
+        rows that are too large to process with the default query option settings, the query
+        fails with an error message suggesting to increase the <code class="ph codeph">MAX_ROW_SIZE</code>
+        setting.
+      </p>
+    </div>
+  </article>
+
   
 
   
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title5" id="scalability__spill_to_disk">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title6" id="scalability__spill_to_disk">
 
-    <h2 class="title topictitle2" id="ariaid-title5">SQL Operations that Spill to Disk</h2>
+    <h2 class="title topictitle2" id="ariaid-title6">SQL Operations that Spill to Disk</h2>
 
     <div class="body conbody">
 
@@ -341,6 +373,14 @@
         you should optimize your queries, system parameters, and hardware configuration to make this spilling a rare occurrence.
       </p>
 
+      <div class="note note note_note"><span class="note__title notetitle">Note:</span> 
+        <p class="p">
+          In <span class="keyword">Impala 2.10</span> and higher, also see <a class="xref" href="impala_scalability.html">Scalability Considerations for Impala</a> for
+          changes to Impala memory allocation that might change the details of which queries spill to disk,
+          and how much memory and disk space is involved in the spilling operation.
+        </p>
+      </div>
+
       <p class="p">
         <strong class="ph b">What kinds of queries might spill to disk:</strong>
       </p>
@@ -412,42 +452,40 @@
       </p>
 
       <p class="p">
-        The infrastructure of the spilling feature affects the way the affected SQL operators, such as
-        <code class="ph codeph">GROUP BY</code>, <code class="ph codeph">DISTINCT</code>, and joins, use memory.
-        On each host that participates in the query, each such operator in a query accumulates memory
-        while building the data structure to process the aggregation or join operation. The amount
-        of memory used depends on the portion of the data being handled by that host, and thus might
-        be different from one host to another. When the amount of memory being used for the operator
-        on a particular host reaches a threshold amount, Impala reserves an additional memory buffer
-        to use as a work area in case that operator causes the query to exceed the memory limit for
-        that host. After allocating the memory buffer, the memory used by that operator remains
-        essentially stable or grows only slowly, until the point where the memory limit is reached
-        and the query begins writing temporary data to disk.
+        In <span class="keyword">Impala 2.10</span> and higher, the way SQL operators such as <code class="ph codeph">GROUP BY</code>,
+        <code class="ph codeph">DISTINCT</code>, and joins, transition between using additional memory or activating the
+        spill-to-disk feature is changed. The memory required to spill to disk is reserved up front, and you can
+        examine it in the <code class="ph codeph">EXPLAIN</code> plan when the <code class="ph codeph">EXPLAIN_LEVEL</code> query option is
+        set to 2 or higher.
       </p>
 
-      <p class="p">
-        Prior to Impala 2.2, the extra memory buffer for an operator that might spill to disk
-        was allocated when the data structure used by the applicable SQL operator reaches 16 MB in size,
-        and the memory buffer itself was 512 MB. In Impala 2.2, these values are halved: the threshold value
-        is 8 MB and the memory buffer is 256 MB. <span class="ph">In <span class="keyword">Impala 2.3</span> and higher, the memory for the buffer
-        is allocated in pieces, only as needed, to avoid sudden large jumps in memory usage.</span> A query that uses
-        multiple such operators might allocate multiple such memory buffers, as the size of the data structure
-        for each operator crosses the threshold on a particular host.
-      </p>
+     <p class="p">
+       The infrastructure of the spilling feature affects the way the affected SQL operators, such as
+       <code class="ph codeph">GROUP BY</code>, <code class="ph codeph">DISTINCT</code>, and joins, use memory.
+       On each host that participates in the query, each such operator in a query requires memory
+       to store rows of data and other data structures. Impala reserves a certain amount of memory
+       up front for each operator that supports spill-to-disk that is sufficient to execute the
+       operator. If an operator accumulates more data than can fit in the reserved memory, it
+       can either reserve more memory to continue processing data in memory or start spilling
+       data to temporary scratch files on disk. Thus, operators with spill-to-disk support
+       can adapt to different memory constraints by using however much memory is available
+       to speed up execution, yet tolerate low memory conditions by spilling data to disk.
+     </p>
+     
+     <p class="p">
+       The amount data depends on the portion of the data being handled by that host, and thus
+       the operator may end up consuming different amounts of memory on different hosts.
+     </p>
+
 
-      <p class="p">
-        Therefore, a query that processes a relatively small amount of data on each host would likely
-        never reach the threshold for any operator, and would never allocate any extra memory buffers. A query
-        that did process millions of groups, distinct values, join keys, and so on might cross the threshold,
-        causing its memory requirement to rise suddenly and then flatten out. The larger the cluster, less data is processed
-        on any particular host, thus reducing the chance of requiring the extra memory allocation.
-      </p>
 
       <p class="p">
         <strong class="ph b">Added in:</strong> This feature was added to the <code class="ph codeph">ORDER BY</code> clause in Impala 1.4.
         This feature was extended to cover join queries, aggregation functions, and analytic
         functions in Impala 2.0. The size of the memory work area required by
         each operator that spills was reduced from 512 megabytes to 256 megabytes in Impala 2.2.
+        <span class="ph">The spilling mechanism was reworked to take advantage of the
+        Impala buffer pool feature and be more predictable and stable in <span class="keyword">Impala 2.10</span>.</span>
       </p>
 
       <p class="p">
@@ -467,8 +505,10 @@
             <li class="li">
               The output of the <code class="ph codeph">PROFILE</code> command in the <span class="keyword cmdname">impala-shell</span>
               interpreter. This data shows the memory usage for each host and in total across the cluster. The
-              <code class="ph codeph">BlockMgr.BytesWritten</code> counter reports how much data was written to disk during the
-              query.
+              <code class="ph codeph">WriteIoBytes</code> counter reports how much data was written to disk for each operator
+              during the query. (In <span class="keyword">Impala 2.9</span>, the counter was named
+              <code class="ph codeph">ScratchBytesWritten</code>; in <span class="keyword">Impala 2.8</span> and earlier, it was named
+              <code class="ph codeph">BytesWritten</code>.)
             </li>
 
             <li class="li">
@@ -571,34 +611,15 @@
 
       <p class="p">
         Issue the <code class="ph codeph">PROFILE</code> command to get a detailed breakdown of the memory usage on each node
-        during the query. The crucial part of the profile output concerning memory is the <code class="ph codeph">BlockMgr</code>
-        portion. For example, this profile shows that the query did not quite exceed the memory limit.
-      </p>
-
-<pre class="pre codeblock"><code>BlockMgr:
-   - BlockWritesIssued: 1
-   - BlockWritesOutstanding: 0
-   - BlocksCreated: 24
-   - BlocksRecycled: 1
-   - BufferedPins: 0
-   - MaxBlockSize: 8.00 MB (8388608)
-   <strong class="ph b">- MemoryLimit: 200.00 MB (209715200)</strong>
-   <strong class="ph b">- PeakMemoryUsage: 192.22 MB (201555968)</strong>
-   - TotalBufferWaitTime: 0ns
-   - TotalEncryptionTime: 0ns
-   - TotalIntegrityCheckTime: 0ns
-   - TotalReadBlockTime: 0ns
-</code></pre>
-
-      <p class="p">
-        In this case, because the memory limit was already below any recommended value, I increased the volume of
-        data for the query rather than reducing the memory limit any further.
+        during the query.
+        
       </p>
 
+
+
       <p class="p">
         Set the <code class="ph codeph">MEM_LIMIT</code> query option to a value that is smaller than the peak memory usage
-        reported in the profile output. Do not specify a memory limit lower than about 300 MB, because with such a
-        low limit, queries could fail to start for other reasons. Now try the memory-intensive query again.
+        reported in the profile output. Now try the memory-intensive query again.
       </p>
 
       <p class="p">
@@ -687,8 +708,8 @@ these tables, hint the plan or disable this behavior via query options to enable
     </div>
   </article>
 
-<article class="topic concept nested1" aria-labelledby="ariaid-title6" id="scalability__complex_query">
-<h2 class="title topictitle2" id="ariaid-title6">Limits on Query Size and Complexity</h2>
+<article class="topic concept nested1" aria-labelledby="ariaid-title7" id="scalability__complex_query">
+<h2 class="title topictitle2" id="ariaid-title7">Limits on Query Size and Complexity</h2>
 <div class="body conbody">
 <p class="p">
 There are hardcoded limits on the maximum size and complexity of queries.
@@ -712,8 +733,8 @@ use a single <code class="ph codeph">IN</code> clause:
 </div>
 </article>
 
-<article class="topic concept nested1" aria-labelledby="ariaid-title7" id="scalability__scalability_io">
-<h2 class="title topictitle2" id="ariaid-title7">Scalability Considerations for Impala I/O</h2>
+<article class="topic concept nested1" aria-labelledby="ariaid-title8" id="scalability__scalability_io">
+<h2 class="title topictitle2" id="ariaid-title8">Scalability Considerations for Impala I/O</h2>
 <div class="body conbody">
 <p class="p">
 Impala parallelizes its I/O operations aggressively,
@@ -738,26 +759,34 @@ Currently, there is no throttling mechanism for Impala I/O.
 </div>
 </article>
 
-<article class="topic concept nested1" aria-labelledby="ariaid-title8" id="scalability__big_tables">
-<h2 class="title topictitle2" id="ariaid-title8">Scalability Considerations for Table Layout</h2>
-<div class="body conbody">
-<p class="p">
-Due to the overhead of retrieving and updating table metadata
-in the metastore database, try to limit the number of columns
-in a table to a maximum of approximately 2000.
-Although Impala can handle wider tables than this, the metastore overhead
-can become significant, leading to query performance that is slower
-than expected based on the actual data volume.
-</p>
-<p class="p">
-To minimize overhead related to the metastore database and Impala query planning,
-try to limit the number of partitions for any partitioned table to a few tens of thousands.
-</p>
-</div>
-</article>
+  <article class="topic concept nested1" aria-labelledby="ariaid-title9" id="scalability__big_tables">
+    <h2 class="title topictitle2" id="ariaid-title9">Scalability Considerations for Table Layout</h2>
+    <div class="body conbody">
+      <p class="p">
+        Due to the overhead of retrieving and updating table metadata
+        in the metastore database, try to limit the number of columns
+        in a table to a maximum of approximately 2000.
+        Although Impala can handle wider tables than this, the metastore overhead
+        can become significant, leading to query performance that is slower
+        than expected based on the actual data volume.
+      </p>
+      <p class="p">
+        To minimize overhead related to the metastore database and Impala query planning,
+        try to limit the number of partitions for any partitioned table to a few tens of thousands.
+      </p>
+      <p class="p">
+        If the volume of data within a table makes it impractical to run exploratory
+        queries, consider using the <code class="ph codeph">TABLESAMPLE</code> clause to limit query processing
+        to only a percentage of data within the table. This technique reduces the overhead
+        for query startup, I/O to read the data, and the amount of network, CPU, and memory
+        needed to process intermediate results during the query. See <a class="xref" href="impala_tablesample.html">TABLESAMPLE Clause</a>
+        for details.
+      </p>
+    </div>
+  </article>
 
-<article class="topic concept nested1" aria-labelledby="ariaid-title9" id="scalability__kerberos_overhead_cluster_size">
-<h2 class="title topictitle2" id="ariaid-title9">Kerberos-Related Network Overhead for Large Clusters</h2>
+<article class="topic concept nested1" aria-labelledby="ariaid-title10" id="scalability__kerberos_overhead_cluster_size">
+<h2 class="title topictitle2" id="ariaid-title10">Kerberos-Related Network Overhead for Large Clusters</h2>
 <div class="body conbody">
 <p class="p">
 When Impala starts up, or after each <code class="ph codeph">kinit</code> refresh, Impala sends a number of
@@ -782,8 +811,8 @@ so other secure services might be affected temporarily.
 </div>
 </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title10" id="scalability__kerberos_overhead_memory_usage">
-  <h2 class="title topictitle2" id="ariaid-title10">Kerberos-Related Memory Overhead for Large Clusters</h2>
+  <article class="topic concept nested1" aria-labelledby="ariaid-title11" id="scalability__kerberos_overhead_memory_usage">
+  <h2 class="title topictitle2" id="ariaid-title11">Kerberos-Related Memory Overhead for Large Clusters</h2>
   <div class="body conbody">
     <div class="p">
         On a kerberized cluster with high memory utilization, <span class="keyword cmdname">kinit</span> commands executed after
@@ -817,8 +846,8 @@ vm.overcommit_memory=1
   </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title11" id="scalability__scalability_hotspots">
-    <h2 class="title topictitle2" id="ariaid-title11">Avoiding CPU Hotspots for HDFS Cached Data</h2>
+  <article class="topic concept nested1" aria-labelledby="ariaid-title12" id="scalability__scalability_hotspots">
+    <h2 class="title topictitle2" id="ariaid-title12">Avoiding CPU Hotspots for HDFS Cached Data</h2>
     <div class="body conbody">
       <p class="p">
         You can use the HDFS caching feature, described in <a class="xref" href="impala_perf_hdfs_caching.html#hdfs_caching">Using HDFS Caching with Impala (Impala 2.1 or higher only)</a>,
@@ -855,4 +884,68 @@ vm.overcommit_memory=1
     </div>
   </article>
 
+  <article class="topic concept nested1" aria-labelledby="ariaid-title13" id="scalability__scalability_file_handle_cache">
+    <h2 class="title topictitle2" id="ariaid-title13">Scalability Considerations for NameNode Traffic with File Handle Caching</h2>
+    <div class="body conbody">
+      <p class="p">
+        One scalability aspect that affects heavily loaded clusters is the load on the HDFS
+        NameNode, from looking up the details as each HDFS file is opened. Impala queries
+        often access many different HDFS files, for example if a query does a full table scan
+        on a table with thousands of partitions, each partition containing multiple data files.
+        Accessing each column of a Parquet file also involves a separate <span class="q">"open"</span> call,
+        further increasing the load on the NameNode. High NameNode overhead can add startup time
+        (that is, increase latency) to Impala queries, and reduce overall throughput for non-Impala
+        workloads that also require accessing HDFS files.
+      </p>
+      <p class="p">
+        In <span class="keyword">Impala 2.10</span> and higher, you can reduce NameNode overhead by enabling
+        a caching feature for HDFS file handles. Data files that are accessed by different queries,
+        or even multiple times within the same query, can be accessed without a new <span class="q">"open"</span>
+        call and without fetching the file details again from the NameNode.
+      </p>
+      <p class="p">
+        Because this feature only involves HDFS data files, it does not apply to non-HDFS tables,
+        such as Kudu or HBase tables, or tables that store their data on cloud services such as
+        S3 or ADLS. Any read operations that perform remote reads also skip the cached file handles.
+      </p>
+      <p class="p">
+        This feature is turned off by default. To enable it, set the configuration option
+        <code class="ph codeph">max_cached_file_handles</code> to a non-zero value for each <span class="keyword cmdname">impalad</span>
+        daemon. Consider an initial starting value of 20 thousand, and adjust upward if NameNode
+        overhead is still significant, or downward if it is more important to reduce the extra memory usage
+        on each host. Each cache entry consumes 6 KB, meaning that caching 20,000 file handles requires
+        up to 120 MB on each DataNode. The exact memory usage varies depending on how many file handles
+        have actually been cached; memory is freed as file handles are evicted from the cache.
+      </p>
+      <p class="p">
+        If a manual HDFS operation moves a file to the HDFS Trashcan while the file handle is cached,
+        Impala still accesses the contents of that file. This is a change from prior behavior. Previously,
+        accessing a file that was in the trashcan would cause an error. This behavior only applies to
+        non-Impala methods of removing HDFS files, not the Impala mechanisms such as <code class="ph codeph">TRUNCATE TABLE</code>
+        or <code class="ph codeph">DROP TABLE</code>.
+      </p>
+      <p class="p">
+        If files are removed, replaced, or appended by HDFS operations outside of Impala, the way to bring the
+        file information up to date is to run the <code class="ph codeph">REFRESH</code> statement on the table.
+      </p>
+      <p class="p">
+        File handle cache entries are evicted as the cache fills up, or based on a timeout period
+        when they have not been accessed for some time.
+      </p>
+      <p class="p">
+        To evaluate the effectiveness of file handle caching for a particular workload, issue the
+        <code class="ph codeph">PROFILE</code> statement in <span class="keyword cmdname">impala-shell</span> or examine query
+        profiles in the Impala web UI. Look for the ratio of <code class="ph codeph">CachedFileHandlesHitCount</code>
+        (ideally, should be high) to <code class="ph codeph">CachedFileHandlesMissCount</code> (ideally, should be low).
+        Before starting any evaluation, run some representative queries to <span class="q">"warm up"</span> the cache,
+        because the first time each data file is accessed is always recorded as a cache miss.
+        To see metrics about file handle caching for each <span class="keyword cmdname">impalad</span> instance,
+        examine the <span class="ph uicontrol">/metrics</span> page in the Impala web UI, in particular the fields
+        <span class="ph uicontrol">impala-server.io.mgr.cached-file-handles-miss-count</span>,
+        <span class="ph uicontrol">impala-server.io.mgr.cached-file-handles-hit-count</span>, and
+        <span class="ph uicontrol">impala-server.io.mgr.num-cached-file-handles</span>.
+      </p>
+    </div>
+  </article>
+
 </article></main></body></html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_select.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_select.html b/docs/build/html/topics/impala_select.html
index 7a12c42..fee5e26 100644
--- a/docs/build/html/topics/impala_select.html
+++ b/docs/build/html/topics/impala_select.html
@@ -1,6 +1,6 @@
 <!DOCTYPE html
   SYSTEM "about:legacy-compat">
-<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_langref_sql.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_joins.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_order_by.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_group_by.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_having.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_limit.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_offset.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_union.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_subqueries.html"><meta name="DC.Relation" scheme="U
 RI" content="../topics/impala_with.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_distinct.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_hints.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="select"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>SELECT Statement</title></head><body id="select"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
+<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_langref_sql.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_joins.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_order_by.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_group_by.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_having.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_limit.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_offset.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_union.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_subqueries.html"><meta name="DC.Relation" scheme="U
 RI" content="../topics/impala_tablesample.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_with.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_distinct.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_hints.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="select"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>SELECT Statement</title></head><body id="select"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
 
   <h1 class="title topictitle1" id="ariaid-title1">SELECT Statement</h1>
   
@@ -33,11 +33,14 @@ FROM <em class="ph i">table_reference</em> [, <em class="ph i">table_reference</
   JOIN <em class="ph i">table_reference</em>
   [ON <em class="ph i">join_equality_clauses</em> | USING (<var class="keyword varname">col1</var>[, <var class="keyword varname">col2</var> ...]] ...
 WHERE <em class="ph i">conditions</em>
-GROUP BY { <em class="ph i">column</em> | <em class="ph i">expression</em> [ASC | DESC] [NULLS FIRST | NULLS LAST] [, ...] }
+GROUP BY { <em class="ph i">column</em> | <em class="ph i">expression</em> [, ...] }
 HAVING <code class="ph codeph">conditions</code>
-GROUP BY { <em class="ph i">column</em> | <em class="ph i">expression</em> [ASC | DESC] [, ...] }
+ORDER BY { <em class="ph i">column</em> | <em class="ph i">expression</em> [ASC | DESC] [NULLS FIRST | NULLS LAST] [, ...] }
 LIMIT <em class="ph i">expression</em> [OFFSET <em class="ph i">expression</em>]
 [UNION [ALL] <em class="ph i">select_statement</em>] ...]
+
+table_reference := { <var class="keyword varname">table_name</var> | (<var class="keyword varname">subquery</var>) }
+  <span class="ph">[ TABLESAMPLE SYSTEM(<var class="keyword varname">percentage</var>) [REPEATABLE(<var class="keyword varname">seed</var>)] ]</span>
 </code></pre>
 
     <p class="p">
@@ -107,7 +110,7 @@ LIMIT <em class="ph i">expression</em> [OFFSET <em class="ph i">expression</em>]
         are supported in all Impala versions. The <code class="ph codeph">CROSS JOIN</code> operator is available in Impala 1.2.2
         and higher. During performance tuning, you can override the reordering of join clauses that Impala does
         internally by including the keyword <code class="ph codeph">STRAIGHT_JOIN</code> immediately after the
-        <code class="ph codeph">SELECT</code> keyword
+        <code class="ph codeph">SELECT</code> and any <code class="ph codeph">DISTINCT</code> or <code class="ph codeph">ALL</code> keywords.
       </p>
         <p class="p">
           See <a class="xref" href="impala_joins.html#joins">Joins in Impala SELECT Statements</a> for details and examples of join queries.
@@ -145,6 +148,12 @@ LIMIT <em class="ph i">expression</em> [OFFSET <em class="ph i">expression</em>]
         <code class="ph codeph">LIKE</code>, <code class="ph codeph">IN</code>, <code class="ph codeph">BETWEEN</code>, and <code class="ph codeph">COALESCE</code>. Impala
         specifically supports built-ins described in <a class="xref" href="impala_functions.html#builtins">Impala Built-In Functions</a>.
       </li>
+
+      <li class="li">
+        In <span class="keyword">Impala 2.9</span> and higher, an optional <code class="ph codeph">TABLESAMPLE</code>
+        clause immediately after a table reference, to specify that the query only processes a
+        specified percentage of the table data. See <a class="xref" href="impala_tablesample.html">TABLESAMPLE Clause</a> for details.
+      </li>
     </ul>
 
     <p class="p">
@@ -224,4 +233,4 @@ LIMIT <em class="ph i">expression</em> [OFFSET <em class="ph i">expression</em>]
   </div>
 
   
-<nav role="navigation" class="related-links"><ul class="ullinks"><li class="link ulchildlink"><strong><a href="../topics/impala_joins.html">Joins in Impala SELECT Statements</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_order_by.html">ORDER BY Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_group_by.html">GROUP BY Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_having.html">HAVING Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_limit.html">LIMIT Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_offset.html">OFFSET Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_union.html">UNION Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_subqueries.html">Subqueries in Impala SELECT Statements</a></strong><
 br></li><li class="link ulchildlink"><strong><a href="../topics/impala_with.html">WITH Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_distinct.html">DISTINCT Operator</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_hints.html">Query Hints in Impala SELECT Statements</a></strong><br></li></ul><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_langref_sql.html">Impala SQL Statements</a></div></div></nav></article></main></body></html>
\ No newline at end of file
+<nav role="navigation" class="related-links"><ul class="ullinks"><li class="link ulchildlink"><strong><a href="../topics/impala_joins.html">Joins in Impala SELECT Statements</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_order_by.html">ORDER BY Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_group_by.html">GROUP BY Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_having.html">HAVING Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_limit.html">LIMIT Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_offset.html">OFFSET Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_union.html">UNION Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_subqueries.html">Subqueries in Impala SELECT Statements</a></strong><
 br></li><li class="link ulchildlink"><strong><a href="../topics/impala_tablesample.html">TABLESAMPLE Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_with.html">WITH Clause</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_distinct.html">DISTINCT Operator</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_hints.html">Query Hints in Impala SELECT Statements</a></strong><br></li></ul><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_langref_sql.html">Impala SQL Statements</a></div></div></nav></article></main></body></html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_shell_commands.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_shell_commands.html b/docs/build/html/topics/impala_shell_commands.html
index d2bee6c..43159a8 100644
--- a/docs/build/html/topics/impala_shell_commands.html
+++ b/docs/build/html/topics/impala_shell_commands.html
@@ -218,6 +218,30 @@
               </p>
             </td>
           </tr>
+          <tr class="row" id="shell_commands__rerun_cmd">
+            <td class="entry nocellnorowborder" headers="shell_commands__entry__1 ">
+              <p class="p">
+                <code class="ph codeph">rerun</code> or <code class="ph codeph">@</code>
+              </p>
+            </td>
+            <td class="entry nocellnorowborder" headers="shell_commands__entry__2 ">
+              <p class="p">
+                Executes a previous <span class="keyword cmdname">impala-shell</span> command again,
+                from the list of commands displayed by the <code class="ph codeph">history</code>
+                command. These could be SQL statements, or commands specific to
+                <span class="keyword cmdname">impala-shell</span> such as <code class="ph codeph">quit</code>
+                or <code class="ph codeph">profile</code>.
+              </p>
+              <p class="p">
+                Specify an integer argument. A positive integer <code class="ph codeph">N</code>
+                represents the command labelled <code class="ph codeph">N</code> in the history list.
+                A negative integer <code class="ph codeph">-N</code> represents the <code class="ph codeph">N</code>th
+                command from the end of the list, such as -1 for the most recent command.
+                Commands that are executed again do not produce new entries in the
+                history list.
+              </p>
+            </td>
+          </tr>
           <tr class="row" id="shell_commands__select_cmd">
             <td class="entry nocellnorowborder" headers="shell_commands__entry__1 ">
               <p class="p">

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_shell_running_commands.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_shell_running_commands.html b/docs/build/html/topics/impala_shell_running_commands.html
index e0e8880..15abef7 100644
--- a/docs/build/html/topics/impala_shell_running_commands.html
+++ b/docs/build/html/topics/impala_shell_running_commands.html
@@ -1,6 +1,6 @@
 <!DOCTYPE html
   SYSTEM "about:legacy-compat">
-<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_impala_shell.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="shell_running_commands"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>Running Commands and SQL Statements in impala-shell</title></head><body id="shell_running_commands"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
+<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_impala_shell.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="shell_running_commands"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>Running Commands and SQL Statements in impala-shell</title></head><body id="shell_running_commands"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
 
   <h1 class="title topictitle1" id="ariaid-title1">Running Commands and SQL Statements in impala-shell</h1>
   
@@ -254,4 +254,69 @@ Fetched 5 row(s) in 0.01s
 </code></pre>
 
   </div>
-<nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_impala_shell.html">Using the Impala Shell (impala-shell Command)</a></div></div></nav></article></main></body></html>
\ No newline at end of file
+
+  <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_impala_shell.html">Using the Impala Shell (impala-shell Command)</a></div></div></nav><article class="topic concept nested1" aria-labelledby="ariaid-title2" id="shell_running_commands__rerun">
+    <h2 class="title topictitle2" id="ariaid-title2">Rerunning impala-shell Commands</h2>
+    <div class="body conbody">
+
+      <p class="p">
+        In <span class="keyword">Impala 2.10</span> and higher, you can use the
+        <code class="ph codeph">rerun</code> command, or its abbreviation <code class="ph codeph">@</code>,
+        to re-execute commands from the history list. The argument can be
+        a positive integer (reflecting the number shown in <code class="ph codeph">history</code>
+        output) or a negative integer (reflecting the N'th last command in the
+        <code class="ph codeph">history</code> output. For example:
+      </p>
+
+<pre class="pre codeblock"><code>
+[localhost:21000] &gt; select * from p1 order by t limit 5;
+...
+[localhost:21000] &gt; show table stats p1;
++-----------+--------+--------+------------------------------------------------------------+
+| #Rows     | #Files | Size   | Location                                                   |
++-----------+--------+--------+------------------------------------------------------------+
+| 134217728 | 50     | 4.66MB | hdfs://test.example.com:8020/user/hive/warehouse/jdr.db/p1 |
++-----------+--------+--------+------------------------------------------------------------+
+[localhost:21000] &gt; compute stats p1;
++-----------------------------------------+
+| summary                                 |
++-----------------------------------------+
+| Updated 1 partition(s) and 3 column(s). |
++-----------------------------------------+
+[localhost:21000] &gt; history;
+[1]: use jdr;
+[2]: history;
+[3]: show tables;
+[4]: select * from p1 order by t limit 5;
+[5]: show table stats p1;
+[6]: compute stats p1;
+[7]: history;
+[localhost:21000] &gt; @-2; &lt;- Rerun the 2nd last command in the history list
+Rerunning compute stats p1;
++-----------------------------------------+
+| summary                                 |
++-----------------------------------------+
+| Updated 1 partition(s) and 3 column(s). |
++-----------------------------------------+
+[localhost:21000] &gt; history; &lt;- History list is not updated by rerunning commands
+                                or by repeating the last command, in this case 'history'.
+[1]: use jdr;
+[2]: history;
+[3]: show tables;
+[4]: select * from p1 order by t limit 5;
+[5]: show table stats p1;
+[6]: compute stats p1;
+[7]: history;
+[localhost:21000] &gt; @4; &lt;- Rerun command #4 in the history list using short form '@'.
+Rerunning select * from p1 order by t limit 5;
+...
+[localhost:21000] &gt; rerun 4; &lt;- Rerun command #4 using long form 'rerun'.
+Rerunning select * from p1 order by t limit 5;
+...
+
+</code></pre>
+
+    </div>
+  </article>
+
+</article></main></body></html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_ssl.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_ssl.html b/docs/build/html/topics/impala_ssl.html
index a9b4d25..e995159 100644
--- a/docs/build/html/topics/impala_ssl.html
+++ b/docs/build/html/topics/impala_ssl.html
@@ -116,4 +116,75 @@
     </div>
   </article>
 
+  <article class="topic concept nested1" aria-labelledby="ariaid-title4" id="ssl__tls_min_version">
+
+    <h2 class="title topictitle2" id="ariaid-title4">Specifying TLS/SSL Minimum Allowed Version and Ciphers</h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        Depending on your cluster configuration and the security practices in your
+        organization, you might need to restrict the allowed versions of TLS/SSL
+        used by Impala. Older TLS/SSL versions might have vulnerabilities or lack
+        certain features. In <span class="keyword">Impala 2.10</span>, you can use startup
+        options for the <span class="keyword cmdname">impalad</span>, <span class="keyword cmdname">catalogd</span>,
+        and <span class="keyword cmdname">statestored</span> daemons to specify a minimum allowed
+        version of TLS/SSL.
+      </p>
+
+      <p class="p">
+        Specify one of the following values for the <code class="ph codeph">--ssl_minimum_version</code>
+        configuration setting:
+      </p>
+
+      <ul class="ul">
+        <li class="li">
+          <p class="p">
+            <code class="ph codeph">tlsv1</code>: Allow any TLS version of 1.0 or higher.
+            This setting is the default when TLS/SSL is enabled.
+          </p>
+        </li>
+        <li class="li">
+          <p class="p">
+            <code class="ph codeph">tlsv1.1</code>: Allow any TLS version of 1.1 or higher.
+          </p>
+        </li>
+        <li class="li">
+          <p class="p">
+            <code class="ph codeph">tlsv1.2</code>: Allow any TLS version of 1.2 or higher.
+          </p>
+        </li>
+      </ul>
+      <div class="note note note_note"><span class="note__title notetitle">Note:</span> 
+        <p class="p">
+          As of <span class="keyword">Impala 2.10</span>, TLSv1.2 may not work for Impala on RHEL 6
+          or CentOS 6, even if OpenSSL 1.0.1 is available. The daemons fail to start, with a
+          socket error stating the TLS version is not supported. The underlying cause is related to
+          <a class="xref" href="https://bugzilla.redhat.com/show_bug.cgi?id=1497859" target="_blank">Red Hat issue 1497859</a>.
+          The issue applies if you build on a RHEL 6 or CentOS 6 system with OpenSSL 1.0.0, and
+          run on a RHEL 6 or CentOS 6 system with OpenSSL 1.0.1.
+        </p>
+      </div>
+
+      <p class="p">
+        Along with specifying the version, you can also specify the allowed set of TLS ciphers
+        by using the <code class="ph codeph">--ssl_cipher_list</code> configuration setting. The argument to
+        this option is a list of keywords, separated by colons, commas, or spaces, and
+        optionally including other notation. For example:
+      </p>
+
+<pre class="pre codeblock"><code>
+--ssl_cipher_list="RC4-SHA,RC4-MD5"
+</code></pre>
+
+      <p class="p">
+        By default, the cipher list is empty, and Impala uses the default cipher list for
+        the underlying platform. See the output of <span class="keyword cmdname">man ciphers</span> for the full
+        set of keywords and notation allowed in the argument string.
+      </p>
+
+    </div>
+
+  </article>
+
 </article></main></body></html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_string_functions.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_string_functions.html b/docs/build/html/topics/impala_string_functions.html
index b3e6dbd..a7a0559 100644
--- a/docs/build/html/topics/impala_string_functions.html
+++ b/docs/build/html/topics/impala_string_functions.html
@@ -63,6 +63,276 @@
 
       
 
+        <dt class="dt dlterm" id="string_functions__base64decode">
+          <code class="ph codeph">base64decode(string str)</code>
+        </dt>
+
+        <dd class="dd">
+          
+          <strong class="ph b">Purpose:</strong>
+          <p class="p">
+            <strong class="ph b">Return type:</strong> <code class="ph codeph">string</code>
+          </p>
+          <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+          <p class="p">
+            For general information about Base64 encoding, see
+            <a class="xref" href="https://en.wikipedia.org/wiki/Base64" target="_blank">Base64 article on Wikipedia</a>.
+          </p>
+          <p class="p">
+        The functions <code class="ph codeph">base64encode()</code> and
+        <code class="ph codeph">base64decode()</code> are typically used
+        in combination, to store in an Impala table string data that is
+        problematic to store or transmit. For example, you could use
+        these functions to store string data that uses an encoding
+        other than UTF-8, or to transform the values in contexts that
+        require ASCII values, such as for partition key columns.
+        Keep in mind that base64-encoded values produce different results
+        for string functions such as <code class="ph codeph">LENGTH()</code>,
+        <code class="ph codeph">MAX()</code>, and <code class="ph codeph">MIN()</code> than when
+        those functions are called with the unencoded string values.
+      </p>
+          <p class="p">
+        The set of characters that can be generated as output
+        from <code class="ph codeph">base64encode()</code>, or specified in
+        the argument string to <code class="ph codeph">base64decode()</code>,
+        are the ASCII uppercase and lowercase letters (A-Z, a-z),
+        digits (0-9), and the punctuation characters
+        <code class="ph codeph">+</code>, <code class="ph codeph">/</code>, and <code class="ph codeph">=</code>.
+      </p>
+          <p class="p">
+        All return values produced by <code class="ph codeph">base64encode()</code>
+        are a multiple of 4 bytes in length. All argument values
+        supplied to <code class="ph codeph">base64decode()</code> must also be a
+        multiple of 4 bytes in length. If a base64-encoded value
+        would otherwise have a different length, it can be padded
+        with trailing <code class="ph codeph">=</code> characters to reach a length
+        that is a multiple of 4 bytes.
+      </p>
+          <p class="p">
+        If the argument string to <code class="ph codeph">base64decode()</code> does
+        not represent a valid base64-encoded value, subject to the
+        constraints of the Impala implementation such as the allowed
+        character set, the function returns <code class="ph codeph">NULL</code>.
+      </p>
+          <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+          <div class="p">
+        The following examples show how to use <code class="ph codeph">base64encode()</code>
+        and <code class="ph codeph">base64decode()</code> together to store and retrieve
+        string values:
+<pre class="pre codeblock"><code>
+-- An arbitrary string can be encoded in base 64.
+-- The length of the output is a multiple of 4 bytes,
+-- padded with trailing = characters if necessary.
+select base64encode('hello world') as encoded,
+  length(base64encode('hello world')) as length;
++------------------+--------+
+| encoded          | length |
++------------------+--------+
+| aGVsbG8gd29ybGQ= | 16     |
++------------------+--------+
+
+-- Passing an encoded value to base64decode() produces
+-- the original value.
+select base64decode('aGVsbG8gd29ybGQ=') as decoded;
++-------------+
+| decoded     |
++-------------+
+| hello world |
++-------------+
+</code></pre>
+
+      These examples demonstrate incorrect encoded values that
+      produce <code class="ph codeph">NULL</code> return values when decoded:
+
+<pre class="pre codeblock"><code>
+-- The input value to base64decode() must be a multiple of 4 bytes.
+-- In this case, leaving off the trailing = padding character
+-- produces a NULL return value.
+select base64decode('aGVsbG8gd29ybGQ') as decoded;
++---------+
+| decoded |
++---------+
+| NULL    |
++---------+
+WARNINGS: UDF WARNING: Invalid base64 string; input length is 15,
+  which is not a multiple of 4.
+
+-- The input to base64decode() can only contain certain characters.
+-- The $ character in this case causes a NULL return value.
+select base64decode('abc$');
++----------------------+
+| base64decode('abc$') |
++----------------------+
+| NULL                 |
++----------------------+
+WARNINGS: UDF WARNING: Could not base64 decode input in space 4; actual output length 0
+</code></pre>
+
+      These examples demonstrate <span class="q">"round-tripping"</span> of an original string to an
+      encoded string, and back again. This technique is applicable if the original
+      source is in an unknown encoding, or if some intermediate processing stage
+      might cause national characters to be misrepresented:
+
+<pre class="pre codeblock"><code>
+select 'circumflex accents: â, ê, î, ô, û' as original,
+  base64encode('circumflex accents: â, ê, î, ô, û') as encoded;
++-----------------------------------+------------------------------------------------------+
+| original                          | encoded                                              |
++-----------------------------------+------------------------------------------------------+
+| circumflex accents: â, ê, î, ô, û | Y2lyY3VtZmxleCBhY2NlbnRzOiDDoiwgw6osIMOuLCDDtCwgw7s= |
++-----------------------------------+------------------------------------------------------+
+
+select base64encode('circumflex accents: â, ê, î, ô, û') as encoded,
+  base64decode(base64encode('circumflex accents: â, ê, î, ô, û')) as decoded;
++------------------------------------------------------+-----------------------------------+
+| encoded                                              | decoded                           |
++------------------------------------------------------+-----------------------------------+
+| Y2lyY3VtZmxleCBhY2NlbnRzOiDDoiwgw6osIMOuLCDDtCwgw7s= | circumflex accents: â, ê, î, ô, û |
++------------------------------------------------------+-----------------------------------+
+</code></pre>
+      </div>
+        </dd>
+
+      
+
+      
+
+        <dt class="dt dlterm" id="string_functions__base64encode">
+          <code class="ph codeph">base64encode(string str)</code>
+        </dt>
+
+        <dd class="dd">
+          
+          <strong class="ph b">Purpose:</strong>
+          <p class="p">
+            <strong class="ph b">Return type:</strong> <code class="ph codeph">string</code>
+          </p>
+          <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+          <p class="p">
+            For general information about Base64 encoding, see
+            <a class="xref" href="https://en.wikipedia.org/wiki/Base64" target="_blank">Base64 article on Wikipedia</a>.
+          </p>
+          <p class="p">
+        The functions <code class="ph codeph">base64encode()</code> and
+        <code class="ph codeph">base64decode()</code> are typically used
+        in combination, to store in an Impala table string data that is
+        problematic to store or transmit. For example, you could use
+        these functions to store string data that uses an encoding
+        other than UTF-8, or to transform the values in contexts that
+        require ASCII values, such as for partition key columns.
+        Keep in mind that base64-encoded values produce different results
+        for string functions such as <code class="ph codeph">LENGTH()</code>,
+        <code class="ph codeph">MAX()</code>, and <code class="ph codeph">MIN()</code> than when
+        those functions are called with the unencoded string values.
+      </p>
+          <p class="p">
+        The set of characters that can be generated as output
+        from <code class="ph codeph">base64encode()</code>, or specified in
+        the argument string to <code class="ph codeph">base64decode()</code>,
+        are the ASCII uppercase and lowercase letters (A-Z, a-z),
+        digits (0-9), and the punctuation characters
+        <code class="ph codeph">+</code>, <code class="ph codeph">/</code>, and <code class="ph codeph">=</code>.
+      </p>
+          <p class="p">
+        All return values produced by <code class="ph codeph">base64encode()</code>
+        are a multiple of 4 bytes in length. All argument values
+        supplied to <code class="ph codeph">base64decode()</code> must also be a
+        multiple of 4 bytes in length. If a base64-encoded value
+        would otherwise have a different length, it can be padded
+        with trailing <code class="ph codeph">=</code> characters to reach a length
+        that is a multiple of 4 bytes.
+      </p>
+          <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+          <div class="p">
+        The following examples show how to use <code class="ph codeph">base64encode()</code>
+        and <code class="ph codeph">base64decode()</code> together to store and retrieve
+        string values:
+<pre class="pre codeblock"><code>
+-- An arbitrary string can be encoded in base 64.
+-- The length of the output is a multiple of 4 bytes,
+-- padded with trailing = characters if necessary.
+select base64encode('hello world') as encoded,
+  length(base64encode('hello world')) as length;
++------------------+--------+
+| encoded          | length |
++------------------+--------+
+| aGVsbG8gd29ybGQ= | 16     |
++------------------+--------+
+
+-- Passing an encoded value to base64decode() produces
+-- the original value.
+select base64decode('aGVsbG8gd29ybGQ=') as decoded;
++-------------+
+| decoded     |
++-------------+
+| hello world |
++-------------+
+</code></pre>
+
+      These examples demonstrate incorrect encoded values that
+      produce <code class="ph codeph">NULL</code> return values when decoded:
+
+<pre class="pre codeblock"><code>
+-- The input value to base64decode() must be a multiple of 4 bytes.
+-- In this case, leaving off the trailing = padding character
+-- produces a NULL return value.
+select base64decode('aGVsbG8gd29ybGQ') as decoded;
++---------+
+| decoded |
++---------+
+| NULL    |
++---------+
+WARNINGS: UDF WARNING: Invalid base64 string; input length is 15,
+  which is not a multiple of 4.
+
+-- The input to base64decode() can only contain certain characters.
+-- The $ character in this case causes a NULL return value.
+select base64decode('abc$');
++----------------------+
+| base64decode('abc$') |
++----------------------+
+| NULL                 |
++----------------------+
+WARNINGS: UDF WARNING: Could not base64 decode input in space 4; actual output length 0
+</code></pre>
+
+      These examples demonstrate <span class="q">"round-tripping"</span> of an original string to an
+      encoded string, and back again. This technique is applicable if the original
+      source is in an unknown encoding, or if some intermediate processing stage
+      might cause national characters to be misrepresented:
+
+<pre class="pre codeblock"><code>
+select 'circumflex accents: â, ê, î, ô, û' as original,
+  base64encode('circumflex accents: â, ê, î, ô, û') as encoded;
++-----------------------------------+------------------------------------------------------+
+| original                          | encoded                                              |
++-----------------------------------+------------------------------------------------------+
+| circumflex accents: â, ê, î, ô, û | Y2lyY3VtZmxleCBhY2NlbnRzOiDDoiwgw6osIMOuLCDDtCwgw7s= |
++-----------------------------------+------------------------------------------------------+
+
+select base64encode('circumflex accents: â, ê, î, ô, û') as encoded,
+  base64decode(base64encode('circumflex accents: â, ê, î, ô, û')) as decoded;
++------------------------------------------------------+-----------------------------------+
+| encoded                                              | decoded                           |
++------------------------------------------------------+-----------------------------------+
+| Y2lyY3VtZmxleCBhY2NlbnRzOiDDoiwgw6osIMOuLCDDtCwgw7s= | circumflex accents: â, ê, î, ô, û |
++------------------------------------------------------+-----------------------------------+
+</code></pre>
+      </div>
+        </dd>
+
+      
+
+      
+
         <dt class="dt dlterm" id="string_functions__btrim">
           <code class="ph codeph">btrim(string a)</code>,
           <code class="ph codeph">btrim(string a, string chars_to_trim)</code>

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_struct.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_struct.html b/docs/build/html/topics/impala_struct.html
index c7b02d0..e7d4c04 100644
--- a/docs/build/html/topics/impala_struct.html
+++ b/docs/build/html/topics/impala_struct.html
@@ -130,7 +130,7 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
           </p>
         </li>
         <li class="li">
-          <p class="p" id="struct__d6e3003">
+          <p class="p" id="struct__d6e3156">
             The maximum length of the column definition for any complex type, including declarations for any nested types,
             is 4000 characters.
           </p>

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_subqueries.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_subqueries.html b/docs/build/html/topics/impala_subqueries.html
index 2be2880..280d60c 100644
--- a/docs/build/html/topics/impala_subqueries.html
+++ b/docs/build/html/topics/impala_subqueries.html
@@ -171,6 +171,13 @@ SELECT x FROM t1 WHERE y &gt; (SELECT count(z) FROM t2);
 </code></pre>
 
     <p class="p">
+        The <code class="ph codeph">STRAIGHT_JOIN</code> hint affects the join order of table references in the query
+        block containing the hint. It does not affect the join order of nested queries, such as views,
+        inline views, or <code class="ph codeph">WHERE</code>-clause subqueries. To use this hint for performance
+        tuning of complex queries, apply the hint to all query blocks that need a fixed join order.
+      </p>
+
+    <p class="p">
         <strong class="ph b">Internal details:</strong>
       </p>
 
@@ -287,6 +294,15 @@ SELECT x FROM t1 WHERE y &gt; (SELECT count(z) FROM t2);
           when referring to any column from the outer query block within a subquery.
         </p>
       </li>
+      <li class="li">
+        <p class="p">
+        The <code class="ph codeph">TABLESAMPLE</code> clause of the <code class="ph codeph">SELECT</code>
+        statement does not apply to a table reference derived from a view, a subquery,
+        or anything other than a real base table. This clause only works for tables
+        backed by HDFS or HDFS-like data files, therefore it does not apply to Kudu or
+        HBase tables.
+      </p>
+      </li>
     </ul>
 
     <p class="p">

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_tablesample.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_tablesample.html b/docs/build/html/topics/impala_tablesample.html
new file mode 100644
index 0000000..7a4f767
--- /dev/null
+++ b/docs/build/html/topics/impala_tablesample.html
@@ -0,0 +1,554 @@
+<!DOCTYPE html
+  SYSTEM "about:legacy-compat">
+<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_select.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="tablesample"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>TABLESAMPLE Clause</title></head><body id="tablesample"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
+
+  <h1 class="title topictitle1" id="ariaid-title1">TABLESAMPLE Clause</h1>
+  
+
+  <div class="body conbody">
+
+    <p class="p">
+      Specify the <code class="ph codeph">TABLESAMPLE</code> clause in cases where you need
+      to explore the data distribution within the table, the table is very large,
+      and it is impractical or unnecessary to process all the data from the table
+      or selected partitions.
+    </p>
+
+    <p class="p">
+      The clause makes the query process a randomized set of data files from the
+      table, so that the total volume of data is greater than or equal to the specified
+      percentage of data bytes within that table. (Or the data bytes within the set of
+      partitions that remain after partition pruning is performed.)
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Syntax:</strong>
+      </p>
+
+<pre class="pre codeblock"><code>
+  <span class="ph">TABLESAMPLE SYSTEM(<var class="keyword varname">percentage</var>) [REPEATABLE(<var class="keyword varname">seed</var>)]</span>
+</code></pre>
+
+    <p class="p">
+      The <code class="ph codeph">TABLESAMPLE</code> clause comes immediately after a table name or table alias.
+    </p>
+
+    <p class="p">
+      The <code class="ph codeph">SYSTEM</code> keyword represents the sampling method. Currently,
+      Impala only supports a single sampling method named <code class="ph codeph">SYSTEM</code>.
+    </p>
+
+    <p class="p">
+      The <var class="keyword varname">percentage</var> argument is an integer literal from 0 to 100.
+      A percentage of 0 produces an empty result set for a particular table reference,
+      while a percentage of 100 uses the entire contents. Because the sampling works by
+      selecting a random set of data files, the proportion of sampled data from the
+      table may be greater than the specified percentage, based on the number and sizes
+      of the underlying data files. See the usage notes for details.
+    </p>
+
+    <p class="p">
+      The optional <code class="ph codeph">REPEATABLE</code> keyword lets you specify an arbitrary
+      positive integer seed value that ensures that when the query is run again, the
+      sampling selects the same set of data files each time. <code class="ph codeph">REPEATABLE</code>
+      does not have a default value. If you omit the <code class="ph codeph">REPEATABLE</code> keyword,
+      the random seed is derived from the current time.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.9.0</span>
+      </p>
+
+    <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+
+    <p class="p">
+      You might use this clause with aggregation queries, such as finding
+      the approximate average, minimum, or maximum where exact precision
+      is not required. You can use these findings to plan the most effective
+      strategy for constructing queries against the full table or designing
+      a partitioning strategy for the data.
+    </p>
+
+    <p class="p">
+      Some other database systems have a <code class="ph codeph">TABLESAMPLE</code> clause.
+      The Impala syntax for this clause is modeled on the syntax for popular
+      relational databases, not the Hive <code class="ph codeph">TABLESAMPLE</code> clause.
+      For example, there is no <code class="ph codeph">BUCKETS</code> keyword as in HiveQL.
+    </p>
+
+    <p class="p">
+      The precision of the <var class="keyword varname">percentage</var> threshold depends on
+      the number and sizes of the underlying data files. Impala brings in
+      additional data files, one at a time, until the number of bytes exceeds
+      the specified percentage based on the total number of bytes for the
+      entire set of table data. The precision of the percentage threshold is higher
+      when the table contains many data files with consistent sizes. See the
+      code listings later in this section for examples.
+    </p>
+
+    <p class="p">
+      When you estimate characteristics of the data distribution based on sampling
+      a percentage of the table data, be aware that the data might be unevenly distributed
+      between different files. Do not assume that the percentage figure reflects the
+      percentage of rows in the table. For example, one file might contain all blank values
+      for a <code class="ph codeph">STRING</code> column, while another file contains long strings
+      in that column; therefore, one file could contain many more rows than another.
+      Likewise, a table created with the <code class="ph codeph">SORT BY</code> clause might
+      contain narrow ranges of values for the sort columns, making it impractical to
+      extrapolate the number of distinct values for those columns based on sampling
+      only some of the data files.
+    </p>
+
+    <p class="p">
+      Because a sample of the table data might not contain all values for a particular
+      column, if the <code class="ph codeph">TABLESAMPLE</code> is used in a join query, the
+      key relationships between the tables might produce incomplete result sets
+      compared to joins using all the table data. For example, if you join 50%
+      of table A with 50% of table B, some values in the join columns might
+      not match between the two tables, even though overall there is a 1:1
+      relationship between the tables.
+    </p>
+
+    <p class="p">
+      The <code class="ph codeph">REPEATABLE</code> keyword makes identical queries use a
+      consistent set of data files when the query is repeated. You specify an
+      arbitrary integer key that acts as a seed value when Impala randomly
+      selects the set of data files to use in the query. This technique
+      lets you verify correctness, examine performance, and so on for queries
+      using the <code class="ph codeph">TABLESAMPLE</code> clause without the sampled data
+      being different each time. The repeatable aspect is reset (that is, the
+      set of selected data files may change) any time the contents of the table
+      change. The statements or operations that can make sampling results
+      non-repeatable are:
+    </p>
+
+    <ul class="ul">
+      <li class="li">
+        <code class="ph codeph">INSERT</code>.
+      </li>
+      <li class="li">
+        <code class="ph codeph">TRUNCATE TABLE</code>.
+      </li>
+      <li class="li">
+        <code class="ph codeph">LOAD DATA</code>.
+      </li>
+      <li class="li">
+        <code class="ph codeph">REFRESH</code> or <code class="ph codeph">INVALIDATE METADATA</code>
+        after files are added or removed by a non-Impala mechanism.
+      </li>
+      <li class="li">
+      </li>
+    </ul>
+
+    <p class="p">
+      This clause is similar in some ways to the <code class="ph codeph">LIMIT</code> clause,
+      because both serve to limit the size of the intermediate data and final
+      result set. <code class="ph codeph">LIMIT 0</code> is more efficient than
+      <code class="ph codeph">TABLESAMPLE SYSTEM(0)</code> for verifying that a query can execute
+      without producing any results. <code class="ph codeph">TABLESAMPLE SYSTEM(<var class="keyword varname">n</var>)</code>
+      often makes query processing more efficient than using a <code class="ph codeph">LIMIT</code> clause
+      by itself, because all phases of query execution use less data overall.
+      If the intent is to retrieve some representative values from the table
+      in an efficient way, you might combine <code class="ph codeph">TABLESAMPLE</code>,
+      <code class="ph codeph">ORDER BY</code>, and <code class="ph codeph">LIMIT</code> clauses within a single query.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Partitioning:</strong>
+      </p>
+    <p class="p">
+      When you query a partitioned table, any partition pruning happens
+      before Impala selects the data files to sample. For example, in a
+      table partitioned by year, a query with <code class="ph codeph">WHERE year = 2017</code>
+      and a <code class="ph codeph">TABLESAMPLE SYSTEM(10)</code> clause would sample
+      data files representing at least 10% of the bytes present in the
+      2017 partition.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Amazon S3 considerations:</strong>
+      </p>
+    <p class="p">
+      This clause applies to S3 tables the same way as tables
+      with data files stored on HDFS.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">ADLS considerations:</strong>
+      </p>
+    <p class="p">
+      This clause applies to ADLS tables the same way as tables
+      with data files stored on HDFS.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Kudu considerations:</strong>
+      </p>
+    <p class="p">
+      This clause does not apply to Kudu tables.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">HBase considerations:</strong>
+      </p>
+    <p class="p">
+      This clause does not apply to HBase tables.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Performance considerations:</strong>
+      </p>
+    <p class="p">
+      From a performance perspective, the <code class="ph codeph">TABLESAMPLE</code>
+      clause is especially valuable for exploratory queries on
+      text, Avro, or other file formats other than Parquet. Text-based
+      or row-oriented file formats must process substantial amounts of
+      redundant data for queries that derive aggregate results such as
+      <code class="ph codeph">MAX()</code>, <code class="ph codeph">MIN()</code>, or <code class="ph codeph">AVG()</code>
+      for a single column. Therefore, you might use <code class="ph codeph">TABLESAMPLE</code>
+      early in the ETL pipeline, when data is still in raw text format
+      and has not been converted to Parquet or moved into a partitioned
+      table.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Restrictions:</strong>
+      </p>
+
+    <p class="p">
+      This clause applies only to tables that use a storage layer
+      with underlying raw data files, such as HDFS, Amazon S3,
+      or Microsoft ADLS.
+    </p>
+
+    <p class="p">
+      This clause does not apply to table references that represent views.
+      A query that applies the <code class="ph codeph">TABLESAMPLE</code> clause to a
+      view or a subquery fails with a semantic error.
+    </p>
+
+    <p class="p">
+      Because the sampling works at the level of entire data files, it
+      is by nature coarse-grained. It is possible to specify a small
+      sample percentage but still process a substantial portion of the
+      table data if the table contains relatively few data files, if
+      each data file is very large, or if the data files vary substantially
+      in size. Be sure that you understand the data distribution and physical
+      file layout so that you can verify if the results are suitable for
+      extrapolation. For example, if the table contains only a single data file,
+      the <span class="q">"sample"</span> will consist of all the table data regardless of
+      the percentage you specify. If the table contains data files of
+      1 GiB, 1 GiB, and 1 KiB, when you specify a sampling percentage of
+      50 you would either process slightly more than 50% of the table
+      (1 GiB + 1 KiB) or almost the entire table (1 GiB + 1 GiB),
+      depending on which data files were selected for sampling.
+    </p>
+
+    <p class="p">
+      If data files are added by a non-Impala mechanism, and the
+      table metadata is not updated by a <code class="ph codeph">REFRESH</code>
+      or <code class="ph codeph">INVALIDATE METADATA</code> statement, the
+      <code class="ph codeph">TABLESAMPLE</code> clause does not consider those
+      new files when computing the number of bytes in the table
+      or selecting which files to sample.
+    </p>
+
+    <p class="p">
+      If data files are removed by a non-Impala mechanism, and the
+      table metadata is not updated by a <code class="ph codeph">REFRESH</code>
+      or <code class="ph codeph">INVALIDATE METADATA</code> statement, the
+      query fails if the <code class="ph codeph">TABLESAMPLE</code> clause
+      attempts to reference any of the missing files.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+
+    <p class="p">
+      The following examples demonstrate the <code class="ph codeph">TABLESAMPLE</code> clause.
+      These examples intentionally use very small data sets to illustrate how
+      the number of files, size of each file, and overall size of data in the table
+      interact with the percentage specified in the clause.
+    </p>
+
+    <p class="p">
+      These examples use an unpartitioned table, containing several files of roughly
+      the same size:
+    </p>
+
+<pre class="pre codeblock"><code>
+create table sample_demo (x int, s string);
+
+insert into sample_demo values (1, 'one');
+insert into sample_demo values (2, 'two');
+insert into sample_demo values (3, 'three');
+insert into sample_demo values (4, 'four');
+insert into sample_demo values (5, 'five');
+
+show files in sample_demo;
++---------------------+------+-----------+
+| Path                | Size | Partition |
++---------------------+------+-----------+
+| 991213608_data.0.   | 7B   |           |
+| 982196806_data.0.   | 6B   |           |
+| _2122096884_data.0. | 8B   |           |
+| _586325431_data.0.  | 6B   |           |
+| 1894746258_data.0.  | 7B   |           |
++---------------------+------+-----------+
+
+show table stats sample_demo;
++-------+--------+------+--------+-------------------------+
+| #Rows | #Files | Size | Format | Location                |
++-------+--------+------+--------+-------------------------+
+| -1    | 5      | 34B  | TEXT   | /tsample.db/sample_demo |
++-------+--------+------+--------+-------------------------+
+&lt;/codeblock&gt;
+
+    &lt;p&gt;
+      A query that samples 50% of the table must process at least
+      17 bytes of data. Based on the sizes of the data files,
+      we can predict that each such query uses 3 arbitrary files.
+      Any 1 or 2 files are not enough to reach 50% of the total
+      data in the table (34 bytes), so the query adds more files
+      until it passes the 50% threshold:
+    &lt;/p&gt;
+
+&lt;codeblock&gt;&lt;![CDATA[
+select distinct x from sample_demo tablesample system(50);
++---+
+| x |
++---+
+| 4 |
+| 1 |
+| 5 |
++---+
+
+select distinct x from sample_demo tablesample system(50);
++---+
+| x |
++---+
+| 5 |
+| 4 |
+| 2 |
++---+
+
+select distinct x from sample_demo tablesample system(50);
++---+
+| x |
++---+
+| 5 |
+| 3 |
+| 2 |
++---+
+&lt;/codeblock&gt;
+
+    &lt;p&gt;
+      To help run reproducible experiments, the &lt;codeph&gt;REPEATABLE&lt;/codeph&gt;
+      clause causes Impala to choose the same set of files for each query.
+      Although the data set being considered is deterministic, the order
+      of results varies (in the absence of an &lt;codeph&gt;ORDER BY&lt;/codeph&gt;
+      clause) because of the way distributed queries are processed:
+    &lt;/p&gt;
+
+&lt;codeblock&gt;&lt;![CDATA[
+select distinct x from sample_demo
+  tablesample system(50) repeatable (12345);
++---+
+| x |
++---+
+| 3 |
+| 2 |
+| 1 |
++---+
+
+select distinct x from sample_demo
+  tablesample system(50) repeatable (12345);
++---+
+| x |
++---+
+| 2 |
+| 1 |
+| 3 |
++---+
+&lt;/codeblock&gt;
+
+    &lt;p&gt;
+      The following examples show how uneven data distribution affects
+      which data is sampled. Adding another data file containing a long
+      string value changes the threshold for 50% of the total data in
+      the table:
+    &lt;/p&gt;
+
+&lt;codeblock&gt;&lt;![CDATA[
+insert into sample_demo values (1000, 'Boyhood is the longest time in li
+fe for a boy. The last term of the school-year is made of decades, not o
+f weeks, and living through them is like waiting for the millennium. Boo
+th Tarkington');
+
+show files in sample_demo;
++---------------------+------+-----------+
+| Path                | Size | Partition |
++---------------------+------+-----------+
+| 991213608_data.0.   | 7B   |           |
+| 982196806_data.0.   | 6B   |           |
+| _253317650_data.0.  | 196B |           |
+| _2122096884_data.0. | 8B   |           |
+| _586325431_data.0.  | 6B   |           |
+| 1894746258_data.0.  | 7B   |           |
++---------------------+------+-----------+
+
+show table stats sample_demo;
++-------+--------+------+--------+-------------------------+
+| #Rows | #Files | Size | Format | Location                |
++-------+--------+------+--------+-------------------------+
+| -1    | 6      | 230B | TEXT   | /tsample.db/sample_demo |
++-------+--------+------+--------+-------------------------+
+&lt;/codeblock&gt;
+
+    &lt;p&gt;
+      Even though the queries do not refer to the &lt;codeph&gt;S&lt;/codeph&gt;
+      column containing the long value, all the sampling queries include
+      the data file containing the column value &lt;codeph&gt;X=1000&lt;/codeph&gt;,
+      because the query cannot reach the 50% threshold (115 bytes) without
+      including that file. The large file might be considered first, in which
+      case it is the only file processed by the query. Or an arbitrary
+      set of other files might be considered first.
+    &lt;/p&gt;
+
+&lt;codeblock&gt;&lt;![CDATA[
+select distinct x from sample_demo tablesample system(50);
++------+
+| x    |
++------+
+| 1000 |
+| 3    |
+| 1    |
++------+
+
+select distinct x from sample_demo tablesample system(50);
++------+
+| x    |
++------+
+| 1000 |
++------+
+
+select distinct x from sample_demo tablesample system(50);
++------+
+| x    |
++------+
+| 1000 |
+| 4    |
+| 2    |
+| 1    |
++------+
+&lt;/codeblock&gt;
+
+    &lt;p&gt;
+      The following examples demonstrate how the &lt;codeph&gt;TABLESAMPLE&lt;/codeph&gt;
+      clause interacts with other table aspects, such as partitioning and file
+      format:
+    &lt;/p&gt;
+
+&lt;codeblock&gt;&lt;![CDATA[
+create table sample_demo_partitions (x int, s string) partitioned by (n int) stored as parquet;
+
+insert into sample_demo_partitions partition (n = 1) select * from sample_demo;
+insert into sample_demo_partitions partition (n = 2) select * from sample_demo;
+insert into sample_demo_partitions partition (n = 3) select * from sample_demo;
+
+show files in sample_demo_partitions;
++--------------------------------+--------+-----------+
+| Path                           | Size   | Partition |
++--------------------------------+--------+-----------+
+| 000000_364262785_data.0.parq   | 1.24KB | n=1       |
+| 000001_973526736_data.0.parq   | 566B   | n=1       |
+| 0000000_1300598134_data.0.parq | 1.24KB | n=2       |
+| 0000001_689099063_data.0.parq  | 568B   | n=2       |
+| 0000000_1861371709_data.0.parq | 1.24KB | n=3       |
+| 0000001_1065507912_data.0.parq | 566B   | n=3       |
++--------------------------------+--------+-----------+
+
+show table stats tablesample_demo_partitioned;
++-------+-------+--------+--------+---------+----------------------------------------------+
+| n     | #Rows | #Files | Size   | Format  | Location                                     |
++-------+-------+--------+--------+---------+----------------------------------------------+
+| 1     | -1    | 2      | 1.79KB | PARQUET | /tsample.db/tablesample_demo_partitioned/n=1 |
+| 2     | -1    | 2      | 1.80KB | PARQUET | /tsample.db/tablesample_demo_partitioned/n=2 |
+| 3     | -1    | 2      | 1.79KB | PARQUET | /tsample.db/tablesample_demo_partitioned/n=3 |
+| Total | -1    | 6      | 5.39KB |         |                                              |
++-------+-------+--------+--------+---------+----------------------------------------------+
+&lt;/codeblock&gt;
+
+    &lt;p&gt;
+      If the query does not involve any partition pruning, the
+      sampling applies to the data volume of the entire table:
+    &lt;/p&gt;
+
+&lt;codeblock&gt;&lt;![CDATA[
+-- 18 rows total.
+select count(*) from sample_demo_partitions;
++----------+
+| count(*) |
++----------+
+| 18       |
++----------+
+
+-- The number of rows per data file is not
+-- perfectly balanced, therefore the count
+-- is different depending on which set of files
+-- is considered.
+select count(*) from sample_demo_partitions
+  tablesample system(75);
++----------+
+| count(*) |
++----------+
+| 14       |
++----------+
+
+select count(*) from sample_demo_partitions
+  tablesample system(75);
++----------+
+| count(*) |
++----------+
+| 16       |
++----------+
+&lt;/codeblock&gt;
+
+    &lt;p&gt;
+      If the query only processes certain partitions,
+      the query computes the sampling threshold based on
+      the data size and set of files only from the
+      relevant partitions:
+    &lt;/p&gt;
+
+&lt;codeblock&gt;&lt;![CDATA[
+select count(*) from sample_demo_partitions
+  tablesample system(50) where n = 1;
++----------+
+| count(*) |
++----------+
+| 6        |
++----------+
+
+select count(*) from sample_demo_partitions
+  tablesample system(50) where n = 1;
++----------+
+| count(*) |
++----------+
+| 2        |
++----------+
+
+</code></pre>
+
+    <p class="p">
+        <strong class="ph b">Related information:</strong>
+      </p>
+    <p class="p">
+      <a class="xref" href="impala_select.html#select">SELECT Statement</a>
+    </p>
+
+  </div>
+<nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_select.html">SELECT Statement</a></div></div></nav></article></main></body></html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_upgrading.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_upgrading.html b/docs/build/html/topics/impala_upgrading.html
index 25e8397..fcd43ac 100644
--- a/docs/build/html/topics/impala_upgrading.html
+++ b/docs/build/html/topics/impala_upgrading.html
@@ -95,8 +95,8 @@ $ ps ax | grep [c]atalogd
               <code class="ph codeph">impalad</code> if the service started successfully.
 <pre class="pre codeblock"><code>$ sudo service impala-server start
 $ ps ax | grep [i]mpalad
- 7936 ?        Sl     0:12 /usr/lib/impala/sbin/impalad -log_dir=/var/log/impala -state_store_port=24000 -use_statestore
--state_store_host=127.0.0.1 -be_port=22000
+ 7936 ?        Sl     0:12 /usr/lib/impala/sbin/impalad -log_dir=/var/log/impala -state_store_port=24000
+ -state_store_host=127.0.0.1 -be_port=22000
 </code></pre>
             </li>
           </ol>

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_views.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_views.html b/docs/build/html/topics/impala_views.html
index ca6595a..fa1dd0e 100644
--- a/docs/build/html/topics/impala_views.html
+++ b/docs/build/html/topics/impala_views.html
@@ -202,6 +202,13 @@ Query finished, fetching results ...
       </p>
 
     <p class="p">
+        The <code class="ph codeph">STRAIGHT_JOIN</code> hint affects the join order of table references in the query
+        block containing the hint. It does not affect the join order of nested queries, such as views,
+        inline views, or <code class="ph codeph">WHERE</code>-clause subqueries. To use this hint for performance
+        tuning of complex queries, apply the hint to all query blocks that need a fixed join order.
+      </p>
+
+    <p class="p">
         <strong class="ph b">Restrictions:</strong>
       </p>
 
@@ -274,6 +281,15 @@ Query finished, fetching results ...
 </code></pre>
       </div>
       </li>
+      <li class="li">
+        <p class="p">
+        The <code class="ph codeph">TABLESAMPLE</code> clause of the <code class="ph codeph">SELECT</code>
+        statement does not apply to a table reference derived from a view, a subquery,
+        or anything other than a real base table. This clause only works for tables
+        backed by HDFS or HDFS-like data files, therefore it does not apply to Kudu or
+        HBase tables.
+      </p>
+      </li>
     </ul>
 
     <p class="p">



[3/7] incubator-impala git commit: Update Impala docs for 2.10 release

Posted by jr...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_min_spillable_buffer_size.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_min_spillable_buffer_size.html b/docs/build/html/topics/impala_min_spillable_buffer_size.html
new file mode 100644
index 0000000..d0aa371
--- /dev/null
+++ b/docs/build/html/topics/impala_min_spillable_buffer_size.html
@@ -0,0 +1,87 @@
+<!DOCTYPE html
+  SYSTEM "about:legacy-compat">
+<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_query_options.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="min_spillable_buffer_size"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>MIN_SPILLABLE_BUFFER_SIZE Query Option</title></head><body id="min_spillable_buffer_size"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
+
+  <h1 class="title topictitle1" id="ariaid-title1">MIN_SPILLABLE_BUFFER_SIZE Query Option</h1>
+  
+  
+
+  <div class="body conbody">
+
+    <p class="p">
+      
+      Specifies the minimum size for a memory buffer used when the
+      spill-to-disk mechanism is activated, for example for queries against
+      a large table with no statistics, or large join operations.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Type:</strong> integer
+      </p>
+
+
+
+    <p class="p">
+        <strong class="ph b">Default:</strong>
+      </p>
+    <p class="p">
+      <code class="ph codeph">65536</code> (64 KB)
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Units:</strong> A numeric argument represents a size in bytes; you can also use a suffix of <code class="ph codeph">m</code>
+        or <code class="ph codeph">mb</code> for megabytes, or <code class="ph codeph">g</code> or <code class="ph codeph">gb</code> for gigabytes. If you
+        specify a value with unrecognized formats, subsequent queries fail with an error.
+      </p>
+
+    <p class="p">
+        <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.10.0</span>
+      </p>
+
+    <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+    <p class="p">
+      This query option sets a lower bound on the size of the internal
+      buffer size that can be used during spill-to-disk operations. The
+      actual size of the buffer is chosen by the query planner.
+    </p>
+    <p class="p">
+      If overall query performance is limited by the time needed for spilling,
+      consider increasing the <code class="ph codeph">MIN_SPILLABLE_BUFFER_SIZE</code> setting.
+      Larger buffer sizes result in Impala issuing larger I/O requests to storage
+      devices, which might result in higher throughput, particularly on rotational
+      disks.
+    </p>
+    <p class="p">
+      The tradeoff with a large value for this setting is increased memory usage during
+      spill-to-disk operations. Reducing this value may reduce memory consumption.
+    </p>
+    <p class="p">
+      To determine if the value for this setting is having an effect by capping the
+      spillable buffer size, you can see the buffer size chosen by the query planner for
+      a particular query. <code class="ph codeph">EXPLAIN</code> the query while the setting
+      <code class="ph codeph">EXPLAIN_LEVEL=2</code> is in effect.
+    </p>
+
+    <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+
+<pre class="pre codeblock"><code>
+set min_spillable_buffer_size=128KB;
+
+</code></pre>
+
+    <p class="p">
+        <strong class="ph b">Related information:</strong>
+      </p>
+    <p class="p">
+      <a class="xref" href="impala_buffer_pool_limit.html">BUFFER_POOL_LIMIT Query Option</a>,
+      <a class="xref" href="impala_default_spillable_buffer_size.html">DEFAULT_SPILLABLE_BUFFER_SIZE Query Option</a>,
+      <a class="xref" href="impala_max_row_size.html">MAX_ROW_SIZE Query Option</a>,
+      <a class="xref" href="impala_scalability.html">Scalability Considerations for Impala</a>
+    </p>
+
+  </div>
+<nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_query_options.html">Query Options for the SET Statement</a></div></div></nav></article></main></body></html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_new_features.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_new_features.html b/docs/build/html/topics/impala_new_features.html
index 7413a22..4db2258 100644
--- a/docs/build/html/topics/impala_new_features.html
+++ b/docs/build/html/topics/impala_new_features.html
@@ -18,15 +18,32 @@
 
 
 
-  <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_release_notes.html">Impala Release Notes</a></div></div></nav><article class="topic concept nested1" aria-labelledby="ariaid-title2" id="new_features__new_features_290">
+  <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_release_notes.html">Impala Release Notes</a></div></div></nav><article class="topic concept nested1" aria-labelledby="ariaid-title2" id="new_features__new_features_2100">
 
-    <h2 class="title topictitle2" id="ariaid-title2">New Features in <span class="keyword">Impala 2.9</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title2">New Features in <span class="keyword">Impala 2.10</span></h2>
 
     <div class="body conbody">
 
       <p class="p">
         For the full list of issues closed in this release, including the issues
-        marked as <span class="q">"new features"</span>, see the
+        marked as <span class="q">"new features"</span> or <span class="q">"improvements"</span>, see the
+        <a class="xref" href="https://impala.incubator.apache.org/docs/changelog-2.10.html" target="_blank">changelog for <span class="keyword">Impala 2.10</span></a>.
+      </p>
+
+    </div>
+  </article>
+
+
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title3" id="new_features__new_features_290">
+
+    <h2 class="title topictitle2" id="ariaid-title3">New Features in <span class="keyword">Impala 2.9</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        For the full list of issues closed in this release, including the issues
+        marked as <span class="q">"new features"</span> or <span class="q">"improvements"</span>, see the
         <a class="xref" href="https://impala.incubator.apache.org/docs/changelog-2.9.html" target="_blank">changelog for <span class="keyword">Impala 2.9</span></a>.
       </p>
 
@@ -59,9 +76,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title3" id="new_features__new_features_280">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title4" id="new_features__new_features_280">
 
-    <h2 class="title topictitle2" id="ariaid-title3">New Features in <span class="keyword">Impala 2.8</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title4">New Features in <span class="keyword">Impala 2.8</span></h2>
 
     <div class="body conbody">
 
@@ -430,9 +447,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title4" id="new_features__new_features_270">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title5" id="new_features__new_features_270">
 
-    <h2 class="title topictitle2" id="ariaid-title4">New Features in <span class="keyword">Impala 2.7</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title5">New Features in <span class="keyword">Impala 2.7</span></h2>
 
     <div class="body conbody">
 
@@ -551,9 +568,9 @@
   </article>
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title5" id="new_features__new_features_260">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title6" id="new_features__new_features_260">
 
-    <h2 class="title topictitle2" id="ariaid-title5">New Features in <span class="keyword">Impala 2.6</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title6">New Features in <span class="keyword">Impala 2.6</span></h2>
 
     <div class="body conbody">
 
@@ -871,9 +888,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title6" id="new_features__new_features_250">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title7" id="new_features__new_features_250">
 
-    <h2 class="title topictitle2" id="ariaid-title6">New Features in <span class="keyword">Impala 2.5</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title7">New Features in <span class="keyword">Impala 2.5</span></h2>
 
     <div class="body conbody">
 
@@ -1277,9 +1294,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title7" id="new_features__new_features_240">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title8" id="new_features__new_features_240">
 
-    <h2 class="title topictitle2" id="ariaid-title7">New Features in <span class="keyword">Impala 2.4</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title8">New Features in <span class="keyword">Impala 2.4</span></h2>
 
     <div class="body conbody">
 
@@ -1299,9 +1316,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title8" id="new_features__new_features_230">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title9" id="new_features__new_features_230">
 
-    <h2 class="title topictitle2" id="ariaid-title8">New Features in <span class="keyword">Impala 2.3</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title9">New Features in <span class="keyword">Impala 2.3</span></h2>
 
     <div class="body conbody">
 
@@ -1670,9 +1687,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title9" id="new_features__new_features_220">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title10" id="new_features__new_features_220">
 
-    <h2 class="title topictitle2" id="ariaid-title9">New Features in <span class="keyword">Impala 2.8</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title10">New Features in <span class="keyword">Impala 2.8</span></h2>
 
     <div class="body conbody">
 
@@ -1916,9 +1933,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title10" id="new_features__new_features_210">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title11" id="new_features__new_features_210">
 
-    <h2 class="title topictitle2" id="ariaid-title10">New Features in <span class="keyword">Impala 2.1</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title11">New Features in <span class="keyword">Impala 2.1</span></h2>
 
     <div class="body conbody">
 
@@ -1972,9 +1989,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title11" id="new_features__new_features_200">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title12" id="new_features__new_features_200">
 
-    <h2 class="title topictitle2" id="ariaid-title11">New Features in <span class="keyword">Impala 2.0</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title12">New Features in <span class="keyword">Impala 2.0</span></h2>
 
     <div class="body conbody">
 
@@ -2283,9 +2300,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title12" id="new_features__new_features_140">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title13" id="new_features__new_features_140">
 
-    <h2 class="title topictitle2" id="ariaid-title12">New Features in <span class="keyword">Impala 1.4</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title13">New Features in <span class="keyword">Impala 1.4</span></h2>
 
     <div class="body conbody">
 
@@ -2529,9 +2546,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title13" id="new_features__new_features_132">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title14" id="new_features__new_features_132">
 
-    <h2 class="title topictitle2" id="ariaid-title13">New Features in <span class="keyword">Impala 1.3.2</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title14">New Features in <span class="keyword">Impala 1.3.2</span></h2>
 
     <div class="body conbody">
 
@@ -2544,9 +2561,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title14" id="new_features__new_features_131">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title15" id="new_features__new_features_131">
 
-    <h2 class="title topictitle2" id="ariaid-title14">New Features in Impala 1.3.1</h2>
+    <h2 class="title topictitle2" id="ariaid-title15">New Features in Impala 1.3.1</h2>
 
     <div class="body conbody">
 
@@ -2598,9 +2615,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title15" id="new_features__new_features_130">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title16" id="new_features__new_features_130">
 
-    <h2 class="title topictitle2" id="ariaid-title15">New Features in <span class="keyword">Impala 1.3</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title16">New Features in <span class="keyword">Impala 1.3</span></h2>
 
     <div class="body conbody">
 
@@ -2722,9 +2739,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title16" id="new_features__new_features_124">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title17" id="new_features__new_features_124">
 
-    <h2 class="title topictitle2" id="ariaid-title16">New Features in Impala 1.2.4</h2>
+    <h2 class="title topictitle2" id="ariaid-title17">New Features in Impala 1.2.4</h2>
 
     <div class="body conbody">
 
@@ -2796,9 +2813,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title17" id="new_features__new_features_123">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title18" id="new_features__new_features_123">
 
-    <h2 class="title topictitle2" id="ariaid-title17">New Features in Impala 1.2.3</h2>
+    <h2 class="title topictitle2" id="ariaid-title18">New Features in Impala 1.2.3</h2>
 
     <div class="body conbody">
 
@@ -2813,9 +2830,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title18" id="new_features__new_features_122">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title19" id="new_features__new_features_122">
 
-    <h2 class="title topictitle2" id="ariaid-title18">New Features in Impala 1.2.2</h2>
+    <h2 class="title topictitle2" id="ariaid-title19">New Features in Impala 1.2.2</h2>
 
     <div class="body conbody">
 
@@ -2944,9 +2961,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title19" id="new_features__new_features_121">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title20" id="new_features__new_features_121">
 
-    <h2 class="title topictitle2" id="ariaid-title19">New Features in Impala 1.2.1</h2>
+    <h2 class="title topictitle2" id="ariaid-title20">New Features in Impala 1.2.1</h2>
 
     <div class="body conbody">
 
@@ -3135,9 +3152,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title20" id="new_features__new_features_120">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title21" id="new_features__new_features_120">
 
-    <h2 class="title topictitle2" id="ariaid-title20">New Features in Impala 1.2.0 (Beta)</h2>
+    <h2 class="title topictitle2" id="ariaid-title21">New Features in Impala 1.2.0 (Beta)</h2>
 
     <div class="body conbody">
 
@@ -3300,9 +3317,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title21" id="new_features__new_features_111">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title22" id="new_features__new_features_111">
 
-    <h2 class="title topictitle2" id="ariaid-title21">New Features in Impala 1.1.1</h2>
+    <h2 class="title topictitle2" id="ariaid-title22">New Features in Impala 1.1.1</h2>
 
     <div class="body conbody">
 
@@ -3340,9 +3357,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title22" id="new_features__new_features_11">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title23" id="new_features__new_features_11">
 
-    <h2 class="title topictitle2" id="ariaid-title22">New Features in Impala 1.1</h2>
+    <h2 class="title topictitle2" id="ariaid-title23">New Features in Impala 1.1</h2>
 
     <div class="body conbody">
 
@@ -3474,9 +3491,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title23" id="new_features__new_features_101">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title24" id="new_features__new_features_101">
 
-    <h2 class="title topictitle2" id="ariaid-title23">New Features in Impala 1.0.1</h2>
+    <h2 class="title topictitle2" id="ariaid-title24">New Features in Impala 1.0.1</h2>
 
     <div class="body conbody">
 
@@ -3511,9 +3528,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title24" id="new_features__new_features_10">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title25" id="new_features__new_features_10">
 
-    <h2 class="title topictitle2" id="ariaid-title24">New Features in Impala 1.0</h2>
+    <h2 class="title topictitle2" id="ariaid-title25">New Features in Impala 1.0</h2>
 
     <div class="body conbody">
 
@@ -3547,9 +3564,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title25" id="new_features__new_features_07">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title26" id="new_features__new_features_07">
 
-    <h2 class="title topictitle2" id="ariaid-title25">New Features in Version 0.7 of the Impala Beta Release</h2>
+    <h2 class="title topictitle2" id="ariaid-title26">New Features in Version 0.7 of the Impala Beta Release</h2>
 
     <div class="body conbody">
 
@@ -3602,9 +3619,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title26" id="new_features__new_features_06">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title27" id="new_features__new_features_06">
 
-    <h2 class="title topictitle2" id="ariaid-title26">New Features in Version 0.6 of the Impala Beta Release</h2>
+    <h2 class="title topictitle2" id="ariaid-title27">New Features in Version 0.6 of the Impala Beta Release</h2>
 
     <div class="body conbody">
 
@@ -3640,9 +3657,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title27" id="new_features__new_features_05">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title28" id="new_features__new_features_05">
 
-    <h2 class="title topictitle2" id="ariaid-title27">New Features in Version 0.5 of the Impala Beta Release</h2>
+    <h2 class="title topictitle2" id="ariaid-title28">New Features in Version 0.5 of the Impala Beta Release</h2>
 
     <div class="body conbody">
 
@@ -3663,9 +3680,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title28" id="new_features__new_features_04">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title29" id="new_features__new_features_04">
 
-    <h2 class="title topictitle2" id="ariaid-title28">New Features in Version 0.4 of the Impala Beta Release</h2>
+    <h2 class="title topictitle2" id="ariaid-title29">New Features in Version 0.4 of the Impala Beta Release</h2>
 
     <div class="body conbody">
 
@@ -3695,9 +3712,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title29" id="new_features__new_features_03">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title30" id="new_features__new_features_03">
 
-    <h2 class="title topictitle2" id="ariaid-title29">New Features in Version 0.3 of the Impala Beta Release</h2>
+    <h2 class="title topictitle2" id="ariaid-title30">New Features in Version 0.3 of the Impala Beta Release</h2>
 
     <div class="body conbody">
 
@@ -3720,9 +3737,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title30" id="new_features__new_features_02">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title31" id="new_features__new_features_02">
 
-    <h2 class="title topictitle2" id="ariaid-title30">New Features in Version 0.2 of the Impala Beta Release</h2>
+    <h2 class="title topictitle2" id="ariaid-title31">New Features in Version 0.2 of the Impala Beta Release</h2>
 
     <div class="body conbody">
 

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_partitioning.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_partitioning.html b/docs/build/html/topics/impala_partitioning.html
index b361083..9a90836 100644
--- a/docs/build/html/topics/impala_partitioning.html
+++ b/docs/build/html/topics/impala_partitioning.html
@@ -650,4 +650,152 @@ explain select s from yy2 where year in (select year from yy where year between
 
   </article>
 
+  <article class="topic concept nested1" aria-labelledby="ariaid-title15" id="partitioning__partition_stats">
+    <h2 class="title topictitle2" id="ariaid-title15">Keeping Statistics Up to Date for Partitioned Tables</h2>
+    <div class="body conbody">
+
+      <p class="p">
+        Because the <code class="ph codeph">COMPUTE STATS</code> statement can be resource-intensive to run on a partitioned table
+        as new partitions are added, Impala includes a variation of this statement that allows computing statistics
+        on a per-partition basis such that stats can be incrementally updated when new partitions are added.
+      </p>
+
+      <div class="note important note_important"><span class="note__title importanttitle">Important:</span> 
+        <p class="p">
+        For a particular table, use either <code class="ph codeph">COMPUTE STATS</code> or
+        <code class="ph codeph">COMPUTE INCREMENTAL STATS</code>, but never combine the two or alternate
+        between them. If you switch from <code class="ph codeph">COMPUTE STATS</code> to
+        <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> during the lifetime of a table, or vice
+        versa, drop all statistics (by running both <code class="ph codeph">DROP STATS</code> and
+        <code class="ph codeph">DROP INCREMENTAL STATS</code>) before making the switch.
+      </p>
+        <p class="p">
+        When you run <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> on a table for the first time,
+        the statistics are computed again from scratch regardless of whether the table already
+        has statistics. Therefore, expect a one-time resource-intensive operation
+        for scanning the entire table when running <code class="ph codeph">COMPUTE INCREMENTAL STATS</code>
+        for the first time on a given table.
+      </p>
+        <p class="p">
+        For a table with a huge number of partitions and many columns, the approximately 400 bytes
+        of metadata per column per partition can add up to significant memory overhead, as it must
+        be cached on the <span class="keyword cmdname">catalogd</span> host and on every <span class="keyword cmdname">impalad</span> host
+        that is eligible to be a coordinator. If this metadata for all tables combined exceeds 2 GB,
+        you might experience service downtime.
+      </p>
+      </div>
+
+      <p class="p">
+        The <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> variation computes statistics only for partitions that were
+        added or changed since the last <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> statement, rather than the entire
+        table. It is typically used for tables where a full <code class="ph codeph">COMPUTE STATS</code>
+        operation takes too long to be practical each time a partition is added or dropped. See
+        <a class="xref" href="impala_perf_stats.html#perf_stats_incremental">Overview of Incremental Statistics</a> for full usage details.
+      </p>
+
+<pre class="pre codeblock"><code>-- Initially the table has no incremental stats, as indicated
+-- 'false' under Incremental stats.
+show table stats item_partitioned;
++-------------+-------+--------+----------+--------------+---------+------------------
+| i_category  | #Rows | #Files | Size     | Bytes Cached | Format  | Incremental stats
++-------------+-------+--------+----------+--------------+---------+------------------
+| Books       | -1    | 1      | 223.74KB | NOT CACHED   | PARQUET | false
+| Children    | -1    | 1      | 230.05KB | NOT CACHED   | PARQUET | false
+| Electronics | -1    | 1      | 232.67KB | NOT CACHED   | PARQUET | false
+| Home        | -1    | 1      | 232.56KB | NOT CACHED   | PARQUET | false
+| Jewelry     | -1    | 1      | 223.72KB | NOT CACHED   | PARQUET | false
+| Men         | -1    | 1      | 231.25KB | NOT CACHED   | PARQUET | false
+| Music       | -1    | 1      | 237.90KB | NOT CACHED   | PARQUET | false
+| Shoes       | -1    | 1      | 234.90KB | NOT CACHED   | PARQUET | false
+| Sports      | -1    | 1      | 227.97KB | NOT CACHED   | PARQUET | false
+| Women       | -1    | 1      | 226.27KB | NOT CACHED   | PARQUET | false
+| Total       | -1    | 10     | 2.25MB   | 0B           |         |
++-------------+-------+--------+----------+--------------+---------+------------------
+
+-- After the first COMPUTE INCREMENTAL STATS,
+-- all partitions have stats. The first
+-- COMPUTE INCREMENTAL STATS scans the whole
+-- table, discarding any previous stats from
+-- a traditional COMPUTE STATS statement.
+compute incremental stats item_partitioned;
++-------------------------------------------+
+| summary                                   |
++-------------------------------------------+
+| Updated 10 partition(s) and 21 column(s). |
++-------------------------------------------+
+show table stats item_partitioned;
++-------------+-------+--------+----------+--------------+---------+------------------
+| i_category  | #Rows | #Files | Size     | Bytes Cached | Format  | Incremental stats
++-------------+-------+--------+----------+--------------+---------+------------------
+| Books       | 1733  | 1      | 223.74KB | NOT CACHED   | PARQUET | true
+| Children    | 1786  | 1      | 230.05KB | NOT CACHED   | PARQUET | true
+| Electronics | 1812  | 1      | 232.67KB | NOT CACHED   | PARQUET | true
+| Home        | 1807  | 1      | 232.56KB | NOT CACHED   | PARQUET | true
+| Jewelry     | 1740  | 1      | 223.72KB | NOT CACHED   | PARQUET | true
+| Men         | 1811  | 1      | 231.25KB | NOT CACHED   | PARQUET | true
+| Music       | 1860  | 1      | 237.90KB | NOT CACHED   | PARQUET | true
+| Shoes       | 1835  | 1      | 234.90KB | NOT CACHED   | PARQUET | true
+| Sports      | 1783  | 1      | 227.97KB | NOT CACHED   | PARQUET | true
+| Women       | 1790  | 1      | 226.27KB | NOT CACHED   | PARQUET | true
+| Total       | 17957 | 10     | 2.25MB   | 0B           |         |
++-------------+-------+--------+----------+--------------+---------+------------------
+
+-- Add a new partition...
+alter table item_partitioned add partition (i_category='Camping');
+-- Add or replace files in HDFS outside of Impala,
+-- rendering the stats for a partition obsolete.
+!import_data_into_sports_partition.sh
+refresh item_partitioned;
+drop incremental stats item_partitioned partition (i_category='Sports');
+-- Now some partitions have incremental stats
+-- and some do not.
+show table stats item_partitioned;
++-------------+-------+--------+----------+--------------+---------+------------------
+| i_category  | #Rows | #Files | Size     | Bytes Cached | Format  | Incremental stats
++-------------+-------+--------+----------+--------------+---------+------------------
+| Books       | 1733  | 1      | 223.74KB | NOT CACHED   | PARQUET | true
+| Camping     | -1    | 1      | 408.02KB | NOT CACHED   | PARQUET | false
+| Children    | 1786  | 1      | 230.05KB | NOT CACHED   | PARQUET | true
+| Electronics | 1812  | 1      | 232.67KB | NOT CACHED   | PARQUET | true
+| Home        | 1807  | 1      | 232.56KB | NOT CACHED   | PARQUET | true
+| Jewelry     | 1740  | 1      | 223.72KB | NOT CACHED   | PARQUET | true
+| Men         | 1811  | 1      | 231.25KB | NOT CACHED   | PARQUET | true
+| Music       | 1860  | 1      | 237.90KB | NOT CACHED   | PARQUET | true
+| Shoes       | 1835  | 1      | 234.90KB | NOT CACHED   | PARQUET | true
+| Sports      | -1    | 1      | 227.97KB | NOT CACHED   | PARQUET | false
+| Women       | 1790  | 1      | 226.27KB | NOT CACHED   | PARQUET | true
+| Total       | 17957 | 11     | 2.65MB   | 0B           |         |
++-------------+-------+--------+----------+--------------+---------+------------------
+
+-- After another COMPUTE INCREMENTAL STATS,
+-- all partitions have incremental stats, and only the 2
+-- partitions without incremental stats were scanned.
+compute incremental stats item_partitioned;
++------------------------------------------+
+| summary                                  |
++------------------------------------------+
+| Updated 2 partition(s) and 21 column(s). |
++------------------------------------------+
+show table stats item_partitioned;
++-------------+-------+--------+----------+--------------+---------+------------------
+| i_category  | #Rows | #Files | Size     | Bytes Cached | Format  | Incremental stats
++-------------+-------+--------+----------+--------------+---------+------------------
+| Books       | 1733  | 1      | 223.74KB | NOT CACHED   | PARQUET | true
+| Camping     | 5328  | 1      | 408.02KB | NOT CACHED   | PARQUET | true
+| Children    | 1786  | 1      | 230.05KB | NOT CACHED   | PARQUET | true
+| Electronics | 1812  | 1      | 232.67KB | NOT CACHED   | PARQUET | true
+| Home        | 1807  | 1      | 232.56KB | NOT CACHED   | PARQUET | true
+| Jewelry     | 1740  | 1      | 223.72KB | NOT CACHED   | PARQUET | true
+| Men         | 1811  | 1      | 231.25KB | NOT CACHED   | PARQUET | true
+| Music       | 1860  | 1      | 237.90KB | NOT CACHED   | PARQUET | true
+| Shoes       | 1835  | 1      | 234.90KB | NOT CACHED   | PARQUET | true
+| Sports      | 1783  | 1      | 227.97KB | NOT CACHED   | PARQUET | true
+| Women       | 1790  | 1      | 226.27KB | NOT CACHED   | PARQUET | true
+| Total       | 17957 | 11     | 2.65MB   | 0B           |         |
++-------------+-------+--------+----------+--------------+---------+------------------
+</code></pre>
+
+    </div>
+  </article>
+
 </article></main></body></html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_perf_joins.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_perf_joins.html b/docs/build/html/topics/impala_perf_joins.html
index 064a8c5..cb9713a 100644
--- a/docs/build/html/topics/impala_perf_joins.html
+++ b/docs/build/html/topics/impala_perf_joins.html
@@ -30,8 +30,9 @@
     <p class="p">
       If statistics are not available for all the tables in the join query, or if Impala chooses a join order that
       is not the most efficient, you can override the automatic join order optimization by specifying the
-      <code class="ph codeph">STRAIGHT_JOIN</code> keyword immediately after the <code class="ph codeph">SELECT</code> keyword. In this case,
-      Impala uses the order the tables appear in the query to guide how the joins are processed.
+      <code class="ph codeph">STRAIGHT_JOIN</code> keyword immediately after the <code class="ph codeph">SELECT</code> and any <code class="ph codeph">DISTINCT</code>
+      or <code class="ph codeph">ALL</code> keywords. In this case, Impala uses the order the tables appear in the query to guide how the
+      joins are processed.
     </p>
 
     <p class="p">
@@ -118,12 +119,22 @@
       <p class="p">
         If an Impala join query is inefficient because of outdated statistics or unexpected data distribution, you
         can keep Impala from reordering the joined tables by using the <code class="ph codeph">STRAIGHT_JOIN</code> keyword
-        immediately after the <code class="ph codeph">SELECT</code> keyword. The <code class="ph codeph">STRAIGHT_JOIN</code> keyword turns off
+        immediately after the <code class="ph codeph">SELECT</code> and any <code class="ph codeph">DISTINCT</code> or <code class="ph codeph">ALL</code>
+        keywords. The <code class="ph codeph">STRAIGHT_JOIN</code> keyword turns off
         the reordering of join clauses that Impala does internally, and produces a plan that relies on the join
         clauses being ordered optimally in the query text. In this case, rewrite the query so that the largest
         table is on the left, followed by the next largest, and so on until the smallest table is on the right.
       </p>
 
+      <div class="note note note_note"><span class="note__title notetitle">Note:</span> 
+        <p class="p">
+        The <code class="ph codeph">STRAIGHT_JOIN</code> hint affects the join order of table references in the query
+        block containing the hint. It does not affect the join order of nested queries, such as views,
+        inline views, or <code class="ph codeph">WHERE</code>-clause subqueries. To use this hint for performance
+        tuning of complex queries, apply the hint to all query blocks that need a fixed join order.
+      </p>
+      </div>
+
       <p class="p">
         In this example, the subselect from the <code class="ph codeph">BIG</code> table produces a very small result set, but
         the table might still be treated as if it were the biggest and placed first in the join order. Using
@@ -132,6 +143,10 @@
       </p>
 
 <pre class="pre codeblock"><code>select straight_join x from medium join small join (select * from big where c1 &lt; 10) as big
+  where medium.id = small.id and small.id = big.id;
+
+-- If the query contains [DISTINCT | ALL], the hint goes after those keywords.
+select distinct straight_join x from medium join small join (select * from big where c1 &lt; 10) as big
   where medium.id = small.id and small.id = big.id;</code></pre>
     </div>
   </article>

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_perf_stats.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_perf_stats.html b/docs/build/html/topics/impala_perf_stats.html
index 7ad1fb0..4d7d17e 100644
--- a/docs/build/html/topics/impala_perf_stats.html
+++ b/docs/build/html/topics/impala_perf_stats.html
@@ -300,15 +300,6 @@ show column stats year_month_day;
 +-----------+---------+------------------+--------+----------+-------------------+
 </code></pre>
 
-      <div class="note note note_note"><span class="note__title notetitle">Note:</span> 
-        Partitioned tables can grow so large that scanning the entire table, as the <code class="ph codeph">COMPUTE STATS</code>
-        statement does, is impractical just to update the statistics for a new partition. The standard
-        <code class="ph codeph">COMPUTE STATS</code> statement might take hours, or even days. That situation is where you switch
-        to using incremental statistics, a feature available in <span class="keyword">Impala 2.1</span> and higher.
-        See <a class="xref" href="impala_perf_stats.html#perf_stats_incremental">Overview of Incremental Statistics</a> for details about this feature
-        and the <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> syntax.
-      </div>
-
       <p class="p">
         If you run the Hive statement <code class="ph codeph">ANALYZE TABLE COMPUTE STATISTICS FOR COLUMNS</code>,
         Impala can only use the resulting column statistics if the table is unpartitioned.
@@ -337,6 +328,31 @@ show column stats year_month_day;
         entire table each time.
       </p>
 
+      <div class="note important note_important"><span class="note__title importanttitle">Important:</span> 
+        <p class="p">
+        For a particular table, use either <code class="ph codeph">COMPUTE STATS</code> or
+        <code class="ph codeph">COMPUTE INCREMENTAL STATS</code>, but never combine the two or alternate
+        between them. If you switch from <code class="ph codeph">COMPUTE STATS</code> to
+        <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> during the lifetime of a table, or vice
+        versa, drop all statistics (by running both <code class="ph codeph">DROP STATS</code> and
+        <code class="ph codeph">DROP INCREMENTAL STATS</code>) before making the switch.
+      </p>
+        <p class="p">
+        When you run <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> on a table for the first time,
+        the statistics are computed again from scratch regardless of whether the table already
+        has statistics. Therefore, expect a one-time resource-intensive operation
+        for scanning the entire table when running <code class="ph codeph">COMPUTE INCREMENTAL STATS</code>
+        for the first time on a given table.
+      </p>
+        <p class="p">
+        For a table with a huge number of partitions and many columns, the approximately 400 bytes
+        of metadata per column per partition can add up to significant memory overhead, as it must
+        be cached on the <span class="keyword cmdname">catalogd</span> host and on every <span class="keyword cmdname">impalad</span> host
+        that is eligible to be a coordinator. If this metadata for all tables combined exceeds 2 GB,
+        you might experience service downtime.
+      </p>
+      </div>
+
       <p class="p">
         You can also compute or drop statistics for a single partition by including a <code class="ph codeph">PARTITION</code>
         clause in the <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> or <code class="ph codeph">DROP INCREMENTAL STATS</code>
@@ -350,9 +366,9 @@ show column stats year_month_day;
       <ul class="ul">
         <li class="li">
           <p class="p">
-            If you have an existing partitioned table for which you have already computed statistics, issuing
-            <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> without a partition clause causes Impala to rescan the
-            entire table. Once the incremental statistics are computed, any future <code class="ph codeph">COMPUTE INCREMENTAL
+            If you have a partitioned table for which you have already run a regular <code class="ph codeph">COMPUTE STATS</code>
+            statement, issuing <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> without a partition clause causes Impala
+            to rescan the entire table. Once the incremental statistics are computed, any future <code class="ph codeph">COMPUTE INCREMENTAL
             STATS</code> statements only scan any new partitions and any partitions where you performed
             <code class="ph codeph">DROP INCREMENTAL STATS</code>.
           </p>

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_query_options.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_query_options.html b/docs/build/html/topics/impala_query_options.html
index 2fbda3f..2d52cff 100644
--- a/docs/build/html/topics/impala_query_options.html
+++ b/docs/build/html/topics/impala_query_options.html
@@ -1,6 +1,6 @@
 <!DOCTYPE html
   SYSTEM "about:legacy-compat">
-<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_set.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_abort_on_default_limit_exceeded.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_abort_on_error.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_allow_unsupported_formats.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_appx_count_distinct.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_batch_size.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_compression_codec.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_debug_action.html"><meta name="DC.Relation" scheme="URI" 
 content="../topics/impala_default_join_distribution_mode.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_default_order_by_limit.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_disable_codegen.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_decimal_v2.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_disable_row_runtime_filtering.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_disable_streaming_preaggregations.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_disable_unsafe_spills.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_exec_single_node_rows_threshold.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_explain_level.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_hbase_cache_blocks.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_hbase_caching.html"><meta name="DC.Rela
 tion" scheme="URI" content="../topics/impala_live_progress.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_live_summary.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_max_errors.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_max_io_buffers.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_max_scan_range_length.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_max_num_runtime_filters.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_mem_limit.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_mt_dop.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_num_nodes.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_num_scanner_threads.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_optimize_partition_key_scans.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_parquet
 _compression_codec.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_parquet_annotate_strings_utf8.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_parquet_fallback_schema_resolution.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_parquet_file_size.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_prefetch_mode.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_query_timeout_s.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_request_pool.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_replica_preference.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_reservation_request_timeout.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_runtime_bloom_filter_size.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_runtime_filter_max_size.html"><meta name="DC.Relation" scheme="URI" content="..
 /topics/impala_runtime_filter_min_size.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_runtime_filter_mode.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_runtime_filter_wait_time_ms.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_s3_skip_insert_staging.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_scan_node_codegen_threshold.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_scratch_limit.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_schedule_random_replica.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_support_start_over.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_sync_ddl.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_v_cpu_cores.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" co
 ntent="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="query_options"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>Query Options for the SET Statement</title></head><body id="query_options"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
+<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2017"><meta name="DC.rights.owner" content="(C) Copyright 2017"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_set.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_abort_on_default_limit_exceeded.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_abort_on_error.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_allow_unsupported_formats.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_appx_count_distinct.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_batch_size.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_buffer_pool_limit.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_compression_codec.html"><meta name="DC.Relation" scheme="
 URI" content="../topics/impala_debug_action.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_decimal_v2.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_default_join_distribution_mode.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_default_order_by_limit.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_default_spillable_buffer_size.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_disable_codegen.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_disable_row_runtime_filtering.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_disable_streaming_preaggregations.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_disable_unsafe_spills.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_exec_single_node_rows_threshold.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_explain_level.html"><met
 a name="DC.Relation" scheme="URI" content="../topics/impala_hbase_cache_blocks.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_hbase_caching.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_live_progress.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_live_summary.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_max_errors.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_max_io_buffers.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_max_row_size.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_max_num_runtime_filters.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_max_scan_range_length.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_mem_limit.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_min_spillable_buffer_size.html"><meta name="DC.Relation" scheme="URI" content="../
 topics/impala_mt_dop.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_num_nodes.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_num_scanner_threads.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_optimize_partition_key_scans.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_parquet_compression_codec.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_parquet_annotate_strings_utf8.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_parquet_fallback_schema_resolution.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_parquet_file_size.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_prefetch_mode.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_query_timeout_s.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_request_pool.html"><meta name="DC.Relation" scheme="URI" content="../topics/im
 pala_replica_preference.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_reservation_request_timeout.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_runtime_bloom_filter_size.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_runtime_filter_max_size.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_runtime_filter_min_size.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_runtime_filter_mode.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_runtime_filter_wait_time_ms.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_s3_skip_insert_staging.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_scan_node_codegen_threshold.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_schedule_random_replica.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_scratch_limit.html"><meta name="DC.Relation" sch
 eme="URI" content="../topics/impala_support_start_over.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_sync_ddl.html"><meta name="DC.Relation" scheme="URI" content="../topics/impala_v_cpu_cores.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.8.x"><meta name="version" content="Impala 2.8.x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="query_options"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>Query Options for the SET Statement</title></head><body id="query_options"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
 
   <h1 class="title topictitle1" id="ariaid-title1">Query Options for the SET Statement</h1>
   
@@ -46,4 +46,4 @@
       <a class="xref" href="impala_set.html#set">SET Statement</a>
     </p>
   </div>
-<nav role="navigation" class="related-links"><ul class="ullinks"><li class="link ulchildlink"><strong><a href="../topics/impala_abort_on_default_limit_exceeded.html">ABORT_ON_DEFAULT_LIMIT_EXCEEDED Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_abort_on_error.html">ABORT_ON_ERROR Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_allow_unsupported_formats.html">ALLOW_UNSUPPORTED_FORMATS Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_appx_count_distinct.html">APPX_COUNT_DISTINCT Query Option (Impala 2.0 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_batch_size.html">BATCH_SIZE Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_compression_codec.html">COMPRESSION_CODEC Query Option (Impala 2.0 or higher only)</a></strong><br></li><li class="lin
 k ulchildlink"><strong><a href="../topics/impala_debug_action.html">DEBUG_ACTION Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_default_join_distribution_mode.html">DEFAULT_JOIN_DISTRIBUTION_MODE Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_default_order_by_limit.html">DEFAULT_ORDER_BY_LIMIT Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_disable_codegen.html">DISABLE_CODEGEN Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_decimal_v2.html">DECIMAL_V2 Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_disable_row_runtime_filtering.html">DISABLE_ROW_RUNTIME_FILTERING Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_disable_streaming_preaggregations.html">DISABLE_STREAM
 ING_PREAGGREGATIONS Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_disable_unsafe_spills.html">DISABLE_UNSAFE_SPILLS Query Option (Impala 2.0 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_exec_single_node_rows_threshold.html">EXEC_SINGLE_NODE_ROWS_THRESHOLD Query Option (Impala 2.1 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_explain_level.html">EXPLAIN_LEVEL Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_hbase_cache_blocks.html">HBASE_CACHE_BLOCKS Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_hbase_caching.html">HBASE_CACHING Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_live_progress.html">LIVE_PROGRESS Query Option (Impala 2.3 or higher only)</a><
 /strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_live_summary.html">LIVE_SUMMARY Query Option (Impala 2.3 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_max_errors.html">MAX_ERRORS Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_max_io_buffers.html">MAX_IO_BUFFERS Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_max_scan_range_length.html">MAX_SCAN_RANGE_LENGTH Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_max_num_runtime_filters.html">MAX_NUM_RUNTIME_FILTERS Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_mem_limit.html">MEM_LIMIT Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_mt_dop.html">MT_DOP Query Option</a></strong><br></li
 ><li class="link ulchildlink"><strong><a href="../topics/impala_num_nodes.html">NUM_NODES Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_num_scanner_threads.html">NUM_SCANNER_THREADS Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_optimize_partition_key_scans.html">OPTIMIZE_PARTITION_KEY_SCANS Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_parquet_compression_codec.html">PARQUET_COMPRESSION_CODEC Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_parquet_annotate_strings_utf8.html">PARQUET_ANNOTATE_STRINGS_UTF8 Query Option (Impala 2.6 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_parquet_fallback_schema_resolution.html">PARQUET_FALLBACK_SCHEMA_RESOLUTION Query Option (Impala 2.6 or higher only)</a></strong><br
 ></li><li class="link ulchildlink"><strong><a href="../topics/impala_parquet_file_size.html">PARQUET_FILE_SIZE Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_prefetch_mode.html">PREFETCH_MODE Query Option (Impala 2.6 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_query_timeout_s.html">QUERY_TIMEOUT_S Query Option (Impala 2.0 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_request_pool.html">REQUEST_POOL Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_replica_preference.html">REPLICA_PREFERENCE Query Option (Impala 2.7 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_reservation_request_timeout.html">RESERVATION_REQUEST_TIMEOUT Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_runtime_bl
 oom_filter_size.html">RUNTIME_BLOOM_FILTER_SIZE Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_runtime_filter_max_size.html">RUNTIME_FILTER_MAX_SIZE Query Option (Impala 2.6 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_runtime_filter_min_size.html">RUNTIME_FILTER_MIN_SIZE Query Option (Impala 2.6 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_runtime_filter_mode.html">RUNTIME_FILTER_MODE Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_runtime_filter_wait_time_ms.html">RUNTIME_FILTER_WAIT_TIME_MS Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_s3_skip_insert_staging.html">S3_SKIP_INSERT_STAGING Query Option (Impala 2.6 or higher only)</a></strong><br
 ></li><li class="link ulchildlink"><strong><a href="../topics/impala_scan_node_codegen_threshold.html">SCAN_NODE_CODEGEN_THRESHOLD Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_scratch_limit.html">SCRATCH_LIMIT Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_schedule_random_replica.html">SCHEDULE_RANDOM_REPLICA Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_support_start_over.html">SUPPORT_START_OVER Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_sync_ddl.html">SYNC_DDL Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_v_cpu_cores.html">V_CPU_CORES Query Option</a></strong><br></li></ul><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href
 ="../topics/impala_set.html">SET Statement</a></div></div></nav></article></main></body></html>
\ No newline at end of file
+<nav role="navigation" class="related-links"><ul class="ullinks"><li class="link ulchildlink"><strong><a href="../topics/impala_abort_on_default_limit_exceeded.html">ABORT_ON_DEFAULT_LIMIT_EXCEEDED Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_abort_on_error.html">ABORT_ON_ERROR Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_allow_unsupported_formats.html">ALLOW_UNSUPPORTED_FORMATS Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_appx_count_distinct.html">APPX_COUNT_DISTINCT Query Option (Impala 2.0 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_batch_size.html">BATCH_SIZE Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_buffer_pool_limit.html">BUFFER_POOL_LIMIT Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a hr
 ef="../topics/impala_compression_codec.html">COMPRESSION_CODEC Query Option (Impala 2.0 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_debug_action.html">DEBUG_ACTION Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_decimal_v2.html">DECIMAL_V2 Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_default_join_distribution_mode.html">DEFAULT_JOIN_DISTRIBUTION_MODE Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_default_order_by_limit.html">DEFAULT_ORDER_BY_LIMIT Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_default_spillable_buffer_size.html">DEFAULT_SPILLABLE_BUFFER_SIZE Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_disable_codegen.html">DISABLE_CODEGEN Query Option</a></strong><br></li><li cl
 ass="link ulchildlink"><strong><a href="../topics/impala_disable_row_runtime_filtering.html">DISABLE_ROW_RUNTIME_FILTERING Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_disable_streaming_preaggregations.html">DISABLE_STREAMING_PREAGGREGATIONS Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_disable_unsafe_spills.html">DISABLE_UNSAFE_SPILLS Query Option (Impala 2.0 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_exec_single_node_rows_threshold.html">EXEC_SINGLE_NODE_ROWS_THRESHOLD Query Option (Impala 2.1 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_explain_level.html">EXPLAIN_LEVEL Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_hbase_cache_blocks.html">HBASE_CACHE_BLOCKS Query
  Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_hbase_caching.html">HBASE_CACHING Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_live_progress.html">LIVE_PROGRESS Query Option (Impala 2.3 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_live_summary.html">LIVE_SUMMARY Query Option (Impala 2.3 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_max_errors.html">MAX_ERRORS Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_max_io_buffers.html">MAX_IO_BUFFERS Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_max_row_size.html">MAX_ROW_SIZE Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_max_num_runtime_filters.html">MAX_NUM_RUNTIME_FILTERS Query Option (Imp
 ala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_max_scan_range_length.html">MAX_SCAN_RANGE_LENGTH Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_mem_limit.html">MEM_LIMIT Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_min_spillable_buffer_size.html">MIN_SPILLABLE_BUFFER_SIZE Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_mt_dop.html">MT_DOP Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_num_nodes.html">NUM_NODES Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_num_scanner_threads.html">NUM_SCANNER_THREADS Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_optimize_partition_key_scans.html">OPTIMIZE_PARTITION_KEY_SCANS Query Option (Imp
 ala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_parquet_compression_codec.html">PARQUET_COMPRESSION_CODEC Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_parquet_annotate_strings_utf8.html">PARQUET_ANNOTATE_STRINGS_UTF8 Query Option (Impala 2.6 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_parquet_fallback_schema_resolution.html">PARQUET_FALLBACK_SCHEMA_RESOLUTION Query Option (Impala 2.6 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_parquet_file_size.html">PARQUET_FILE_SIZE Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_prefetch_mode.html">PREFETCH_MODE Query Option (Impala 2.6 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_query_timeout_s.html">QUERY_TIMEOUT_S Query 
 Option (Impala 2.0 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_request_pool.html">REQUEST_POOL Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_replica_preference.html">REPLICA_PREFERENCE Query Option (Impala 2.7 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_reservation_request_timeout.html">RESERVATION_REQUEST_TIMEOUT Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_runtime_bloom_filter_size.html">RUNTIME_BLOOM_FILTER_SIZE Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_runtime_filter_max_size.html">RUNTIME_FILTER_MAX_SIZE Query Option (Impala 2.6 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_runtime_filter_min_size.html">RUNTIME_FILTER_MIN_SIZE Query
  Option (Impala 2.6 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_runtime_filter_mode.html">RUNTIME_FILTER_MODE Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_runtime_filter_wait_time_ms.html">RUNTIME_FILTER_WAIT_TIME_MS Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_s3_skip_insert_staging.html">S3_SKIP_INSERT_STAGING Query Option (Impala 2.6 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_scan_node_codegen_threshold.html">SCAN_NODE_CODEGEN_THRESHOLD Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_schedule_random_replica.html">SCHEDULE_RANDOM_REPLICA Query Option (Impala 2.5 or higher only)</a></strong><br></li><li class="link ulchildlink"><strong><a
  href="../topics/impala_scratch_limit.html">SCRATCH_LIMIT Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_support_start_over.html">SUPPORT_START_OVER Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_sync_ddl.html">SYNC_DDL Query Option</a></strong><br></li><li class="link ulchildlink"><strong><a href="../topics/impala_v_cpu_cores.html">V_CPU_CORES Query Option</a></strong><br></li></ul><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_set.html">SET Statement</a></div></div></nav></article></main></body></html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_reserved_words.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_reserved_words.html b/docs/build/html/topics/impala_reserved_words.html
index 2516a6d..dc92593 100644
--- a/docs/build/html/topics/impala_reserved_words.html
+++ b/docs/build/html/topics/impala_reserved_words.html
@@ -193,6 +193,7 @@ string
 symbol
 table
 tables
+<span class="ph">tablesample</span>
 tblproperties
 terminated
 textfile
@@ -333,7 +334,6 @@ shutdown
 some
 statistics
 system_user
-tablesample
 textsize
 then
 top


[5/7] incubator-impala git commit: Update Impala docs for 2.10 release

Posted by jr...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/ca9005be/docs/build/html/topics/impala_fixed_issues.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_fixed_issues.html b/docs/build/html/topics/impala_fixed_issues.html
index 5219de8..3ba3d99 100644
--- a/docs/build/html/topics/impala_fixed_issues.html
+++ b/docs/build/html/topics/impala_fixed_issues.html
@@ -20,9 +20,25 @@
 
 
 
-  <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_release_notes.html">Impala Release Notes</a></div></div></nav><article class="topic concept nested1" aria-labelledby="ariaid-title2" id="fixed_issues__fixed_issues_290">
+  <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_release_notes.html">Impala Release Notes</a></div></div></nav><article class="topic concept nested1" aria-labelledby="ariaid-title2" id="fixed_issues__fixed_issues_2100">
 
-    <h2 class="title topictitle2" id="ariaid-title2">Issues Fixed in <span class="keyword">Impala 2.9.0</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title2">Issues Fixed in <span class="keyword">Impala 2.10.0</span></h2>
+
+    <div class="body conbody">
+
+      <p class="p">
+        For the full list of issues closed in this release, including bug fixes,
+        see the <a class="xref" href="https://impala.incubator.apache.org/docs/changelog-2.10.html" target="_blank">changelog for <span class="keyword">Impala 2.10</span></a>.
+      </p>
+
+    </div>
+  </article>
+
+
+
+  <article class="topic concept nested1" aria-labelledby="ariaid-title3" id="fixed_issues__fixed_issues_290">
+
+    <h2 class="title topictitle2" id="ariaid-title3">Issues Fixed in <span class="keyword">Impala 2.9.0</span></h2>
 
     <div class="body conbody">
 
@@ -36,9 +52,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title3" id="fixed_issues__fixed_issues_280">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title4" id="fixed_issues__fixed_issues_280">
 
-    <h2 class="title topictitle2" id="ariaid-title3">Issues Fixed in <span class="keyword">Impala 2.8.0</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title4">Issues Fixed in <span class="keyword">Impala 2.8.0</span></h2>
 
     <div class="body conbody">
 
@@ -52,9 +68,9 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title4" id="fixed_issues__fixed_issues_270">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title5" id="fixed_issues__fixed_issues_270">
 
-    <h2 class="title topictitle2" id="ariaid-title4">Issues Fixed in <span class="keyword">Impala 2.7.0</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title5">Issues Fixed in <span class="keyword">Impala 2.7.0</span></h2>
 
     <div class="body conbody">
 
@@ -69,23 +85,23 @@
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title5" id="fixed_issues__fixed_issues_263">
-    <h2 class="title topictitle2" id="ariaid-title5">Issues Fixed in <span class="keyword">Impala 2.6.3</span></h2>
+  <article class="topic concept nested1" aria-labelledby="ariaid-title6" id="fixed_issues__fixed_issues_263">
+    <h2 class="title topictitle2" id="ariaid-title6">Issues Fixed in <span class="keyword">Impala 2.6.3</span></h2>
     <div class="body conbody">
       <p class="p"></p>
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title6" id="fixed_issues__fixed_issues_262">
-    <h2 class="title topictitle2" id="ariaid-title6">Issues Fixed in <span class="keyword">Impala 2.6.2</span></h2>
+  <article class="topic concept nested1" aria-labelledby="ariaid-title7" id="fixed_issues__fixed_issues_262">
+    <h2 class="title topictitle2" id="ariaid-title7">Issues Fixed in <span class="keyword">Impala 2.6.2</span></h2>
     <div class="body conbody">
       <p class="p"></p>
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title7" id="fixed_issues__fixed_issues_260">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title8" id="fixed_issues__fixed_issues_260">
 
-    <h2 class="title topictitle2" id="ariaid-title7">Issues Fixed in <span class="keyword">Impala 2.6.0</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title8">Issues Fixed in <span class="keyword">Impala 2.6.0</span></h2>
 
     <div class="body conbody">
 
@@ -98,8 +114,8 @@
 
     </div>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title8" id="fixed_issues_260__IMPALA-3385">
-      <h3 class="title topictitle3" id="ariaid-title8">RuntimeState::error_log_ crashes</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title9" id="fixed_issues_260__IMPALA-3385">
+      <h3 class="title topictitle3" id="ariaid-title9">RuntimeState::error_log_ crashes</h3>
       <div class="body conbody">
       <p class="p">
         A crash could occur, with stack trace pointing to <code class="ph codeph">impala::RuntimeState::ErrorLog</code>.
@@ -109,8 +125,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title9" id="fixed_issues_260__IMPALA-3378">
-      <h3 class="title topictitle3" id="ariaid-title9">HiveUdfCall::Open() produces unsynchronized access to JniUtil::global_refs_ vector</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title10" id="fixed_issues_260__IMPALA-3378">
+      <h3 class="title topictitle3" id="ariaid-title10">HiveUdfCall::Open() produces unsynchronized access to JniUtil::global_refs_ vector</h3>
       <div class="body conbody">
       <p class="p">
         A crash could occur because of contention between multiple calls to Java UDFs.
@@ -120,8 +136,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title10" id="fixed_issues_260__IMPALA-3379">
-      <h3 class="title topictitle3" id="ariaid-title10">HBaseTableWriter::CreatePutList() produces unsynchronized access to JniUtil::global_refs_ vector</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title11" id="fixed_issues_260__IMPALA-3379">
+      <h3 class="title topictitle3" id="ariaid-title11">HBaseTableWriter::CreatePutList() produces unsynchronized access to JniUtil::global_refs_ vector</h3>
       <div class="body conbody">
       <p class="p">
         A crash could occur because of contention between multiple concurrent statements writing to HBase.
@@ -131,8 +147,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title11" id="fixed_issues_260__IMPALA-3317">
-      <h3 class="title topictitle3" id="ariaid-title11">Stress test failure: sorter.cc:745] Check failed: i == 0 (1 vs. 0) </h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title12" id="fixed_issues_260__IMPALA-3317">
+      <h3 class="title topictitle3" id="ariaid-title12">Stress test failure: sorter.cc:745] Check failed: i == 0 (1 vs. 0) </h3>
       <div class="body conbody">
       <p class="p">
         A crash or wrong results could occur if the spill-to-disk mechanism encountered a zero-length string at
@@ -143,8 +159,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title12" id="fixed_issues_260__IMPALA-3311">
-      <h3 class="title topictitle3" id="ariaid-title12">String data coming out of agg can be corrupted by blocking operators</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title13" id="fixed_issues_260__IMPALA-3311">
+      <h3 class="title topictitle3" id="ariaid-title13">String data coming out of agg can be corrupted by blocking operators</h3>
       <div class="body conbody">
       <p class="p">
         If a query plan contains an aggregation node producing string values anywhere within a subplan
@@ -156,8 +172,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title13" id="fixed_issues_260__IMPALA-3269">
-      <h3 class="title topictitle3" id="ariaid-title13">CTAS with subquery throws AuthzException</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title14" id="fixed_issues_260__IMPALA-3269">
+      <h3 class="title topictitle3" id="ariaid-title14">CTAS with subquery throws AuthzException</h3>
       <div class="body conbody">
       <p class="p">
         A <code class="ph codeph">CREATE TABLE AS SELECT</code> operation could fail with an authorization error,
@@ -168,8 +184,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title14" id="fixed_issues_260__IMPALA-3237">
-      <h3 class="title topictitle3" id="ariaid-title14">Crash on inserting into table with binary and parquet</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title15" id="fixed_issues_260__IMPALA-3237">
+      <h3 class="title topictitle3" id="ariaid-title15">Crash on inserting into table with binary and parquet</h3>
       <div class="body conbody">
       <p class="p">
         Impala incorrectly allowed <code class="ph codeph">BINARY</code> to be specified as a column type,
@@ -180,8 +196,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title15" id="fixed_issues_260__IMPALA-3105">
-      <h3 class="title topictitle3" id="ariaid-title15">RowBatch::MaxTupleBufferSize() calculation incorrect, may lead to memory corruption</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title16" id="fixed_issues_260__IMPALA-3105">
+      <h3 class="title topictitle3" id="ariaid-title16">RowBatch::MaxTupleBufferSize() calculation incorrect, may lead to memory corruption</h3>
       <div class="body conbody">
       <p class="p">
         A crash could occur while querying tables with very large rows, for example wide tables with many
@@ -193,8 +209,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title16" id="fixed_issues_260__IMPALA-3494">
-      <h3 class="title topictitle3" id="ariaid-title16">Thrift buffer overflows when serialize more than 3355443200 bytes in impala</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title17" id="fixed_issues_260__IMPALA-3494">
+      <h3 class="title topictitle3" id="ariaid-title17">Thrift buffer overflows when serialize more than 3355443200 bytes in impala</h3>
       <div class="body conbody">
       <p class="p">
         A very large memory allocation within the <span class="keyword cmdname">catalogd</span> daemon could exceed an internal Thrift limit,
@@ -205,8 +221,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title17" id="fixed_issues_260__IMPALA-3314">
-      <h3 class="title topictitle3" id="ariaid-title17">Altering table partition's storage format is not working and crashing the daemon</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title18" id="fixed_issues_260__IMPALA-3314">
+      <h3 class="title topictitle3" id="ariaid-title18">Altering table partition's storage format is not working and crashing the daemon</h3>
       <div class="body conbody">
       <p class="p">
         If a partitioned table used a file format other than Avro, and the file format of an individual partition
@@ -217,8 +233,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title18" id="fixed_issues_260__IMPALA-3798">
-      <h3 class="title topictitle3" id="ariaid-title18">Race condition may cause scanners to spin with runtime filters on Avro or Sequence files</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title19" id="fixed_issues_260__IMPALA-3798">
+      <h3 class="title topictitle3" id="ariaid-title19">Race condition may cause scanners to spin with runtime filters on Avro or Sequence files</h3>
       <div class="body conbody">
       <p class="p">
         A timing problem during runtime filter processing could cause queries against Avro or SequenceFile tables
@@ -232,23 +248,23 @@
   </article>
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title19" id="fixed_issues__fixed_issues_254">
-    <h2 class="title topictitle2" id="ariaid-title19">Issues Fixed in <span class="keyword">Impala 2.5.4</span></h2>
+  <article class="topic concept nested1" aria-labelledby="ariaid-title20" id="fixed_issues__fixed_issues_254">
+    <h2 class="title topictitle2" id="ariaid-title20">Issues Fixed in <span class="keyword">Impala 2.5.4</span></h2>
     <div class="body conbody">
       <p class="p"></p>
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title20" id="fixed_issues__fixed_issues_252">
-    <h2 class="title topictitle2" id="ariaid-title20">Issues Fixed in <span class="keyword">Impala 2.5.2</span></h2>
+  <article class="topic concept nested1" aria-labelledby="ariaid-title21" id="fixed_issues__fixed_issues_252">
+    <h2 class="title topictitle2" id="ariaid-title21">Issues Fixed in <span class="keyword">Impala 2.5.2</span></h2>
     <div class="body conbody">
       <p class="p"></p>
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title21" id="fixed_issues__fixed_issues_251">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title22" id="fixed_issues__fixed_issues_251">
 
-    <h2 class="title topictitle2" id="ariaid-title21">Issues Fixed in <span class="keyword">Impala 2.5.1</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title22">Issues Fixed in <span class="keyword">Impala 2.5.1</span></h2>
 
     <div class="body conbody">
       <p class="p"></p>
@@ -256,9 +272,9 @@
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title22" id="fixed_issues__fixed_issues_250">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title23" id="fixed_issues__fixed_issues_250">
 
-    <h2 class="title topictitle2" id="ariaid-title22">Issues Fixed in <span class="keyword">Impala 2.5.0</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title23">Issues Fixed in <span class="keyword">Impala 2.5.0</span></h2>
 
     <div class="body conbody">
 
@@ -270,16 +286,16 @@
 
     </div>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title23" id="fixed_issues_250__IMPALA-2683">
-      <h3 class="title topictitle3" id="ariaid-title23">Stress test hit assert in LLVM: external function could not be resolved</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title24" id="fixed_issues_250__IMPALA-2683">
+      <h3 class="title topictitle3" id="ariaid-title24">Stress test hit assert in LLVM: external function could not be resolved</h3>
       <div class="body conbody">
 <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2683" target="_blank">IMPALA-2683</a></p>
 <p class="p">The stress test was running a build with the TPC-H, TPC-DS, and TPC-H nested queries with scale factor 3.</p>
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title24" id="fixed_issues_250__IMPALA-2365">
-      <h3 class="title topictitle3" id="ariaid-title24">Impalad is crashing if udf jar is not available in hdfs location for first time</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title25" id="fixed_issues_250__IMPALA-2365">
+      <h3 class="title topictitle3" id="ariaid-title25">Impalad is crashing if udf jar is not available in hdfs location for first time</h3>
       <div class="body conbody">
         <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2365" target="_blank">IMPALA-2365</a></p>
         <p class="p">
@@ -289,8 +305,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title25" id="fixed_issues_250__IMPALA-2535-570">
-      <h3 class="title topictitle3" id="ariaid-title25">PAGG hits mem_limit when switching to I/O buffers</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title26" id="fixed_issues_250__IMPALA-2535-570">
+      <h3 class="title topictitle3" id="ariaid-title26">PAGG hits mem_limit when switching to I/O buffers</h3>
       <div class="body conbody">
       <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2535" target="_blank">IMPALA-2535</a></p>
       <p class="p">
@@ -303,8 +319,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title26" id="fixed_issues_250__IMPALA-2643-570">
-      <h3 class="title topictitle3" id="ariaid-title26">Prevent migrating incorrectly inferred identity predicates into inline views</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title27" id="fixed_issues_250__IMPALA-2643-570">
+      <h3 class="title topictitle3" id="ariaid-title27">Prevent migrating incorrectly inferred identity predicates into inline views</h3>
       <div class="body conbody">
       <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2643" target="_blank">IMPALA-2643</a></p>
       <p class="p">
@@ -316,8 +332,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title27" id="fixed_issues_250__IMPALA-1459-570">
-      <h3 class="title topictitle3" id="ariaid-title27">Fix migration/assignment of On-clause predicates inside inline views</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title28" id="fixed_issues_250__IMPALA-1459-570">
+      <h3 class="title topictitle3" id="ariaid-title28">Fix migration/assignment of On-clause predicates inside inline views</h3>
       <div class="body conbody">
       <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1459" target="_blank">IMPALA-1459</a></p>
       <p class="p">
@@ -340,8 +356,8 @@
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title28" id="fixed_issues_250__IMPALA-2093">
-      <h3 class="title topictitle3" id="ariaid-title28">Wrong plan of NOT IN aggregate subquery when a constant is used in subquery predicate</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title29" id="fixed_issues_250__IMPALA-2093">
+      <h3 class="title topictitle3" id="ariaid-title29">Wrong plan of NOT IN aggregate subquery when a constant is used in subquery predicate</h3>
       <div class="body conbody">
         <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2093" target="_blank">IMPALA-2093</a></p>
         <p class="p">
@@ -355,8 +371,8 @@ select * from alltypestiny t1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title29" id="fixed_issues_250__IMPALA-2940">
-      <h3 class="title topictitle3" id="ariaid-title29">Parquet DictDecoders accumulate throughout query</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title30" id="fixed_issues_250__IMPALA-2940">
+      <h3 class="title topictitle3" id="ariaid-title30">Parquet DictDecoders accumulate throughout query</h3>
       <div class="body conbody">
         <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2940" target="_blank">IMPALA-2940</a></p>
         <p class="p">
@@ -365,16 +381,16 @@ select * from alltypestiny t1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title30" id="fixed_issues_250__IMPALA-3056">
-      <h3 class="title topictitle3" id="ariaid-title30">Planner doesn't set the has_local_target field correctly</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title31" id="fixed_issues_250__IMPALA-3056">
+      <h3 class="title topictitle3" id="ariaid-title31">Planner doesn't set the has_local_target field correctly</h3>
       <div class="body conbody">
 <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3056" target="_blank">IMPALA-3056</a></p>
 
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title31" id="fixed_issues_250__IMPALA-2742">
-      <h3 class="title topictitle3" id="ariaid-title31">MemPool allocation growth behavior</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title32" id="fixed_issues_250__IMPALA-2742">
+      <h3 class="title topictitle3" id="ariaid-title32">MemPool allocation growth behavior</h3>
       <div class="body conbody">
         <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2742" target="_blank">IMPALA-2742</a></p>
         <p class="p">
@@ -386,8 +402,8 @@ select * from alltypestiny t1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title32" id="fixed_issues_250__IMPALA-3035">
-      <h3 class="title topictitle3" id="ariaid-title32">Drop partition operations don't follow the catalog's locking protocol</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title33" id="fixed_issues_250__IMPALA-3035">
+      <h3 class="title topictitle3" id="ariaid-title33">Drop partition operations don't follow the catalog's locking protocol</h3>
       <div class="body conbody">
         <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3035" target="_blank">IMPALA-3035</a></p>
         <p class="p">
@@ -399,8 +415,8 @@ select * from alltypestiny t1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title33" id="fixed_issues_250__IMPALA-2215">
-      <h3 class="title topictitle3" id="ariaid-title33">HAVING clause without aggregation not applied properly</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title34" id="fixed_issues_250__IMPALA-2215">
+      <h3 class="title topictitle3" id="ariaid-title34">HAVING clause without aggregation not applied properly</h3>
       <div class="body conbody">
         <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2215" target="_blank">IMPALA-2215</a></p>
         <p class="p">
@@ -414,8 +430,8 @@ select case when 1=1 then 'didit' end as c1 from (select 1 as one) a having 1!=1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title34" id="fixed_issues_250__IMPALA-2914">
-      <h3 class="title topictitle3" id="ariaid-title34">Hit DCHECK Check failed: HasDateOrTime()</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title35" id="fixed_issues_250__IMPALA-2914">
+      <h3 class="title topictitle3" id="ariaid-title35">Hit DCHECK Check failed: HasDateOrTime()</h3>
       <div class="body conbody">
         <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2914" target="_blank">IMPALA-2914</a></p>
         <p class="p">
@@ -425,8 +441,8 @@ select case when 1=1 then 'didit' end as c1 from (select 1 as one) a having 1!=1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title35" id="fixed_issues_250__IMPALA-2986">
-      <h3 class="title topictitle3" id="ariaid-title35">Aggregation spill loop gives up too early leading to mem limit exceeded errors</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title36" id="fixed_issues_250__IMPALA-2986">
+      <h3 class="title topictitle3" id="ariaid-title36">Aggregation spill loop gives up too early leading to mem limit exceeded errors</h3>
       <div class="body conbody">
         <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2986" target="_blank">IMPALA-2986</a></p>
         <p class="p">
@@ -435,8 +451,8 @@ select case when 1=1 then 'didit' end as c1 from (select 1 as one) a having 1!=1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title36" id="fixed_issues_250__IMPALA-2592">
-      <h3 class="title topictitle3" id="ariaid-title36">DataStreamSender::Channel::CloseInternal() does not close the channel on an error.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title37" id="fixed_issues_250__IMPALA-2592">
+      <h3 class="title topictitle3" id="ariaid-title37">DataStreamSender::Channel::CloseInternal() does not close the channel on an error.</h3>
       <div class="body conbody">
         <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2592" target="_blank">IMPALA-2592</a></p>
         <p class="p">
@@ -448,8 +464,8 @@ select case when 1=1 then 'didit' end as c1 from (select 1 as one) a having 1!=1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title37" id="fixed_issues_250__IMPALA-2184">
-      <h3 class="title topictitle3" id="ariaid-title37">Codegen does not catch exceptions in FROM_UNIXTIME()</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title38" id="fixed_issues_250__IMPALA-2184">
+      <h3 class="title topictitle3" id="ariaid-title38">Codegen does not catch exceptions in FROM_UNIXTIME()</h3>
       <div class="body conbody">
         <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2184" target="_blank">IMPALA-2184</a></p>
         <p class="p">
@@ -464,8 +480,8 @@ SET disable_codegen=true;
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title38" id="fixed_issues_250__IMPALA-2788">
-      <h3 class="title topictitle3" id="ariaid-title38">Impala returns wrong result for function 'conv(bigint, from_base, to_base)'</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title39" id="fixed_issues_250__IMPALA-2788">
+      <h3 class="title topictitle3" id="ariaid-title39">Impala returns wrong result for function 'conv(bigint, from_base, to_base)'</h3>
       <div class="body conbody">
         <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2788" target="_blank">IMPALA-2788</a></p>
         <p class="p">
@@ -520,9 +536,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title39" id="fixed_issues__fixed_issues_241">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title40" id="fixed_issues__fixed_issues_241">
 
-    <h2 class="title topictitle2" id="ariaid-title39">Issues Fixed in <span class="keyword">Impala 2.4.1</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title40">Issues Fixed in <span class="keyword">Impala 2.4.1</span></h2>
 
     <div class="body conbody">
       <p class="p">
@@ -531,9 +547,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title40" id="fixed_issues__fixed_issues_240">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title41" id="fixed_issues__fixed_issues_240">
 
-    <h2 class="title topictitle2" id="ariaid-title40">Issues Fixed in <span class="keyword">Impala 2.4.0</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title41">Issues Fixed in <span class="keyword">Impala 2.4.0</span></h2>
 
     <div class="body conbody">
 
@@ -549,9 +565,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title41" id="fixed_issues__fixed_issues_234">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title42" id="fixed_issues__fixed_issues_234">
 
-    <h2 class="title topictitle2" id="ariaid-title41">Issues Fixed in <span class="keyword">Impala 2.3.4</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title42">Issues Fixed in <span class="keyword">Impala 2.3.4</span></h2>
 
     <div class="body conbody">
       <p class="p"></p>
@@ -559,9 +575,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title42" id="fixed_issues__fixed_issues_232">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title43" id="fixed_issues__fixed_issues_232">
 
-    <h2 class="title topictitle2" id="ariaid-title42">Issues Fixed in <span class="keyword">Impala 2.3.2</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title43">Issues Fixed in <span class="keyword">Impala 2.3.2</span></h2>
 
     <div class="body conbody">
 
@@ -572,8 +588,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
     </div>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title43" id="fixed_issues_232__IMPALA-2829">
-      <h3 class="title topictitle3" id="ariaid-title43">SEGV in AnalyticEvalNode touching NULL input_stream_</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title44" id="fixed_issues_232__IMPALA-2829">
+      <h3 class="title topictitle3" id="ariaid-title44">SEGV in AnalyticEvalNode touching NULL input_stream_</h3>
       <div class="body conbody">
       <p class="p">
         A query involving an analytic function could encounter a serious error.
@@ -584,8 +600,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title44" id="fixed_issues_232__IMPALA-2722">
-      <h3 class="title topictitle3" id="ariaid-title44">Free local allocations per row batch in non-partitioned AGG and HJ</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title45" id="fixed_issues_232__IMPALA-2722">
+      <h3 class="title topictitle3" id="ariaid-title45">Free local allocations per row batch in non-partitioned AGG and HJ</h3>
       <div class="body conbody">
       <p class="p">
         An outer join query could fail unexpectedly with an out-of-memory error
@@ -595,9 +611,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title45" id="fixed_issues_232__IMPALA-2612">
+    <article class="topic concept nested2" aria-labelledby="ariaid-title46" id="fixed_issues_232__IMPALA-2612">
       
-      <h3 class="title topictitle3" id="ariaid-title45">Free local allocations once for every row batch when building hash tables</h3>
+      <h3 class="title topictitle3" id="ariaid-title46">Free local allocations once for every row batch when building hash tables</h3>
       <div class="body conbody">
       <p class="p">
         A join query could encounter a serious error due to an internal failure to allocate memory, which
@@ -607,8 +623,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title46" id="fixed_issues_232__IMPALA-2643">
-      <h3 class="title topictitle3" id="ariaid-title46">Prevent migrating incorrectly inferred identity predicates into inline views</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title47" id="fixed_issues_232__IMPALA-2643">
+      <h3 class="title topictitle3" id="ariaid-title47">Prevent migrating incorrectly inferred identity predicates into inline views</h3>
       <div class="body conbody">
       <p class="p">
         Referring to the same column twice in a view definition could cause the view to omit
@@ -620,8 +636,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title47" id="fixed_issues_232__IMPALA-2695">
-      <h3 class="title topictitle3" id="ariaid-title47">Fix GRANTs on URIs with uppercase letters</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title48" id="fixed_issues_232__IMPALA-2695">
+      <h3 class="title topictitle3" id="ariaid-title48">Fix GRANTs on URIs with uppercase letters</h3>
       <div class="body conbody">
       <p class="p">
         A <code class="ph codeph">GRANT</code> statement for a URI could be ineffective if the URI
@@ -650,8 +666,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title49" id="fixed_issues_232__IMPALA-2226">
-      <h3 class="title topictitle3" id="ariaid-title49">Throw AnalysisError if table properties are too large (for the Hive metastore)</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title50" id="fixed_issues_232__IMPALA-2226">
+      <h3 class="title topictitle3" id="ariaid-title50">Throw AnalysisError if table properties are too large (for the Hive metastore)</h3>
       <div class="body conbody">
       <p class="p">
         <code class="ph codeph">CREATE TABLE</code> or <code class="ph codeph">ALTER TABLE</code> statements could fail with
@@ -663,8 +679,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title50" id="fixed_issues_232__IMPALA-2273-552">
-      <h3 class="title topictitle3" id="ariaid-title50">Make MAX_PAGE_HEADER_SIZE configurable</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title51" id="fixed_issues_232__IMPALA-2273-552">
+      <h3 class="title topictitle3" id="ariaid-title51">Make MAX_PAGE_HEADER_SIZE configurable</h3>
       <div class="body conbody">
       <p class="p">
         Impala could fail to access Parquet data files with page headers larger than 8 MB, which could
@@ -676,8 +692,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title51" id="fixed_issues_232__IMPALA-2473">
-      <h3 class="title topictitle3" id="ariaid-title51">reduce scanner memory usage</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title52" id="fixed_issues_232__IMPALA-2473">
+      <h3 class="title topictitle3" id="ariaid-title52">reduce scanner memory usage</h3>
       <div class="body conbody">
       <p class="p">
         Queries on Parquet tables could consume excessive memory (potentially multiple gigabytes) due to producing
@@ -689,8 +705,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title52" id="fixed_issues_232__IMPALA-2113">
-      <h3 class="title topictitle3" id="ariaid-title52">Handle error when distinct and aggregates are used with a having clause</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title53" id="fixed_issues_232__IMPALA-2113">
+      <h3 class="title topictitle3" id="ariaid-title53">Handle error when distinct and aggregates are used with a having clause</h3>
       <div class="body conbody">
       <p class="p">
         A query that included a <code class="ph codeph">DISTINCT</code> operator and a <code class="ph codeph">HAVING</code> clause, but no
@@ -701,8 +717,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title53" id="fixed_issues_232__IMPALA-2225">
-      <h3 class="title topictitle3" id="ariaid-title53">Handle error when star based select item and aggregate are incorrectly used</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title54" id="fixed_issues_232__IMPALA-2225">
+      <h3 class="title topictitle3" id="ariaid-title54">Handle error when star based select item and aggregate are incorrectly used</h3>
       <div class="body conbody">
       <p class="p">
         A query that included <code class="ph codeph">*</code> in the <code class="ph codeph">SELECT</code> list, in addition to an
@@ -714,8 +730,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title54" id="fixed_issues_232__IMPALA-2731-552">
-      <h3 class="title topictitle3" id="ariaid-title54">Refactor MemPool usage in HBase scan node</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title55" id="fixed_issues_232__IMPALA-2731-552">
+      <h3 class="title topictitle3" id="ariaid-title55">Refactor MemPool usage in HBase scan node</h3>
       <div class="body conbody">
       <p class="p">
         Queries involving HBase tables used substantially more memory than in earlier Impala versions.
@@ -727,8 +743,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title55" id="fixed_issues_232__IMPALA-1459-552">
-      <h3 class="title topictitle3" id="ariaid-title55">Fix migration/assignment of On-clause predicates inside inline views</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title56" id="fixed_issues_232__IMPALA-1459-552">
+      <h3 class="title topictitle3" id="ariaid-title56">Fix migration/assignment of On-clause predicates inside inline views</h3>
       <div class="body conbody">
       <p class="p">
         Some combinations of <code class="ph codeph">ON</code> clauses in join queries could result in comparisons
@@ -751,8 +767,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title56" id="fixed_issues_232__IMPALA-2558">
-      <h3 class="title topictitle3" id="ariaid-title56">DCHECK in parquet scanner after block read error</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title57" id="fixed_issues_232__IMPALA-2558">
+      <h3 class="title topictitle3" id="ariaid-title57">DCHECK in parquet scanner after block read error</h3>
       <div class="body conbody">
       <p class="p">
         A debug build of Impala could encounter a serious error after encountering some kinds of I/O
@@ -762,8 +778,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title57" id="fixed_issues_232__IMPALA-2535">
-      <h3 class="title topictitle3" id="ariaid-title57">PAGG hits mem_limit when switching to I/O buffers</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title58" id="fixed_issues_232__IMPALA-2535">
+      <h3 class="title topictitle3" id="ariaid-title58">PAGG hits mem_limit when switching to I/O buffers</h3>
       <div class="body conbody">
       <p class="p">
         A join query could fail with an out-of-memory error despite the apparent presence of sufficient memory.
@@ -778,8 +794,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
     
     
-    <article class="topic concept nested2" aria-labelledby="ariaid-title58" id="fixed_issues_232__IMPALA-2559">
-      <h3 class="title topictitle3" id="ariaid-title58">Fix check failed: sorter_runs_.back()-&gt;is_pinned_</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title59" id="fixed_issues_232__IMPALA-2559">
+      <h3 class="title topictitle3" id="ariaid-title59">Fix check failed: sorter_runs_.back()-&gt;is_pinned_</h3>
       <div class="body conbody">
       <p class="p">
         A query could fail with an internal error while calculating the memory limit.
@@ -789,8 +805,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title59" id="fixed_issues_232__IMPALA-2614">
-      <h3 class="title topictitle3" id="ariaid-title59">Don't ignore Status returned by DataStreamRecvr::CreateMerger()</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title60" id="fixed_issues_232__IMPALA-2614">
+      <h3 class="title topictitle3" id="ariaid-title60">Don't ignore Status returned by DataStreamRecvr::CreateMerger()</h3>
       <div class="body conbody">
       <p class="p">
         A query could fail with an internal error while calculating the memory limit.
@@ -801,8 +817,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title60" id="fixed_issues_232__IMPALA-2591">
-      <h3 class="title topictitle3" id="ariaid-title60">DataStreamSender::Send() does not return an error status if SendBatch() failed</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title61" id="fixed_issues_232__IMPALA-2591">
+      <h3 class="title topictitle3" id="ariaid-title61">DataStreamSender::Send() does not return an error status if SendBatch() failed</h3>
       <div class="body conbody">
       
       <p class="p">
@@ -811,8 +827,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title61" id="fixed_issues_232__IMPALA-2598">
-      <h3 class="title topictitle3" id="ariaid-title61">Re-enable SSL and Kerberos on server-server</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title62" id="fixed_issues_232__IMPALA-2598">
+      <h3 class="title topictitle3" id="ariaid-title62">Re-enable SSL and Kerberos on server-server</h3>
       <div class="body conbody">
       <p class="p">
         These fixes lift the restriction on using SSL encryption and Kerberos authentication together
@@ -827,9 +843,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title62" id="fixed_issues__fixed_issues_231">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title63" id="fixed_issues__fixed_issues_231">
 
-    <h2 class="title topictitle2" id="ariaid-title62">Issues Fixed in <span class="keyword">Impala 2.3.1</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title63">Issues Fixed in <span class="keyword">Impala 2.3.1</span></h2>
 
     <div class="body conbody">
 
@@ -842,9 +858,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title63" id="fixed_issues__fixed_issues_230">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title64" id="fixed_issues__fixed_issues_230">
 
-    <h2 class="title topictitle2" id="ariaid-title63">Issues Fixed in <span class="keyword">Impala 2.3.0</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title64">Issues Fixed in <span class="keyword">Impala 2.3.0</span></h2>
 
     <div class="body conbody">
       <p class="p"> This section lists the most serious or frequently encountered customer
@@ -858,8 +874,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
     </div>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title64" id="fixed_issues_230__serious_230">
-      <h3 class="title topictitle3" id="ariaid-title64">Fixes for Serious Errors</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title65" id="fixed_issues_230__serious_230">
+      <h3 class="title topictitle3" id="ariaid-title65">Fixes for Serious Errors</h3>
       <div class="body conbody">
       <p class="p">
         A number of issues were resolved that could result in serious errors
@@ -881,8 +897,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title65" id="fixed_issues_230__correctness_230">
-      <h3 class="title topictitle3" id="ariaid-title65">Fixes for Correctness Errors</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title66" id="fixed_issues_230__correctness_230">
+      <h3 class="title topictitle3" id="ariaid-title66">Fixes for Correctness Errors</h3>
       <div class="body conbody">
       <p class="p">
         A number of issues were resolved that could result in wrong results
@@ -907,9 +923,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title66" id="fixed_issues__fixed_issues_2210">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title67" id="fixed_issues__fixed_issues_2210">
 
-    <h2 class="title topictitle2" id="ariaid-title66">Issues Fixed in <span class="keyword">Impala 2.2.10</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title67">Issues Fixed in <span class="keyword">Impala 2.2.10</span></h2>
 
     <div class="body conbody">
       <p class="p"></p>
@@ -917,9 +933,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title67" id="fixed_issues__fixed_issues_229">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title68" id="fixed_issues__fixed_issues_229">
 
-    <h2 class="title topictitle2" id="ariaid-title67">Issues Fixed in <span class="keyword">Impala 2.2.9</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title68">Issues Fixed in <span class="keyword">Impala 2.2.9</span></h2>
 
     <div class="body conbody">
 
@@ -929,9 +945,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
     </div>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title68" id="fixed_issues_229__IMPALA-1917">
+    <article class="topic concept nested2" aria-labelledby="ariaid-title69" id="fixed_issues_229__IMPALA-1917">
       
-      <h3 class="title topictitle3" id="ariaid-title68">Query return empty result if it contains NullLiteral in inlineview</h3>
+      <h3 class="title topictitle3" id="ariaid-title69">Query return empty result if it contains NullLiteral in inlineview</h3>
       <div class="body conbody">
       <p class="p">
         If an inline view in a <code class="ph codeph">FROM</code> clause contained a <code class="ph codeph">NULL</code> literal,
@@ -941,9 +957,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title69" id="fixed_issues_229__IMPALA-2731">
+    <article class="topic concept nested2" aria-labelledby="ariaid-title70" id="fixed_issues_229__IMPALA-2731">
       
-      <h3 class="title topictitle3" id="ariaid-title69">HBase scan node uses 2-4x memory after upgrade to Impala 2.2.8</h3>
+      <h3 class="title topictitle3" id="ariaid-title70">HBase scan node uses 2-4x memory after upgrade to Impala 2.2.8</h3>
       <div class="body conbody">
       <p class="p">
         Queries involving HBase tables used substantially more memory than in earlier Impala versions.
@@ -955,8 +971,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title70" id="fixed_issues_229__IMPALA-1459">
-      <h3 class="title topictitle3" id="ariaid-title70">Fix migration/assignment of On-clause predicates inside inline views</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title71" id="fixed_issues_229__IMPALA-1459">
+      <h3 class="title topictitle3" id="ariaid-title71">Fix migration/assignment of On-clause predicates inside inline views</h3>
       <div class="body conbody">
       
       <p class="p">
@@ -980,8 +996,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title71" id="fixed_issues_229__IMPALA-2446">
-      <h3 class="title topictitle3" id="ariaid-title71">Fix wrong predicate assignment in outer joins</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title72" id="fixed_issues_229__IMPALA-2446">
+      <h3 class="title topictitle3" id="ariaid-title72">Fix wrong predicate assignment in outer joins</h3>
       <div class="body conbody">
       <p class="p">
         The join predicate for an <code class="ph codeph">OUTER JOIN</code> clause could be applied at the wrong stage
@@ -991,8 +1007,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title72" id="fixed_issues_229__IMPALA-2648">
-      <h3 class="title topictitle3" id="ariaid-title72">Avoid sending large partition stats objects over thrift</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title73" id="fixed_issues_229__IMPALA-2648">
+      <h3 class="title topictitle3" id="ariaid-title73">Avoid sending large partition stats objects over thrift</h3>
       <div class="body conbody">
       <p class="p"> The <span class="keyword cmdname">catalogd</span> daemon could encounter a serious error when loading the
           incremental statistics metadata for tables with large numbers of partitions and columns.
@@ -1005,8 +1021,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title73" id="fixed_issues_229__IMPALA-1675">
-      <h3 class="title topictitle3" id="ariaid-title73">Avoid overflow when adding large intervals to TIMESTAMPs</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title74" id="fixed_issues_229__IMPALA-1675">
+      <h3 class="title topictitle3" id="ariaid-title74">Avoid overflow when adding large intervals to TIMESTAMPs</h3>
       <div class="body conbody">
       <p class="p"> Adding or subtracting a large <code class="ph codeph">INTERVAL</code> value to a
             <code class="ph codeph">TIMESTAMP</code> value could produce an incorrect result, with the value
@@ -1015,8 +1031,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title74" id="fixed_issues_229__IMPALA-1949">
-      <h3 class="title topictitle3" id="ariaid-title74">Analysis exception when a binary operator contains an IN operator with values</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title75" id="fixed_issues_229__IMPALA-1949">
+      <h3 class="title topictitle3" id="ariaid-title75">Analysis exception when a binary operator contains an IN operator with values</h3>
       <div class="body conbody">
       <p class="p">
         An <code class="ph codeph">IN</code> operator with literal values could cause a statement to fail if used
@@ -1026,9 +1042,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title75" id="fixed_issues_229__IMPALA-2273">
+    <article class="topic concept nested2" aria-labelledby="ariaid-title76" id="fixed_issues_229__IMPALA-2273">
     
-      <h3 class="title topictitle3" id="ariaid-title75">Make MAX_PAGE_HEADER_SIZE configurable</h3>
+      <h3 class="title topictitle3" id="ariaid-title76">Make MAX_PAGE_HEADER_SIZE configurable</h3>
       <div class="body conbody">
       <p class="p"> Impala could fail to access Parquet data files with page headers larger than 8 MB, which
           could occur, for example, if the minimum or maximum values for a column were long strings.
@@ -1038,8 +1054,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title76" id="fixed_issues_229__IMPALA-2357">
-      <h3 class="title topictitle3" id="ariaid-title76">Fix spilling sorts with var-len slots that are NULL or empty.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title77" id="fixed_issues_229__IMPALA-2357">
+      <h3 class="title topictitle3" id="ariaid-title77">Fix spilling sorts with var-len slots that are NULL or empty.</h3>
       <div class="body conbody">
       <p class="p">
         A query that activated the spill-to-disk mechanism could fail if it contained a sort expression
@@ -1049,8 +1065,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title77" id="fixed_issues_229__block_pin_oom">
-      <h3 class="title topictitle3" id="ariaid-title77">Work-around IMPALA-2344: Fail query with OOM in case block-&gt;Pin() fails</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title78" id="fixed_issues_229__block_pin_oom">
+      <h3 class="title topictitle3" id="ariaid-title78">Work-around IMPALA-2344: Fail query with OOM in case block-&gt;Pin() fails</h3>
       <div class="body conbody">
       <p class="p">
         Some queries that activated the spill-to-disk mechanism could produce a serious error
@@ -1061,8 +1077,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title78" id="fixed_issues_229__IMPALA-2252">
-      <h3 class="title topictitle3" id="ariaid-title78">Crash (likely race) tearing down BufferedBlockMgr on query failure</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title79" id="fixed_issues_229__IMPALA-2252">
+      <h3 class="title topictitle3" id="ariaid-title79">Crash (likely race) tearing down BufferedBlockMgr on query failure</h3>
       <div class="body conbody">
       <p class="p">
         A serious error could occur under rare circumstances, due to a race condition while freeing memory during heavily concurrent workloads.
@@ -1071,8 +1087,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title79" id="fixed_issues_229__IMPALA-1746">
-      <h3 class="title topictitle3" id="ariaid-title79">QueryExecState doesn't check for query cancellation or errors</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title80" id="fixed_issues_229__IMPALA-1746">
+      <h3 class="title topictitle3" id="ariaid-title80">QueryExecState doesn't check for query cancellation or errors</h3>
       <div class="body conbody">
       <p class="p">
         A call to <code class="ph codeph">SetError()</code> in a user-defined function (UDF) would not cause the query to fail as expected.
@@ -1081,8 +1097,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title80" id="fixed_issues_229__IMPALA-2533">
-      <h3 class="title topictitle3" id="ariaid-title80">Impala throws IllegalStateException when inserting data into a partition while select
+    <article class="topic concept nested2" aria-labelledby="ariaid-title81" id="fixed_issues_229__IMPALA-2533">
+      <h3 class="title topictitle3" id="ariaid-title81">Impala throws IllegalStateException when inserting data into a partition while select
         subquery group by partition columns</h3>
       <div class="body conbody">
       <p class="p">
@@ -1095,9 +1111,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title81" id="fixed_issues__fixed_issues_228">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title82" id="fixed_issues__fixed_issues_228">
 
-    <h2 class="title topictitle2" id="ariaid-title81">Issues Fixed in <span class="keyword">Impala 2.2.8</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title82">Issues Fixed in <span class="keyword">Impala 2.2.8</span></h2>
 
     <div class="body conbody">
 
@@ -1109,8 +1125,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
 
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title82" id="fixed_issues_228__IMPALA-1136">
-      <h3 class="title topictitle3" id="ariaid-title82">Impala is unable to read hive tables created with the "STORED AS AVRO" clause</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title83" id="fixed_issues_228__IMPALA-1136">
+      <h3 class="title topictitle3" id="ariaid-title83">Impala is unable to read hive tables created with the "STORED AS AVRO" clause</h3>
       <div class="body conbody">
       <p class="p">Impala could not read Avro tables created in Hive with the <code class="ph codeph">STORED AS AVRO</code> clause.</p>
       <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1136" target="_blank">IMPALA-1136</a>,
@@ -1118,8 +1134,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title83" id="fixed_issues_228__IMPALA-2213">
-      <h3 class="title topictitle3" id="ariaid-title83">make Parquet scanner fail query if the file size metadata is stale</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title84" id="fixed_issues_228__IMPALA-2213">
+      <h3 class="title topictitle3" id="ariaid-title84">make Parquet scanner fail query if the file size metadata is stale</h3>
       <div class="body conbody">
       <p class="p">If a Parquet file in HDFS was overwritten by a smaller file, Impala could encounter a serious error.
       Issuing a <code class="ph codeph">INVALIDATE METADATA</code> statement before a subsequent query would avoid the error.
@@ -1129,8 +1145,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-     <article class="topic concept nested2" aria-labelledby="ariaid-title84" id="fixed_issues_228__IMPALA-2249">
-      <h3 class="title topictitle3" id="ariaid-title84">Avoid allocating StringBuffer &gt; 1GB in ScannerContext::Stream::GetBytesInternal()</h3>
+     <article class="topic concept nested2" aria-labelledby="ariaid-title85" id="fixed_issues_228__IMPALA-2249">
+      <h3 class="title topictitle3" id="ariaid-title85">Avoid allocating StringBuffer &gt; 1GB in ScannerContext::Stream::GetBytesInternal()</h3>
       <div class="body conbody">
       <p class="p">Impala could encounter a serious error when reading compressed text files larger than 1 GB. The fix causes Impala
       to issue an error message instead in this case.</p>
@@ -1138,8 +1154,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title85" id="fixed_issues_228__IMPALA-2284">
-      <h3 class="title topictitle3" id="ariaid-title85">Disallow long (1&lt;&lt;30) strings in group_concat()</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title86" id="fixed_issues_228__IMPALA-2284">
+      <h3 class="title topictitle3" id="ariaid-title86">Disallow long (1&lt;&lt;30) strings in group_concat()</h3>
       <div class="body conbody">
       <p class="p">A query using the <code class="ph codeph">group_concat()</code> function could encounter a serious error if the returned string value was larger than 1 GB.
       Now the query fails with an error message in this case.</p>
@@ -1147,8 +1163,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title86" id="fixed_issues_228__IMPALA-2270">
-      <h3 class="title topictitle3" id="ariaid-title86">avoid FnvHash64to32 with empty inputs</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title87" id="fixed_issues_228__IMPALA-2270">
+      <h3 class="title topictitle3" id="ariaid-title87">avoid FnvHash64to32 with empty inputs</h3>
       <div class="body conbody">
       <p class="p">An edge case in the algorithm used to distribute data among nodes could result in uneven distribution of work for some queries,
       with all data sent to the same node.</p>
@@ -1156,8 +1172,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title87" id="fixed_issues_228__IMPALA-2348">
-      <h3 class="title topictitle3" id="ariaid-title87">The catalog does not close the connection to HMS during table invalidation</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title88" id="fixed_issues_228__IMPALA-2348">
+      <h3 class="title topictitle3" id="ariaid-title88">The catalog does not close the connection to HMS during table invalidation</h3>
       <div class="body conbody">
       <p class="p">A communication error could occur between Impala and the Hive metastore database, causing Impala operations that update
       table metadata to fail.</p>
@@ -1165,16 +1181,16 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title88" id="fixed_issues_228__IMPALA-2364-548">
-      <h3 class="title topictitle3" id="ariaid-title88">Wrong DCHECK in PHJ::ProcessProbeBatch</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title89" id="fixed_issues_228__IMPALA-2364-548">
+      <h3 class="title topictitle3" id="ariaid-title89">Wrong DCHECK in PHJ::ProcessProbeBatch</h3>
       <div class="body conbody">
       <p class="p">Certain queries could encounter a serious error if the spill-to-disk mechanism was activated.</p>
       <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2364" target="_blank">IMPALA-2364</a></p>
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title89" id="fixed_issues_228__IMPALA-2165-548">
-      <h3 class="title topictitle3" id="ariaid-title89">Avoid cardinality 0 in scan nodes of small tables and low selectivity</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title90" id="fixed_issues_228__IMPALA-2165-548">
+      <h3 class="title topictitle3" id="ariaid-title90">Avoid cardinality 0 in scan nodes of small tables and low selectivity</h3>
       <div class="body conbody">
       <p class="p">Impala could generate a suboptimal query plan for some queries involving small tables.</p>
       <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2165" target="_blank">IMPALA-2165</a></p>
@@ -1183,9 +1199,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title90" id="fixed_issues__fixed_issues_227">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title91" id="fixed_issues__fixed_issues_227">
 
-    <h2 class="title topictitle2" id="ariaid-title90">Issues Fixed in <span class="keyword">Impala 2.2.7</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title91">Issues Fixed in <span class="keyword">Impala 2.2.7</span></h2>
 
     <div class="body conbody">
 
@@ -1195,8 +1211,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
     </div>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title91" id="fixed_issues_227__IMPALA-1983">
-      <h3 class="title topictitle3" id="ariaid-title91">Warn if table stats are potentially corrupt.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title92" id="fixed_issues_227__IMPALA-1983">
+      <h3 class="title topictitle3" id="ariaid-title92">Warn if table stats are potentially corrupt.</h3>
       <div class="body conbody">
       <p class="p">
         Impala warns if it detects a discrepancy in table statistics: a table considered to have zero rows even though there are data files present.
@@ -1206,24 +1222,24 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title92" id="fixed_issues_227__IMPALA-2266">
-      <h3 class="title topictitle3" id="ariaid-title92">Pass correct child node in 2nd phase merge aggregation.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title93" id="fixed_issues_227__IMPALA-2266">
+      <h3 class="title topictitle3" id="ariaid-title93">Pass correct child node in 2nd phase merge aggregation.</h3>
       <div class="body conbody">
       <p class="p">A query could encounter a serious error if it included a particular combination of aggregate functions and inline views.</p>
       <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2266" target="_blank">IMPALA-2266</a></p>
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title93" id="fixed_issues_227__IMPALA-2216">
-      <h3 class="title topictitle3" id="ariaid-title93">Set the output smap of an EmptySetNode produced from an empty inline view.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title94" id="fixed_issues_227__IMPALA-2216">
+      <h3 class="title topictitle3" id="ariaid-title94">Set the output smap of an EmptySetNode produced from an empty inline view.</h3>
       <div class="body conbody">
       <p class="p">A query could encounter a serious error if it included an inline view whose subquery had no <code class="ph codeph">FROM</code> clause.</p>
       <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2216" target="_blank">IMPALA-2216</a></p>
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title94" id="fixed_issues_227__IMPALA-2203">
-      <h3 class="title topictitle3" id="ariaid-title94">Set an InsertStmt's result exprs from the source statement's result exprs.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title95" id="fixed_issues_227__IMPALA-2203">
+      <h3 class="title topictitle3" id="ariaid-title95">Set an InsertStmt's result exprs from the source statement's result exprs.</h3>
       <div class="body conbody">
       <p class="p">
       A <code class="ph codeph">CREATE TABLE AS SELECT</code> or <code class="ph codeph">INSERT ... SELECT</code> statement could produce
@@ -1234,8 +1250,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title95" id="fixed_issues_227__IMPALA-2088">
-      <h3 class="title topictitle3" id="ariaid-title95">Fix planning of empty union operands with analytics.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title96" id="fixed_issues_227__IMPALA-2088">
+      <h3 class="title topictitle3" id="ariaid-title96">Fix planning of empty union operands with analytics.</h3>
       <div class="body conbody">
       <p class="p">
         A query could return incorrect results if it contained a <code class="ph codeph">UNION</code> clause,
@@ -1249,8 +1265,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
 
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title96" id="fixed_issues_227__IMPALA-2089">
-      <h3 class="title topictitle3" id="ariaid-title96">Retain eq predicates bound by grouping slots with complex grouping exprs.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title97" id="fixed_issues_227__IMPALA-2089">
+      <h3 class="title topictitle3" id="ariaid-title97">Retain eq predicates bound by grouping slots with complex grouping exprs.</h3>
       <div class="body conbody">
       <p class="p">
         A query containing an <code class="ph codeph">INNER JOIN</code> clause could return undesired rows.
@@ -1262,8 +1278,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
 
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title97" id="fixed_issues_227__IMPALA-2199">
-      <h3 class="title topictitle3" id="ariaid-title97">Row count not set for empty partition when spec is used with compute incremental stats</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title98" id="fixed_issues_227__IMPALA-2199">
+      <h3 class="title topictitle3" id="ariaid-title98">Row count not set for empty partition when spec is used with compute incremental stats</h3>
       <div class="body conbody">
       <p class="p">
         A <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> statement could leave the row count for an emptyp partition as -1,
@@ -1273,8 +1289,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title98" id="fixed_issues_227__IMPALA-1898">
-      <h3 class="title topictitle3" id="ariaid-title98">Explicit aliases + ordinals analysis bug</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title99" id="fixed_issues_227__IMPALA-1898">
+      <h3 class="title topictitle3" id="ariaid-title99">Explicit aliases + ordinals analysis bug</h3>
       <div class="body conbody">
       <p class="p">
         A query could encounter a serious error if it included column aliases with the same names as table columns, and used
@@ -1284,8 +1300,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title99" id="fixed_issues_227__IMPALA-1987">
-      <h3 class="title topictitle3" id="ariaid-title99">Fix TupleIsNullPredicate to return false if no tuples are nullable.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title100" id="fixed_issues_227__IMPALA-1987">
+      <h3 class="title topictitle3" id="ariaid-title100">Fix TupleIsNullPredicate to return false if no tuples are nullable.</h3>
       <div class="body conbody">
       <p class="p">
         A query could return incorrect results if it included an outer join clause, inline views, and calls to functions such as <code class="ph codeph">coalesce()</code>
@@ -1295,8 +1311,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title100" id="fixed_issues_227__IMPALA-2178">
-      <h3 class="title topictitle3" id="ariaid-title100">fix Expr::ComputeResultsLayout() logic</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title101" id="fixed_issues_227__IMPALA-2178">
+      <h3 class="title topictitle3" id="ariaid-title101">fix Expr::ComputeResultsLayout() logic</h3>
       <div class="body conbody">
       <p class="p">
         A query could return incorrect results if the table contained multiple <code class="ph codeph">CHAR</code> columns with length of 2 or less,
@@ -1306,8 +1322,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title101" id="fixed_issues_227__IMPALA-1737">
-      <h3 class="title topictitle3" id="ariaid-title101">Substitute an InsertStmt's partition key exprs with the root node's smap.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title102" id="fixed_issues_227__IMPALA-1737">
+      <h3 class="title topictitle3" id="ariaid-title102">Substitute an InsertStmt's partition key exprs with the root node's smap.</h3>
       <div class="body conbody">
       <p class="p">
         An <code class="ph codeph">INSERT</code> statement could encounter a serious error if the <code class="ph codeph">SELECT</code>
@@ -1319,9 +1335,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title102" id="fixed_issues__fixed_issues_225">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title103" id="fixed_issues__fixed_issues_225">
 
-    <h2 class="title topictitle2" id="ariaid-title102">Issues Fixed in Impala <span class="keyword">Impala 2.2.5</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title103">Issues Fixed in Impala <span class="keyword">Impala 2.2.5</span></h2>
 
     <div class="body conbody">
 
@@ -1331,8 +1347,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
     </div>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title103" id="fixed_issues_225__IMPALA-2048">
-      <h3 class="title topictitle3" id="ariaid-title103">Impala DML/DDL operations corrupt table metadata leading to Hive query failures</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title104" id="fixed_issues_225__IMPALA-2048">
+      <h3 class="title topictitle3" id="ariaid-title104">Impala DML/DDL operations corrupt table metadata leading to Hive query failures</h3>
       <div class="body conbody">
       <p class="p">
         When the Impala <code class="ph codeph">COMPUTE STATS</code> statement was run on a partitioned Parquet table that was created in Hive, the table subsequently became inaccessible in Hive.
@@ -1343,8 +1359,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title104" id="fixed_issues_225__IMPALA-1929">
-      <h3 class="title topictitle3" id="ariaid-title104">Avoiding a DCHECK of NULL hash table in spilled right joins</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title105" id="fixed_issues_225__IMPALA-1929">
+      <h3 class="title topictitle3" id="ariaid-title105">Avoiding a DCHECK of NULL hash table in spilled right joins</h3>
       
       <div class="body conbody">
       <p class="p">
@@ -1355,8 +1371,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title105" id="fixed_issues_225__IMPALA-2136">
-      <h3 class="title topictitle3" id="ariaid-title105">Bug in PrintTColumnValue caused wrong stats for TINYINT partition cols</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title106" id="fixed_issues_225__IMPALA-2136">
+      <h3 class="title topictitle3" id="ariaid-title106">Bug in PrintTColumnValue caused wrong stats for TINYINT partition cols</h3>
       
       <div class="body conbody">
       <p class="p">
@@ -1367,8 +1383,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title106" id="fixed_issues_225__IMPALA-2018">
-      <h3 class="title topictitle3" id="ariaid-title106">Where clause does not propagate to joins inside nested views</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title107" id="fixed_issues_225__IMPALA-2018">
+      <h3 class="title topictitle3" id="ariaid-title107">Where clause does not propagate to joins inside nested views</h3>
       
       <div class="body conbody">
       <p class="p">
@@ -1380,8 +1396,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title107" id="fixed_issues_225__IMPALA-2064">
-      <h3 class="title topictitle3" id="ariaid-title107">Add effective_user() builtin</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title108" id="fixed_issues_225__IMPALA-2064">
+      <h3 class="title topictitle3" id="ariaid-title108">Add effective_user() builtin</h3>
       
       <div class="body conbody">
       <p class="p">
@@ -1394,8 +1410,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title108" id="fixed_issues_225__IMPALA-2125">
-      <h3 class="title topictitle3" id="ariaid-title108">Make UTC to local TimestampValue conversion faster.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title109" id="fixed_issues_225__IMPALA-2125">
+      <h3 class="title topictitle3" id="ariaid-title109">Make UTC to local TimestampValue conversion faster.</h3>
       
       <div class="body conbody">
       <p class="p">
@@ -1407,8 +1423,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title109" id="fixed_issues_225__IMPALA-2065">
-      <h3 class="title topictitle3" id="ariaid-title109">Workaround IMPALA-1619 in BufferedBlockMgr::ConsumeMemory()</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title110" id="fixed_issues_225__IMPALA-2065">
+      <h3 class="title topictitle3" id="ariaid-title110">Workaround IMPALA-1619 in BufferedBlockMgr::ConsumeMemory()</h3>
       
       <div class="body conbody">
       <p class="p">
@@ -1425,9 +1441,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title110" id="fixed_issues__fixed_issues_223">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title111" id="fixed_issues__fixed_issues_223">
 
-    <h2 class="title topictitle2" id="ariaid-title110">Issues Fixed in <span class="keyword">Impala 2.2.3</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title111">Issues Fixed in <span class="keyword">Impala 2.2.3</span></h2>
 
     <div class="body conbody">
 
@@ -1437,8 +1453,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
     </div>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title111" id="fixed_issues_223__isilon_support">
-      <h3 class="title topictitle3" id="ariaid-title111">Enable using Isilon as the underlying filesystem.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title112" id="fixed_issues_223__isilon_support">
+      <h3 class="title topictitle3" id="ariaid-title112">Enable using Isilon as the underlying filesystem.</h3>
       <div class="body conbody">
       <p class="p">
         Enabling Impala to work with the Isilon filesystem involves a number of
@@ -1454,8 +1470,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
 
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title112" id="fixed_issues_223__IMPALA-1381">
-      <h3 class="title topictitle3" id="ariaid-title112">Expand set of supported timezones.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title113" id="fixed_issues_223__IMPALA-1381">
+      <h3 class="title topictitle3" id="ariaid-title113">Expand set of supported timezones.</h3>
       <div class="body conbody">
       <p class="p">
         The set of timezones recognized by Impala was expanded.
@@ -1467,8 +1483,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title113" id="fixed_issues_223__IMPALA-1963">
-      <h3 class="title topictitle3" id="ariaid-title113">Impala Timestamp ISO-8601 Support.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title114" id="fixed_issues_223__IMPALA-1963">
+      <h3 class="title topictitle3" id="ariaid-title114">Impala Timestamp ISO-8601 Support.</h3>
       <div class="body conbody">
       <p class="p">
         Impala can now process <code class="ph codeph">TIMESTAMP</code> literals including a trailing <code class="ph codeph">z</code>,
@@ -1478,8 +1494,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title114" id="fixed_issues_223__IMPALA-2008">
-      <h3 class="title topictitle3" id="ariaid-title114">Fix wrong warning when insert overwrite to empty table</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title115" id="fixed_issues_223__IMPALA-2008">
+      <h3 class="title topictitle3" id="ariaid-title115">Fix wrong warning when insert overwrite to empty table</h3>
       <div class="body conbody">
       <p class="p">
         An <code class="ph codeph">INSERT OVERWRITE</code> operation would encounter an error
@@ -1490,10 +1506,10 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title115" id="fixed_issues_223__IMPALA-1952">
+    <article class="topic concept nested2" aria-labelledby="ariaid-title116" id="fixed_issues_223__IMPALA-1952">
     
     
-      <h3 class="title topictitle3" id="ariaid-title115">Expand parsing of decimals to include scientific notation</h3>
+      <h3 class="title topictitle3" id="ariaid-title116">Expand parsing of decimals to include scientific notation</h3>
       <div class="body conbody">
       <p class="p">
         <code class="ph codeph">DECIMAL</code> literals can now include <code class="ph codeph">e</code> scientific notation.
@@ -1507,9 +1523,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
 
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title116" id="fixed_issues__fixed_issues_221">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title117" id="fixed_issues__fixed_issues_221">
 
-    <h2 class="title topictitle2" id="ariaid-title116">Issues Fixed in <span class="keyword">Impala 2.2.1</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title117">Issues Fixed in <span class="keyword">Impala 2.2.1</span></h2>
 
     <div class="body conbody">
 
@@ -1520,9 +1536,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
     </div>
   </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title117" id="fixed_issues__fixed_issues_220">
+  <article class="topic concept nested1" aria-labelledby="ariaid-title118" id="fixed_issues__fixed_issues_220">
 
-    <h2 class="title topictitle2" id="ariaid-title117">Issues Fixed in <span class="keyword">Impala 2.2.0</span></h2>
+    <h2 class="title topictitle2" id="ariaid-title118">Issues Fixed in <span class="keyword">Impala 2.2.0</span></h2>
 
     <div class="body conbody">
 
@@ -1539,8 +1555,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
     </div>
 
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title118" id="fixed_issues_220__IMPALA-1607">
-      <h3 class="title topictitle3" id="ariaid-title118">Altering a column's type causes column stats to stop sticking for that column</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title119" id="fixed_issues_220__IMPALA-1607">
+      <h3 class="title topictitle3" id="ariaid-title119">Altering a column's type causes column stats to stop sticking for that column</h3>
       <div class="body conbody">
       <p class="p">
       When the type of a column was changed in either Hive or Impala through <code class="ph codeph">ALTER TABLE CHANGE COLUMN</code>, the metastore database did not correctly propagate
@@ -1553,16 +1569,16 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title119" id="fixed_issues_220__IMPALA-1854">
-      <h3 class="title topictitle3" id="ariaid-title119">Impala may leak or use too many file descriptors</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title120" id="fixed_issues_220__IMPALA-1854">
+      <h3 class="title topictitle3" id="ariaid-title120">Impala may leak or use too many file descriptors</h3>
       <div class="body conbody">
       <p class="p">If a file was truncated in HDFS without a corresponding <code class="ph codeph">REFRESH</code> in Impala, Impala could allocate memory for file descriptors and not free that memory.</p>
       <p class="p"><strong class="ph b">Bug:</strong> <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1854" target="_blank">IMPALA-1854</a></p>
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title120" id="fixed_issues_220__IMPALA-1712">
-      <h3 class="title topictitle3" id="ariaid-title120">Spurious stale block locality messages</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title121" id="fixed_issues_220__IMPALA-1712">
+      <h3 class="title topictitle3" id="ariaid-title121">Spurious stale block locality messages</h3>
       <div class="body conbody">
       <p class="p">
         Impala could issue messages stating the block locality metadata was stale,
@@ -1576,8 +1592,8 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title121" id="fixed_issues_220__IMPALA-1711">
-      <h3 class="title topictitle3" id="ariaid-title121">DROP TABLE fails after COMPUTE STATS and ALTER TABLE RENAME to a different database.</h3>
+    <article class="topic concept nested2" aria-labelledby="ariaid-title122" id="fixed_issues_220__IMPALA-1711">
+      <h3 class="title topictitle3" id="ariaid-title122">DROP TABLE fails after COMPUTE STATS and ALTER TABLE RENAME to a different database.</h3>
       <div class="body conbody">
       <p class="p">
         When a table was moved from one database to another, the column statistics were not pointed to the new database.i
@@ -1588,9 +1604,9 @@ select 2061013007, conv(cast(cast(2061013007 as decimal(20,0)) as bigint), 16, 1
       </div>
     </article>
 
-    <article class="topic concept nested2" aria-labelledby="ariaid-title122" id="fixed_issues_220__IMPALA-1674">
+    <article class="topic concept nested2" aria-labelledby="ariaid-title123" id="fixed_issues_220__IMPALA-1674">
 
-      <h3 class="title topictitle3" id="ariaid-title122">IMPALA-1556 causes memory leak with secure connections</h3>
+      <h3 class="title topictitle3" id="ariaid-title123">IMPALA-1556 causes memory leak with secure connections</h3>
 
       <div class="body

<TRUNCATED>