You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by mi...@apache.org on 2018/12/06 23:14:43 UTC

[17/51] [partial] impala git commit: [DOCS] Impala 3.1 Docs to be published

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/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 155756a..5532a05 100644
--- a/docs/build/html/topics/impala_new_features.html
+++ b/docs/build/html/topics/impala_new_features.html
@@ -1,9 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
 <!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 2018"><meta name="DC.rights.owner" content="(C) Copyright 2018"><meta name="DC.Type" content="concept"><meta name="DC.Relation" scheme="URI" content="../topics/impala_release_notes.html"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.12x"><meta name="version" content="Impala 2.12x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="new_features"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>New Features in Apache Impala</title></head><body id="new_features"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
+  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
+<head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+
+<meta name="copyright" content="(C) Copyright 2018" />
+<meta name="DC.rights.owner" content="(C) Copyright 2018" />
+<meta name="DC.Type" content="concept" />
+<meta name="DC.Title" content="New Features in Apache Impala" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_release_notes.html" />
+<meta name="prodname" content="Impala" />
+<meta name="prodname" content="Impala" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="new_features" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>New Features in Apache Impala</title>
+</head>
+<body id="new_features">
+
 
   <h1 class="title topictitle1" id="ariaid-title1"><span class="ph">New Features in Apache Impala</span></h1>
 
+
   
 
   <div class="body conbody">
@@ -12,15 +32,52 @@
       This release of Impala contains the following changes and enhancements from previous releases.
     </p>
 
+
     <p class="p toc inpage"></p>
 
+
+  </div>
+
+
+  <div 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>
+</div><div class="topic concept nested1" aria-labelledby="ariaid-title2" id="new_features_31">
+    <h2 class="title topictitle2" id="ariaid-title2">New Features in <span class="keyword">Impala 3.1</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.apache.org/docs/changelog-3.1.html" target="_blank">changelog for <span class="keyword">Impala 3.1</span></a>. </p>
+
+    </div>
+
+  </div>
+
+
+
+  <div class="topic concept nested1" aria-labelledby="ariaid-title3" id="new_features_300">
+    <h2 class="title topictitle2" id="ariaid-title3">New Features in <span class="keyword">Impala 3.0</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.apache.org/docs/changelog-3.0.html" target="_blank">changelog for <span class="keyword">Impala 3.0</span></a>.
+      </p>
+
+    </div>
+
   </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="new_features__new_features_2120">
 
-    <h2 class="title topictitle2" id="ariaid-title2">New Features in <span class="keyword">Impala 2.12</span></h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title4" id="new_features_2120">
+
+    <h2 class="title topictitle2" id="ariaid-title4">New Features in <span class="keyword">Impala 2.12</span></h2>
+
 
     <div class="body conbody">
 
@@ -30,14 +87,18 @@
         <a class="xref" href="https://impala.apache.org/docs/changelog-2.12.html" target="_blank">changelog for <span class="keyword">Impala 2.12</span></a>.
       </p>
 
+
     </div>
-  </article>
+
+  </div>
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title3" id="new_features__new_features_2110">
 
-    <h2 class="title topictitle2" id="ariaid-title3">New Features in <span class="keyword">Impala 2.11</span></h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title5" id="new_features_2110">
+
+    <h2 class="title topictitle2" id="ariaid-title5">New Features in <span class="keyword">Impala 2.11</span></h2>
+
 
     <div class="body conbody">
 
@@ -47,14 +108,18 @@
         <a class="xref" href="https://impala.apache.org/docs/changelog-2.11.html" target="_blank">changelog for <span class="keyword">Impala 2.11</span></a>.
       </p>
 
+
     </div>
-  </article>
+
+  </div>
+
+
 
 
+  <div class="topic concept nested1" aria-labelledby="ariaid-title6" id="new_features_2100">
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title4" id="new_features__new_features_2100">
+    <h2 class="title topictitle2" id="ariaid-title6">New Features in <span class="keyword">Impala 2.10</span></h2>
 
-    <h2 class="title topictitle2" id="ariaid-title4">New Features in <span class="keyword">Impala 2.10</span></h2>
 
     <div class="body conbody">
 
@@ -64,14 +129,18 @@
         <a class="xref" href="https://impala.apache.org/docs/changelog-2.10.html" target="_blank">changelog for <span class="keyword">Impala 2.10</span></a>.
       </p>
 
+
     </div>
-  </article>
+
+  </div>
+
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title5" id="new_features__new_features_290">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title7" id="new_features_290">
+
+    <h2 class="title topictitle2" id="ariaid-title7">New Features in <span class="keyword">Impala 2.9</span></h2>
 
-    <h2 class="title topictitle2" id="ariaid-title5">New Features in <span class="keyword">Impala 2.9</span></h2>
 
     <div class="body conbody">
 
@@ -81,10 +150,12 @@
         <a class="xref" href="https://impala.apache.org/docs/changelog-2.9.html" target="_blank">changelog for <span class="keyword">Impala 2.9</span></a>.
       </p>
 
+
       <p class="p">
         The following are some of the most significant new features in this release:
       </p>
 
+
       <ul class="ul" id="new_features_290__feature_list">
         <li class="li">
           <p class="p">
@@ -92,7 +163,9 @@
             <code class="ph codeph">regexp_replace()</code> for simple string substitutions.
             See <a class="xref" href="impala_string_functions.html">Impala String Functions</a> for details.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Startup flags for the <span class="keyword cmdname">impalad</span> daemon, <code class="ph codeph">is_executor</code>
@@ -100,19 +173,25 @@
             between a small number of hosts acting as query coordinators, and a larger number of
             hosts acting as query executors. By default, each host can act in both roles,
             potentially introducing bottlenecks during heavily concurrent workloads.
-            See <a class="xref" href="impala_scalability.html">Scalability Considerations for Impala</a> for details.
+            See <a class="xref" href="impala_dedicated_coordinator.html">How to Configure Impala with Dedicated Coordinators</a> for details.
           </p>
+
         </li>
+
       </ul>
 
+
     </div>
-  </article>
+
+  </div>
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title6" id="new_features__new_features_280">
 
-    <h2 class="title topictitle2" id="ariaid-title6">New Features in <span class="keyword">Impala 2.8</span></h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title8" id="new_features_280">
+
+    <h2 class="title topictitle2" id="ariaid-title8">New Features in <span class="keyword">Impala 2.8</span></h2>
+
 
     <div class="body conbody">
 
@@ -121,36 +200,46 @@
           <p class="p">
             Performance and scalability improvements:
           </p>
+
           <ul class="ul">
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">COMPUTE STATS</code> statement can
                 take advantage of multithreading.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Improved scalability for highly concurrent loads by reducing the possibility of TCP/IP timeouts.
                 A configuration setting, <code class="ph codeph">accepted_cnxn_queue_depth</code>, can be adjusted upwards to
                 avoid this type of timeout on large clusters.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Several performance improvements were made to the mechanism for generating native code:
               </p>
+
               <ul class="ul">
                 <li class="li">
                   <p class="p">
                     Some queries involving analytic functions can take better advantage of native code generation.
                   </p>
+
                 </li>
+
                 <li class="li">
                   <p class="p">
                     Modules produced during intermediate code generation are organized
                     to be easier to cache and reuse during the lifetime of a long-running or complicated query.
                   </p>
+
                 </li>
+
                 <li class="li">
                   <p class="p">
                     The <code class="ph codeph">COMPUTE STATS</code> statement is more efficient
@@ -158,15 +247,21 @@
                     of columns, especially for tables containing <code class="ph codeph">TIMESTAMP</code>
                     columns.
                   </p>
+
                 </li>
+
                 <li class="li">
                   <p class="p">
                     The logic for determining whether or not to use a runtime filter is more reliable, and the
                     evaluation process itself is faster because of native code generation.
                   </p>
+
                 </li>
+
               </ul>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">MT_DOP</code> query option enables
@@ -176,14 +271,18 @@
                 intra-node parallelism and CPU efficiency of this data-intensive
                 operation.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">COMPUTE STATS</code> statement is more efficient
                 (less time for the codegen phase) for tables with a large number
                 of columns.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 A new hint, <code class="ph codeph">CLUSTERED</code>,
@@ -194,14 +293,18 @@
                 by a single host, reducing the amount of memory needed to buffer
                 Parquet data while the data blocks are being constructed.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The new configuration setting <code class="ph codeph">inc_stats_size_limit_bytes</code>
                 lets you reduce the load on the catalog server when running the
                 <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> statement for very large tables.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Impala folds many constant expressions within query statements,
@@ -210,32 +313,42 @@
                 format <code class="ph codeph">TIMESTAMP</code> values, such as the result
                 of an expression such as <code class="ph codeph">to_date(now() - interval 1 day)</code>.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Parsing of complicated expressions is faster. This speedup is
                 especially useful for queries containing large <code class="ph codeph">CASE</code>
                 expressions.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Evaluation is faster for <code class="ph codeph">IN</code> operators with many constant
                 arguments. The same performance improvement applies to other functions
                 with many constant arguments.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Impala optimizes identical comparison operators within multiple <code class="ph codeph">OR</code>
                 blocks.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The reporting for wall-clock times and total CPU time in profile output is more accurate.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 A new query option, <code class="ph codeph">SCRATCH_LIMIT</code>, lets you restrict the amount of
@@ -245,13 +358,18 @@
                 without restarting the cluster to turn the spilling feature off entirely.
                 See <a class="xref" href="impala_scratch_limit.html#scratch_limit">SCRATCH_LIMIT Query Option</a> for details.
               </p>
+
             </li>
+
           </ul>
+
         </li>
+
         <li class="li">
           <p class="p">
             Integration with Apache Kudu:
           </p>
+
           <ul class="ul">
             <li class="li">
               <p class="p">
@@ -259,21 +377,27 @@
                 into the main Impala development branch. Impala can now directly access Kudu tables,
                 opening up new capabilities such as enhanced DML operations and continuous ingestion.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">DELETE</code> statement is a flexible way to remove data from a Kudu table. Previously,
                 removing data from an Impala table involved removing or rewriting the underlying data files, dropping entire partitions,
                 or rewriting the entire table. This Impala statement only works for Kudu tables.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">UPDATE</code> statement is a flexible way to modify data within a Kudu table. Previously,
                 updating data in an Impala table involved replacing the underlying data files, dropping entire partitions,
                 or rewriting the entire table. This Impala statement only works for Kudu tables.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">UPSERT</code> statement is a flexible way to ingest, modify, or both data within a Kudu table. Previously,
@@ -282,7 +406,9 @@
                 the primary key designation for Kudu tables, lets you add or replace rows in a single operation, and
                 automatically avoids creating any duplicate data.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">CREATE TABLE</code> statement gains some new clauses that are specific to Kudu tables:
@@ -292,7 +418,9 @@
                 These clauses replace the explicit <code class="ph codeph">TBLPROPERTIES</code> settings that were required in the
                 early experimental phases of integration between Impala and Kudu.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">ALTER TABLE</code> statement can change certain attributes of Kudu tables.
@@ -302,14 +430,18 @@
                 independently from the Impala table name in the metastore database.
                 You cannot change the data type of an existing column in a Kudu table.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">SHOW PARTITIONS</code> statement displays information about the distribution of data
                 between partitions in Kudu tables. A new variation, <code class="ph codeph">SHOW RANGE PARTITIONS</code>,
                 displays information about the Kudu-specific partitions that apply across ranges of key values.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Not all Impala data types are supported in Kudu tables. In particular, currently the Impala
@@ -321,20 +453,26 @@
                 cast values in a result set to these types. Certain types, such as <code class="ph codeph">BOOLEAN</code>,
                 cannot be used as primary key columns.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Currently, Kudu tables are not interchangeable between Impala and Hive the way other kinds of Impala tables are.
                 Although the metadata for Kudu tables is stored in the metastore database, currently Hive cannot access Kudu tables.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">INSERT</code> statement works for Kudu tables. The organization
                 of the Kudu data makes it more efficient than with HDFS-backed tables to insert
                 data in small batches, such as with the <code class="ph codeph">INSERT ... VALUES</code> syntax.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Some audit data is recorded for data governance purposes.
@@ -342,7 +480,9 @@
                 as <code class="ph codeph">INSERT</code> operations in the audit log. Currently, lineage metadata is not generated for
                 <code class="ph codeph">UPDATE</code> and <code class="ph codeph">DELETE</code> operations on Kudu tables.
               </p>
+
             </li>
+
             <li class="li">
               <div class="p">
                 Currently, Kudu tables have limited support for Sentry:
@@ -351,36 +491,50 @@
                     <p class="p">
                       Access to Kudu tables must be granted to roles as usual.
                     </p>
+
                   </li>
+
                   <li class="li">
                     <p class="p">
                       Currently, access to a Kudu table through Sentry is <span class="q">"all or nothing"</span>.
                       You cannot enforce finer-grained permissions such as at the column level,
                       or permissions on certain operations such as <code class="ph codeph">INSERT</code>.
                     </p>
+
                   </li>
+
                   <li class="li">
                     <p class="p">
                       Only users with <code class="ph codeph">ALL</code> privileges on <code class="ph codeph">SERVER</code> can create external Kudu tables.
                     </p>
+
                   </li>
+
                 </ul>
+
                 Because non-SQL APIs can access Kudu data without going through Sentry
                 authorization, currently the Sentry support is considered preliminary.
               </div>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Equality and <code class="ph codeph">IN</code> predicates in Impala queries are pushed to
                 Kudu and evaluated efficiently by the Kudu storage layer.
               </p>
+
             </li>
+
           </ul>
+
         </li>
+
         <li class="li">
           <p class="p">
             <strong class="ph b">Security:</strong>
           </p>
+
           <ul class="ul">
             <li class="li">
               <p class="p">
@@ -388,16 +542,13 @@
                 store, to avoid exposing the secret key when accessing
                 data stored on S3.
               </p>
+
             </li>
+
           </ul>
+
         </li>
-        <li class="li">
-          <p class="p">
-            The <code class="ph codeph">REFRESH</code> statement now updates information about HDFS block locations.
-            Therefore, you can perform a fast and efficient <code class="ph codeph">REFRESH</code> after doing an HDFS
-            rebalancing operation instead of the more expensive <code class="ph codeph">INVALIDATE METADATA</code> statement.
-          </p>
-        </li>
+
         <li class="li">
           <p class="p">
             [<a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-1654" target="_blank">IMPALA-1654</a>]
@@ -417,53 +568,70 @@
             <code class="ph codeph">SET LOCATION</code>, and <code class="ph codeph">INSERT</code> with a static
             partitioning clause.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             The <code class="ph codeph">instr()</code> function has optional second and third arguments, representing
             the character to position to begin searching for the substring, and the Nth occurrence
             of the substring to find.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Improved error handling for malformed Avro data. In particular, incorrect
             precision or scale for <code class="ph codeph">DECIMAL</code> types is now handled.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Impala debug web UI:
           </p>
+
           <ul class="ul">
             <li class="li">
               <p class="p">
                 In addition to <span class="q">"inflight"</span> and <span class="q">"finished"</span> queries, the web UI
                 now also includes a section for <span class="q">"queued"</span> queries.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <span class="ph uicontrol">/sessions</span> tab now clarifies how many of the displayed
                 sections are active, and lets you sort by <span class="ph uicontrol">Expired</span> status
                 to distinguish active sessions from expired ones.
               </p>
+
             </li>
+
           </ul>
+
         </li>
+
         <li class="li">
           <p class="p">
             Improved stability when DDL operations such as <code class="ph codeph">CREATE DATABASE</code>
             or <code class="ph codeph">DROP DATABASE</code> are run in Hive at the same time as an Impala
             <code class="ph codeph">INVALIDATE METADATA</code> statement.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             The <span class="q">"out of memory"</span> error report was made more user-friendly, with additional
             diagnostic information to help identify the spot where the memory limit was exceeded.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Improved disk space usage for Java-based UDFs. Temporary copies of the associated JAR
@@ -473,17 +641,23 @@
             configuration setting, so that the storage for these temporary files can be independent
             from any capacity limits on the <span class="ph filepath">/tmp</span> filesystem.
           </p>
+
         </li>
+
       </ul>
 
+
     </div>
-  </article>
+
+  </div>
+
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title7" id="new_features__new_features_270">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title9" id="new_features_270">
+
+    <h2 class="title topictitle2" id="ariaid-title9">New Features in <span class="keyword">Impala 2.7</span></h2>
 
-    <h2 class="title topictitle2" id="ariaid-title7">New Features in <span class="keyword">Impala 2.7</span></h2>
 
     <div class="body conbody">
 
@@ -492,6 +666,7 @@
           <p class="p">
             Performance improvements:
           </p>
+
           <ul class="ul">
             <li class="li">
               <p class="p">
@@ -500,14 +675,18 @@
                 The code that parses <code class="ph codeph">DECIMAL</code> values from Avro now uses
                 native code generation.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 [<a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3674" target="_blank">IMPALA-3674</a>]
                 Improved efficiency in LLVM code generation can reduce codegen time, especially
                 for short queries.
               </p>
+
             </li>
+
             
             <li class="li">
               <p class="p">
@@ -516,9 +695,13 @@
                 enabled by the <code class="ph codeph">REPLICA_PREFERENCE</code> query option.
                 See <a class="xref" href="impala_replica_preference.html#replica_preference">REPLICA_PREFERENCE Query Option (Impala 2.7 or higher only)</a> for details.
               </p>
+
             </li>
+
           </ul>
+
         </li>
+
         
         <li class="li">
           <p class="p">
@@ -527,11 +710,14 @@
             rather than the entire table. See <a class="xref" href="impala_refresh.html#refresh">REFRESH Statement</a>
             and <a class="xref" href="impala_partitioning.html#partition_refresh">Refreshing a Single Partition</a> for details.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Improvements to the Impala web user interface:
           </p>
+
           <ul class="ul">
             <li class="li">
               <p class="p">
@@ -539,23 +725,31 @@
                 You can now force a session to expire by clicking a link in the web UI,
                 on the <span class="ph uicontrol">/sessions</span> tab.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 [<a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3715" target="_blank">IMPALA-3715</a>]
                 The <span class="ph uicontrol">/memz</span> tab includes more information about
                 Impala memory usage.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 [<a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3716" target="_blank">IMPALA-3716</a>]
                 The <span class="ph uicontrol">Details</span> page for a query now includes
                 a <span class="ph uicontrol">Memory</span> tab.
               </p>
+
             </li>
+
           </ul>
+
         </li>
+
         <li class="li">
           <p class="p">
             [<a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3499" target="_blank">IMPALA-3499</a>]
@@ -563,7 +757,9 @@
             more efficiently for tables with large numbers of columns and partitions, where the
             size of the metadata exceeds 2 GiB.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             [<a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3677" target="_blank">IMPALA-3677</a>]
@@ -572,7 +768,9 @@
             without triggering a crash. See <a class="xref" href="impala_breakpad.html#breakpad">Breakpad Minidumps for Impala (Impala 2.6 or higher only)</a> for
             details about the Breakpad minidump feature.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             [<a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3687" target="_blank">IMPALA-3687</a>]
@@ -585,7 +783,9 @@
             See <a class="xref" href="impala_avro.html#avro_create_table">Creating Avro Tables</a> for details about
             column definitions in Avro tables.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             [<a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-3575" target="_blank">IMPALA-3575</a>]
@@ -595,16 +795,22 @@
             problems, to avoid hangs when a sender or receiver fails in the
             middle of a network transmission, and to make cancellation requests
             more reliable despite network issues. </p>
+
         </li>
+
       </ul>
 
+
     </div>
-  </article>
+
+  </div>
+
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title8" id="new_features__new_features_260">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title10" id="new_features_260">
+
+    <h2 class="title topictitle2" id="ariaid-title10">New Features in <span class="keyword">Impala 2.6</span></h2>
 
-    <h2 class="title topictitle2" id="ariaid-title8">New Features in <span class="keyword">Impala 2.6</span></h2>
 
     <div class="body conbody">
 
@@ -613,6 +819,7 @@
           <p class="p">
             Improvements to Impala support for the Amazon S3 filesystem:
           </p>
+
           <ul class="ul">
             <li class="li">
               <p class="p">
@@ -621,7 +828,9 @@
                 See <a class="xref" href="impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for general information about
                 using Impala with S3.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 A new query option, <code class="ph codeph">S3_SKIP_INSERT_STAGING</code>, lets you
@@ -631,13 +840,18 @@
                 See <a class="xref" href="impala_s3_skip_insert_staging.html#s3_skip_insert_staging">S3_SKIP_INSERT_STAGING Query Option (Impala 2.6 or higher only)</a> for details
                 about this option.
               </p>
+
             </li>
+
           </ul>
+
         </li>
+
         <li class="li">
           <p class="p">
             Performance improvements for the runtime filtering feature:
           </p>
+
           <ul class="ul">
             <li class="li">
               <p class="p">
@@ -646,7 +860,9 @@
                 See <a class="xref" href="impala_runtime_filter_mode.html#runtime_filter_mode">RUNTIME_FILTER_MODE Query Option (Impala 2.5 or higher only)</a> for
                 details about this option.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">RUNTIME_BLOOM_FILTER_SIZE</code> setting is now only used
@@ -655,7 +871,9 @@
                 See <a class="xref" href="impala_runtime_bloom_filter_size.html#runtime_bloom_filter_size">RUNTIME_BLOOM_FILTER_SIZE Query Option (Impala 2.5 or higher only)</a> for
                 details about this option.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 New query options <code class="ph codeph">RUNTIME_FILTER_MIN_SIZE</code> and
@@ -669,24 +887,32 @@
                 and <a class="xref" href="impala_runtime_filter_max_size.html#runtime_filter_max_size">RUNTIME_FILTER_MAX_SIZE Query Option (Impala 2.6 or higher only)</a>
                 for details about these options.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Runtime filter propagation now applies to all the
                 operands of <code class="ph codeph">UNION</code> and <code class="ph codeph">UNION ALL</code>
                 operators.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Runtime filters can now be produced during join queries even
                 when the join processing activates the spill-to-disk mechanism.
               </p>
+
             </li>
+
           </ul>
+
             See <a class="xref" href="impala_runtime_filtering.html#runtime_filtering">Runtime Filtering for Impala Queries (Impala 2.5 or higher only)</a> for
             general information about the runtime filtering feature.
         </li>
+
         
         <li class="li">
           <p class="p">
@@ -694,7 +920,9 @@
             See <a class="xref" href="impala_admission.html#admission_control">Admission Control and Query Queuing</a> for details
             about admission control.
           </p>
+
         </li>
+
         
         <li class="li">
           <p class="p">
@@ -703,7 +931,9 @@
             <code class="ph codeph">SET COLUMN STATS</code> clause.
             See <a class="xref" href="impala_perf_stats.html#perf_column_stats_manual">impala_perf_stats.html#perf_column_stats_manual</a> for details.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Impala can now write lightweight <span class="q">"minidump"</span> files, rather
@@ -712,7 +942,9 @@
             open source <code class="ph codeph">breakpad</code> framework.
             See <a class="xref" href="impala_breakpad.html#breakpad">Breakpad Minidumps for Impala (Impala 2.6 or higher only)</a> for details.
           </p>
+
         </li>
+
         <li class="li">
           <div class="p">
             New query options improve interoperability with Parquet files:
@@ -728,7 +960,9 @@
                   See <a class="xref" href="impala_parquet_fallback_schema_resolution.html#parquet_fallback_schema_resolution">PARQUET_FALLBACK_SCHEMA_RESOLUTION Query Option (Impala 2.6 or higher only)</a>
                   for details.
                 </p>
+
               </li>
+
               <li class="li">
                 <p class="p">
                   The <code class="ph codeph">PARQUET_ANNOTATE_STRINGS_UTF8</code> query option
@@ -740,16 +974,22 @@
                   See <a class="xref" href="impala_parquet_annotate_strings_utf8.html#parquet_annotate_strings_utf8">PARQUET_ANNOTATE_STRINGS_UTF8 Query Option (Impala 2.6 or higher only)</a>
                   for details.
                 </p>
+
               </li>
+
             </ul>
+
             See <a class="xref" href="impala_parquet.html#parquet">Using the Parquet File Format with Impala Tables</a> for general information about working
             with Parquet files.
           </div>
+
         </li>
+
         <li class="li">
           <p class="p">
             Improvements to security and reduction in overhead for secure clusters:
           </p>
+
           <ul class="ul">
             <li class="li">
               <p class="p">
@@ -757,7 +997,9 @@
                 (TPC-H queries on a secure cluster were benchmarked
                 at roughly 3x as fast as the previous release.)
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Impala now recognizes the <code class="ph codeph">auth_to_local</code> setting,
@@ -768,14 +1010,18 @@
                 in the <span class="keyword cmdname">impalad</span> configuration settings.
                 See <a class="xref" href="impala_kerberos.html#auth_to_local">Mapping Kerberos Principals to Short Names for Impala</a> for details.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Timing improvements in the mechanism for the <span class="keyword cmdname">impalad</span>
                 daemon to acquire Kerberos tickets. This feature spreads out the overhead
                 on the KDC during Impala startup, especially for large clusters.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 For Kerberized clusters, the Catalog service now uses
@@ -785,9 +1031,13 @@
                 setting to put the OS user into the Sentry administrative group, on clusters where the principal
                 and the OS user name for this user are different.
               </p>
+
             </li>
+
           </ul>
+
         </li>
+
         <li class="li">
           <p class="p">
             Overall performance improvements for join queries, by using a prefetching mechanism
@@ -795,7 +1045,9 @@
             See <a class="xref" href="impala_prefetch_mode.html#prefetch_mode">PREFETCH_MODE Query Option (Impala 2.6 or higher only)</a> for the query option
             to control this optimization.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             The <span class="keyword cmdname">impala-shell</span> interpreter has a new command,
@@ -808,14 +1060,18 @@
             and <a class="xref" href="impala_shell_running_commands.html#shell_running_commands">Running Commands and SQL Statements in impala-shell</a>
             for examples.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             The <code class="ph codeph">millisecond()</code> built-in function lets you extract
             the fractional seconds part of a <code class="ph codeph">TIMESTAMP</code> value.
             See <a class="xref" href="impala_datetime_functions.html#datetime_functions">Impala Date and Time Functions</a> for details.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             If an Avro table is created without column definitions in the
@@ -826,7 +1082,9 @@
             See <a class="xref" href="impala_avro.html#avro">Using the Avro File Format with Impala Tables</a> for general details about
             working with Avro files.
           </p>
+
         </li>
+
         <li class="li">
           <div class="p">
             The mechanism for interpreting <code class="ph codeph">DECIMAL</code> literals is
@@ -839,25 +1097,34 @@
                   <code class="ph codeph">DOUBLE</code> produces a more precise
                   value for the <code class="ph codeph">TIMESTAMP</code> than formerly.
                 </p>
+
               </li>
+
               <li class="li">
                 <p class="p">
                   Certain function calls involving <code class="ph codeph">DECIMAL</code> literals
                   now succeed, when formerly they failed due to lack of a function
                   signature with a <code class="ph codeph">DOUBLE</code> argument.
                 </p>
+
               </li>
+
               <li class="li">
                 <p class="p">
                   Faster runtime performance for <code class="ph codeph">DECIMAL</code> constant
                   values, through improved native code generation for all combinations
                   of precision and scale.
                 </p>
+
               </li>
+
             </ul>
-            See <a class="xref" href="impala_decimal.html#decimal">DECIMAL Data Type (Impala 1.4 or higher only)</a> for details about the <code class="ph codeph">DECIMAL</code> type.
+
+            See <a class="xref" href="impala_decimal.html#decimal">DECIMAL Data Type (Impala 3.0 or higher only)</a> for details about the <code class="ph codeph">DECIMAL</code> type.
           </div>
+
         </li>
+
         <li class="li">
           <p class="p">
             Improved type accuracy for <code class="ph codeph">CASE</code> return values.
@@ -868,26 +1135,34 @@
             See <a class="xref" href="impala_conditional_functions.html#conditional_functions">Impala Conditional Functions</a>
             for details about the <code class="ph codeph">CASE</code> function.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Uncorrelated queries using the <code class="ph codeph">NOT EXISTS</code> operator
             are now supported. Formerly, the <code class="ph codeph">NOT EXISTS</code>
             operator was only available for correlated subqueries.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Improved performance for reading Parquet files.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Improved performance for <dfn class="term">top-N</dfn> queries, that is,
             those including both <code class="ph codeph">ORDER BY</code> and
             <code class="ph codeph">LIMIT</code> clauses.
           </p>
+
         </li>
+
         
         <li class="li">
           <p class="p">
@@ -896,14 +1171,18 @@
             in the <code class="ph codeph">TBLPROPERTIES</code> field of the table metadata.
             See <a class="xref" href="impala_txtfile.html#text_data_files">Data Files for Text Tables</a> for details.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Trailing comments are now allowed in queries processed by
             the <span class="keyword cmdname">impala-shell</span> options <code class="ph codeph">-q</code>
             and <code class="ph codeph">-f</code>.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Impala can run <code class="ph codeph">COUNT</code> queries for RCFile tables
@@ -914,17 +1193,23 @@
             <a class="xref" href="impala_map.html#map">MAP Complex Type (Impala 2.3 or higher only)</a>, and <a class="xref" href="impala_struct.html#struct">STRUCT Complex Type (Impala 2.3 or higher only)</a>
             for syntax details of each type.
           </p>
+
         </li>
+
       </ul>
 
+
     </div>
-  </article>
+
+  </div>
+
+
 
 
+  <div class="topic concept nested1" aria-labelledby="ariaid-title11" id="new_features_250">
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title9" id="new_features__new_features_250">
+    <h2 class="title topictitle2" id="ariaid-title11">New Features in <span class="keyword">Impala 2.5</span></h2>
 
-    <h2 class="title topictitle2" id="ariaid-title9">New Features in <span class="keyword">Impala 2.5</span></h2>
 
     <div class="body conbody">
 
@@ -938,6 +1223,7 @@
             such as <code class="ph codeph">SELECT c1 FROM partitioned_table WHERE year = (SELECT MAX(year) FROM other_table)</code>.
             <span class="ph">See <a class="xref" href="impala_partitioning.html#dynamic_partition_pruning">Dynamic Partition Pruning</a> for details.</span>
           </p>
+
           <p class="p">
             The dynamic partition pruning optimization technique lets Impala avoid reading
             data files from partitions that are not part of the result set, even when
@@ -948,13 +1234,16 @@
             match the <code class="ph codeph">WHERE</code> clause, and only scan the associated partitions
             when evaluating the <code class="ph codeph">ON</code> clause.
           </p>
+
           <p class="p">
             Dynamic partition pruning is controlled by the same settings as the runtime filtering feature.
             By default, this feature is enabled at a medium level, because the maximum setting can use
             slightly more memory for queries than in previous releases.
             To fully enable this feature, set the query option <code class="ph codeph">RUNTIME_FILTER_MODE=GLOBAL</code>.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Runtime filtering. This is a wide-ranging set of optimizations that are especially valuable for join queries.
@@ -965,12 +1254,14 @@
             instead of the full set of values or the entire table.
             <span class="ph">See <a class="xref" href="impala_runtime_filtering.html#runtime_filtering">Runtime Filtering for Impala Queries (Impala 2.5 or higher only)</a> for details.</span>
           </p>
+
           <p class="p">
             By default, this feature is enabled at a medium level, because the maximum setting can use
             slightly more memory for queries than in previous releases.
             To fully enable this feature, set the query option <code class="ph codeph">RUNTIME_FILTER_MODE=GLOBAL</code>.
             <span class="ph">See <a class="xref" href="impala_runtime_filter_mode.html#runtime_filter_mode">RUNTIME_FILTER_MODE Query Option (Impala 2.5 or higher only)</a> for details.</span>
           </p>
+
           <p class="p">
             This feature involves some new query options:
             <a class="xref" href="impala_runtime_filter_mode.html">RUNTIME_FILTER_MODE</a>,
@@ -987,7 +1278,9 @@
             for details.
             </span>
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             More efficient use of the HDFS caching feature, to avoid
@@ -1004,7 +1297,9 @@
             lets you fine-tune the interaction with HDFS caching even more.
             <span class="ph">See <a class="xref" href="impala_perf_hdfs_caching.html#hdfs_caching">Using HDFS Caching with Impala (Impala 2.1 or higher only)</a> for details.</span>
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             The <code class="ph codeph">TRUNCATE TABLE</code> statement now accepts an <code class="ph codeph">IF EXISTS</code>
@@ -1012,7 +1307,9 @@
             might not exist.
             <span class="ph">See <a class="xref" href="impala_truncate_table.html#truncate_table">TRUNCATE TABLE Statement (Impala 2.3 or higher only)</a> for details.</span>
           </p>
+
         </li>
+
         <li class="li">
           <div class="p">
             Improved performance and reliability for the <code class="ph codeph">DECIMAL</code> data type:
@@ -1023,7 +1320,9 @@
                 triggers the native code generation optimization, speeding up queries that
                 group by values such as prices.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Checking for overflow in <code class="ph codeph">DECIMAL</code>
@@ -1031,7 +1330,9 @@
                 a more practical data type in some use cases where formerly <code class="ph codeph">DECIMAL</code>
                 was much slower than <code class="ph codeph">FLOAT</code> or <code class="ph codeph">DOUBLE</code>.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Multiplying a mixture of <code class="ph codeph">DECIMAL</code>
@@ -1040,11 +1341,16 @@
                 some cases where an intermediate value would underflow or overflow and become
                 <code class="ph codeph">NULL</code> unexpectedly.
               </p>
+
             </li>
+
             </ul>
-            <span class="ph">See <a class="xref" href="impala_decimal.html">DECIMAL Data Type (Impala 1.4 or higher only)</a> for details.</span>
+
+            <span class="ph">See <a class="xref" href="impala_decimal.html">DECIMAL Data Type (Impala 3.0 or higher only)</a> for details.</span>
           </div>
+
         </li>
+
         <li class="li">
           <p class="p">
             For UDFs written in Java, or Hive UDFs reused for Impala,
@@ -1053,14 +1359,18 @@
             object types.
             <span class="ph">See <a class="xref" href="impala_udf.html#udfs_hive">Using Hive UDFs with Impala</a> for details.</span>
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Performance improvements for HDFS I/O. Impala now caches HDFS file handles to avoid the
             overhead of repeatedly opening the same file.
           </p>
+
         </li>
 
+
         
         <li class="li">
           <p class="p">
@@ -1068,8 +1378,10 @@
             Certain basic query types, such as counting the elements of a complex column,
             now use an optimized code path.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Improvements to the memory reservation mechanism for the Impala
@@ -1079,8 +1391,10 @@
             default limit for concurrent queries (the <span class="ph uicontrol">max requests</span>
             setting) is now unlimited instead of 200.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Performance improvements related to code generation.
@@ -1090,7 +1404,9 @@
             other parts of the query, such as evaluating
             functions in the <code class="ph codeph">WHERE</code> clause.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Performance improvements for queries using aggregation functions
@@ -1106,7 +1422,9 @@
             using the <code class="ph codeph">DISABLE_STREAMING_PREAGGREGATIONS</code> query option.
             <span class="ph">See <a class="xref" href="impala_disable_streaming_preaggregations.html#disable_streaming_preaggregations">DISABLE_STREAMING_PREAGGREGATIONS Query Option (Impala 2.5 or higher only)</a> for details.</span>
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Spill-to-disk feature now always recommended. In earlier releases, the spill-to-disk feature
@@ -1118,13 +1436,16 @@
             no longer needed or supported. In particular, some new features in <span class="keyword">Impala 2.5</span>
             and higher do not work when the spill-to-disk feature is disabled.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Improvements to scripting capability for the <span class="keyword cmdname">impala-shell</span> command,
             through user-specified substitution variables that can appear in statements processed
             by <span class="keyword cmdname">impala-shell</span>:
           </p>
+
           <ul class="ul">
             <li class="li">
               <p class="p">
@@ -1137,7 +1458,9 @@
                 <code class="ph codeph">impala-shell -f <var class="keyword varname">filename</var></code> command.
                 <span class="ph">See <a class="xref" href="impala_shell_running_commands.html#shell_running_commands">Running Commands and SQL Statements in impala-shell</a> for details.</span>
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 The <code class="ph codeph">SET</code> and <code class="ph codeph">UNSET</code> commands within the
@@ -1153,9 +1476,13 @@
                 <code class="ph codeph">SET</code> statement in a JDBC or ODBC application.
                 <span class="ph">See <a class="xref" href="impala_set.html#set">SET Statement</a> for details.</span>
               </p>
+
             </li>
+
           </ul>
+
         </li>
+
         <li class="li">
           <p class="p">
             Performance improvements for query startup. Impala better parallelizes certain work
@@ -1163,7 +1490,9 @@
             startup time for queries involving tables with many partitions on large clusters,
             or complicated queries with many plan fragments.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Performance and scalability improvements for tables with many partitions.
@@ -1171,7 +1500,9 @@
             faster and less resource-intensive
             to do joins involving several tables with thousands of partitions each.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Whitelisting for access to internal APIs. For applications that need direct access
@@ -1184,20 +1515,27 @@
             Impala-related daemons, although currently it is primarily used for HDFS to control the
             behavior of the catalog server.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Improvements to Impala integration and usability for Hue. (The code changes
             are actually on the Hue side.)
           </p>
+
           <ul class="ul">
           <li class="li">
             <p class="p">
               The list of tables now refreshes dynamically.
             </p>
+
           </li>
+
           </ul>
+
         </li>
+
         <li class="li">
           <p class="p">
             Usability improvements for case-insensitive queries.
@@ -1207,7 +1545,9 @@
             or <code class="ph codeph">LOWER</code>.
             <span class="ph">See <a class="xref" href="impala_operators.html#ilike">ILIKE Operator</a> and <a class="xref" href="impala_operators.html#iregexp">IREGEXP Operator</a> for details.</span>
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Performance and reliability improvements for DDL and insert operations on partitioned tables with a large
@@ -1216,7 +1556,9 @@
             other Impala statements that attempt to modify metadata for the same table wait until the first one
             finishes.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Reliability improvements for the <code class="ph codeph">LOAD DATA</code> statement.
@@ -1224,7 +1566,9 @@
             contained any subdirectories at all. Now, the statement ignores
             any hidden subdirectories, for example <span class="ph filepath">_impala_insert_staging</span>.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             A new operator, <code class="ph codeph">IS [NOT] DISTINCT FROM</code>, lets you compare values
@@ -1235,7 +1579,9 @@
             treat key values that are <code class="ph codeph">NULL</code> in both tables as equal.
             <span class="ph">See <a class="xref" href="impala_operators.html#is_distinct_from">IS DISTINCT FROM Operator</a> for details.</span>
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Security enhancements for the <span class="keyword cmdname">impala-shell</span> command.
@@ -1245,7 +1591,9 @@
             with the LDAP server.
             <span class="ph">See <a class="xref" href="impala_shell_options.html">impala-shell Configuration Options</a> for details.</span>
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             The <code class="ph codeph">CREATE TABLE AS SELECT</code> statement now accepts a
@@ -1253,14 +1601,18 @@
             partitioned table and insert data into it with a single statement.
             <span class="ph">See <a class="xref" href="impala_create_table.html#create_table">CREATE TABLE Statement</a> for details.</span>
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             User-defined functions (UDFs and UDAFs) written in C++ now persist automatically
             when the <span class="keyword cmdname">catalogd</span> daemon is restarted. You no longer
             have to run the <code class="ph codeph">CREATE FUNCTION</code> statements again after a restart.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             User-defined functions (UDFs) written in Java can now persist
@@ -1274,7 +1626,9 @@
             for calling through Impala.
             <span class="ph">See <a class="xref" href="impala_create_function.html#create_function">CREATE FUNCTION Statement</a> for details.</span>
           </p>
+
         </li>
+
         <li class="li">
           
           <p class="p">
@@ -1282,7 +1636,9 @@
             that formerly might have failed with an out-of-memory error due to memory contention,
             now can succeed using the spill-to-disk mechanism.
           </p>
+
         </li>
+
         <li class="li">
           
           <p class="p">
@@ -1292,7 +1648,9 @@
             result set contains only a single column.
             <span class="ph">See <a class="xref" href="impala_show.html#show_databases">SHOW DATABASES</a> for details.</span>
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             A new optimization speeds up aggregation operations that involve only the partition key
@@ -1303,7 +1661,9 @@
             by setting the query option <code class="ph codeph">OPTIMIZE_PARTITION_KEY_SCANS</code>.
             <span class="ph">See <a class="xref" href="impala_optimize_partition_key_scans.html">OPTIMIZE_PARTITION_KEY_SCANS Query Option (Impala 2.5 or higher only)</a> for details.</span>
           </p>
+
         </li>
+
         
         <li class="li">
           <p class="p">
@@ -1311,7 +1671,9 @@
             syntax <code class="ph codeph">DESCRIBE DATABASE <var class="keyword varname">db_name</var></code>.
             <span class="ph">See <a class="xref" href="impala_describe.html#describe">DESCRIBE Statement</a> for details.</span>
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             The <code class="ph codeph">uuid()</code> built-in function generates an
@@ -1320,17 +1682,23 @@
             numeric sequence is not suitable.
             <span class="ph">See <a class="xref" href="impala_misc_functions.html#misc_functions">Impala Miscellaneous Functions</a> for details.</span>
           </p>
+
         </li>
+
       </ul>
 
+
     </div>
-  </article>
+
+  </div>
+
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title10" id="new_features__new_features_240">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title12" id="new_features_240">
+
+    <h2 class="title topictitle2" id="ariaid-title12">New Features in <span class="keyword">Impala 2.4</span></h2>
 
-    <h2 class="title topictitle2" id="ariaid-title10">New Features in <span class="keyword">Impala 2.4</span></h2>
 
     <div class="body conbody">
 
@@ -1340,19 +1708,25 @@
             Impala can be used on the DSSD D5 Storage Appliance.
             From a user perspective, the Impala features are the same as in <span class="keyword">Impala 2.3</span>.
           </p>
+
         </li>
+
       </ul>
 
+
     </div>
-  </article>
+
+  </div>
+
 
 
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title11" id="new_features__new_features_230">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title13" id="new_features_230">
+
+    <h2 class="title topictitle2" id="ariaid-title13">New Features in <span class="keyword">Impala 2.3</span></h2>
 
-    <h2 class="title topictitle2" id="ariaid-title11">New Features in <span class="keyword">Impala 2.3</span></h2>
 
     <div class="body conbody">
 
@@ -1362,6 +1736,7 @@
         manageability, security.
       </p>
 
+
       <ul class="ul">
 
         <li class="li">
@@ -1374,8 +1749,10 @@
             and so on. Currently, complex data types are only supported for the Parquet file format.
             <span class="ph">See <a class="xref" href="impala_complex_types.html#complex_types">Complex Types (Impala 2.3 or higher only)</a> for usage details and <a class="xref" href="impala_array.html#array">ARRAY Complex Type (Impala 2.3 or higher only)</a>, <a class="xref" href="impala_struct.html#struct">STRUCT Complex Type (Impala 2.3 or higher only)</a>, and <a class="xref" href="impala_map.html#map">MAP Complex Type (Impala 2.3 or higher only)</a> for syntax.</span>
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Column-level authorization lets you define access to particular columns within a table,
@@ -1384,15 +1761,19 @@
             See <span class="xref">the documentation for Apache Sentry</span> for background details, and
             <a class="xref" href="impala_grant.html#grant">GRANT Statement (Impala 2.0 or higher only)</a> and <a class="xref" href="impala_revoke.html#revoke">REVOKE Statement (Impala 2.0 or higher only)</a> for Impala-specific syntax.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             The <code class="ph codeph">TRUNCATE TABLE</code> statement removes all the data from a table without removing the table itself.
             <span class="ph">See <a class="xref" href="impala_truncate_table.html#truncate_table">TRUNCATE TABLE Statement (Impala 2.3 or higher only)</a> for details.</span>
           </p>
+
         </li>
 
+
         <li class="li" id="new_features_230__IMPALA-2015">
           <p class="p">
             Nested loop join queries. Some join queries that formerly required equality comparisons can now use
@@ -1400,27 +1781,34 @@
             internally to optimize queries that retrieve values from complex type columns.
             <span class="ph">See <a class="xref" href="impala_joins.html#joins">Joins in Impala SELECT Statements</a> for details about Impala join queries.</span>
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Reduced memory usage and improved performance and robustness for spill-to-disk feature.
             <span class="ph">See <a class="xref" href="impala_scalability.html#spill_to_disk">SQL Operations that Spill to Disk</a> for details about this feature.</span>
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Performance improvements for querying Parquet data files containing multiple row groups
             and multiple data blocks:
           </p>
+
           <ul class="ul">
           <li class="li">
           <p class="p"> For files written by Hive, SparkSQL, and other Parquet MR writers
                 and spanning multiple HDFS blocks, Impala now scans the extra
                 data blocks locally when possible, rather than using remote
                 reads. </p>
+
           </li>
+
           <li class="li">
           <p class="p">
             Impala queries benefit from the improved alignment of row groups with HDFS blocks for Parquet
@@ -1434,197 +1822,254 @@
             Include this setting in the <span class="ph filepath">hive-site</span> configuration file to influence Parquet files written by Hive,
             or the <span class="ph filepath">hdfs-site</span> configuration file to influence Parquet files written by all non-Impala components.
           </p>
+
           </li>
+
           </ul>
+
           <p class="p">
             See <a class="xref" href="impala_parquet.html#parquet">Using the Parquet File Format with Impala Tables</a> for instructions about using Parquet data files
             with Impala.
           </p>
+
         </li>
 
+
         <li class="li" id="new_features_230__IMPALA-1660">
           <p class="p">
             Many new built-in scalar functions, for convenience and enhanced portability of SQL that uses common industry extensions.
           </p>
 
+
           <p class="p">
             Math functions<span class="ph"> (see <a class="xref" href="impala_math_functions.html#math_functions">Impala Mathematical Functions</a> for details)</span>:
           </p>
+
           <ul class="ul">
             <li class="li">
               <code class="ph codeph">ATAN2</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">COSH</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">COT</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">DCEIL</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">DEXP</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">DFLOOR</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">DLOG10</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">DPOW</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">DROUND</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">DSQRT</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">DTRUNC</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">FACTORIAL</code>, and corresponding <code class="ph codeph">!</code> operator
             </li>
 
+
             <li class="li">
               <code class="ph codeph">FPOW</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">RADIANS</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">RANDOM</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">SINH</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">TANH</code>
             </li>
+
           </ul>
 
+
           <p class="p">
             String functions<span class="ph"> (see <a class="xref" href="impala_string_functions.html#string_functions">Impala String Functions</a> for details)</span>:
           </p>
+
           <ul class="ul">
             <li class="li">
               <code class="ph codeph">BTRIM</code>
             </li>
+
             <li class="li">
               <code class="ph codeph">CHR</code>
             </li>
+
             <li class="li">
               <code class="ph codeph">REGEXP_LIKE</code>
             </li>
+
             <li class="li">
               <code class="ph codeph">SPLIT_PART</code>
             </li>
+
           </ul>
 
+
           <p class="p">
             Date and time functions<span class="ph"> (see <a class="xref" href="impala_datetime_functions.html#datetime_functions">Impala Date and Time Functions</a> for details)</span>:
           </p>
+
           <ul class="ul">
               <li class="li">
                 <code class="ph codeph">INT_MONTHS_BETWEEN</code>
               </li>
+
               <li class="li">
                 <code class="ph codeph">MONTHS_BETWEEN</code>
               </li>
+
               <li class="li">
                 <code class="ph codeph">TIMEOFDAY</code>
               </li>
+
               <li class="li">
                 <code class="ph codeph">TIMESTAMP_CMP</code>
               </li>
+
           </ul>
 
+
           <p class="p">
             Bit manipulation functions<span class="ph"> (see <a class="xref" href="impala_bit_functions.html#bit_functions">Impala Bit Functions</a> for details)</span>:
           </p>
+
           <ul class="ul">
             <li class="li">
               <code class="ph codeph">BITAND</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">BITNOT</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">BITOR</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">BITXOR</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">COUNTSET</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">GETBIT</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">ROTATELEFT</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">ROTATERIGHT</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">SETBIT</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">SHIFTLEFT</code>
             </li>
 
+
             <li class="li">
               <code class="ph codeph">SHIFTRIGHT</code>
             </li>
+
           </ul>
+
           <p class="p">
             Type conversion functions<span class="ph"> (see <a class="xref" href="impala_conversion_functions.html#conversion_functions">Impala Type Conversion Functions</a> for details)</span>:
           </p>
+
           <ul class="ul">
             <li class="li">
               <code class="ph codeph">TYPEOF</code>
             </li>
+
           </ul>
+
           <p class="p">
             The <code class="ph codeph">effective_user()</code> function<span class="ph"> (see <a class="xref" href="impala_misc_functions.html#misc_functions">Impala Miscellaneous Functions</a> for details)</span>.
           </p>
+
         </li>
 
+
         <li class="li" id="new_features_230__IMPALA-2081">
           <p class="p">
             New built-in analytic functions: <code class="ph codeph">PERCENT_RANK</code>, <code class="ph codeph">NTILE</code>,
             <code class="ph codeph">CUME_DIST</code>.
             <span class="ph">See <a class="xref" href="impala_analytic_functions.html#analytic_functions">Impala Analytic Functions</a> for details.</span>
           </p>
+
         </li>
 
+
         <li class="li" id="new_features_230__IMPALA-595">
           <p class="p">
             The <code class="ph codeph">DROP DATABASE</code> statement now works for a non-empty database.
@@ -1632,8 +2077,10 @@
             database are dropped before the database itself is removed.
             <span class="ph">See <a class="xref" href="impala_drop_database.html#drop_database">DROP DATABASE Statement</a> for details.</span>
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             The <code class="ph codeph">DROP TABLE</code> and <code class="ph codeph">ALTER TABLE DROP PARTITION</code> statements have a new optional keyword, <code class="ph codeph">PURGE</code>.
@@ -1643,8 +2090,10 @@
             than the data files.
             <span class="ph">See <a class="xref" href="impala_drop_table.html#drop_table">DROP TABLE Statement</a> and <a class="xref" href="impala_alter_table.html#alter_table">ALTER TABLE Statement</a> for syntax.</span>
           </p>
+
         </li>
 
+
         <li class="li" id="new_features_230__IMPALA-80">
           <p class="p">
             The <span class="keyword cmdname">impala-shell</span> command has a new feature for live progress reporting. This feature
@@ -1653,37 +2102,47 @@
             <code class="ph codeph">LIVE_PROGRESS</code> query options.
             <span class="ph">See <a class="xref" href="impala_live_progress.html#live_progress">LIVE_PROGRESS Query Option (Impala 2.3 or higher only)</a> and <a class="xref" href="impala_live_summary.html#live_summary">LIVE_SUMMARY Query Option (Impala 2.3 or higher only)</a> for details.</span>
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             The <span class="keyword cmdname">impala-shell</span> command also now displays a random <span class="q">"tip of the day"</span> when it starts.
           </p>
+
         </li>
 
+
         <li class="li" id="new_features_230__IMPALA-1413">
           <p class="p">
             The <span class="keyword cmdname">impala-shell</span> option <code class="ph codeph">-f</code> now recognizes a special filename
             <code class="ph codeph">-</code> to accept input from stdin.
             <span class="ph">See <a class="xref" href="impala_shell_options.html#shell_options">impala-shell Configuration Options</a> for details about the options for running <span class="keyword cmdname">impala-shell</span> in non-interactive mode.</span>
           </p>
+
         </li>
 
+
         <li class="li" id="new_features_230__IMPALA-1963">
           <p class="p">
             Format strings for the <code class="ph codeph">unix_timestamp()</code> function can now include numeric timezone offsets.
             <span class="ph">See <a class="xref" href="impala_datetime_functions.html#datetime_functions">Impala Date and Time Functions</a> for details.</span>
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Impala can now run a specified command to obtain the password to decrypt a private-key PEM file,
             rather than having the private-key file be unencrypted on disk.
             <span class="ph">See <a class="xref" href="impala_ssl.html#ssl">Configuring TLS/SSL for Impala</a> for details.</span>
           </p>
+
         </li>
 
+
         <li class="li" id="new_features_230__IMPALA-859">
           <p class="p">
             Impala components now can use SSL for more of their internal communication. SSL is used for
@@ -1692,22 +2151,28 @@
             applications when the configuration option <code class="ph codeph">ssl_client_ca_certificate</code> is enabled.
             <span class="ph">See <a class="xref" href="impala_ssl.html#ssl">Configuring TLS/SSL for Impala</a> for details.</span>
           </p>
+
           <p class="p">
             Currently, you can only use one of server-to-server TLS/SSL encryption or Kerberos authentication.
             This limitation is tracked by the issue
             <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2598" target="_blank">IMPALA-2598</a>.
           </p>
+
         </li>
 
+
         <li class="li" id="new_features_230__IMPALA-1829">
           <p class="p">
             Improved flexibility for intermediate data types in user-defined aggregate functions (UDAFs).
             <span class="ph">See <a class="xref" href="impala_udf.html#udafs">Writing User-Defined Aggregate Functions (UDAFs)</a> for details.</span>
           </p>
+
         </li>
 
+
       </ul>
 
+
       <p class="p">
         In <span class="keyword">Impala 2.3.2</span>, the bug fix for <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-2598" target="_blank">IMPALA-2598</a>
         removes the restriction on using both Kerberos and SSL for internal communication between Impala components.
@@ -1715,15 +2180,19 @@
 
 
 
+
     </div>
 
-  </article>
+
+  </div>
+
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title12" id="new_features__new_features_220">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title14" id="new_features_220">
+
+    <h2 class="title topictitle2" id="ariaid-title14">New Features in <span class="keyword">Impala 2.8</span></h2>
 
-    <h2 class="title topictitle2" id="ariaid-title12">New Features in <span class="keyword">Impala 2.8</span></h2>
 
     <div class="body conbody">
 
@@ -1732,6 +2201,7 @@
         contains improvements to performance, manageability, security, and SQL syntax.
       </p>
 
+
       <ul class="ul">
         <li class="li">
           <p class="p">
@@ -1739,6 +2209,7 @@
             database systems, provide more flexibility for handling time zones, and future-proof the handling of
             <code class="ph codeph">TIMESTAMP</code> values:
           </p>
+
           <ul class="ul">
             <li class="li">
               <p class="p">
@@ -1749,7 +2220,9 @@
                 processes each cached block. Increasing the replication factor lets Impala choose
                 different hosts to process different cached blocks, to better distribute the CPU load.
               </p>
+
             </li>
+
             <li class="li">
               <p class="p">
                 Startup flags for the <span class="keyword cmdname">impalad</span> daemon enable a higher level of compatibility with
@@ -1760,6 +2233,7 @@
                 <code class="ph codeph">-convert_legacy_hive_parquet_utc_timestamps=true</code>.
               </p>
 
+
               <p class="p">
                 The <code class="ph codeph">-use_local_tz_for_unix_timestamp_conversions</code> setting controls how the
                 <code class="ph codeph">unix_timestamp()</code>, <code class="ph codeph">from_unixtime()</code>, and <code class="ph codeph">now()</code>
@@ -1771,6 +2245,7 @@
                 inconsistent results depending on which host reads or writes <code class="ph codeph">TIMESTAMP</code> data.
               </p>
 
+
               <p class="p">
                 The <code class="ph codeph">-convert_legacy_hive_parquet_utc_timestamps</code> setting causes Impala to convert
                 <code class="ph codeph">TIMESTAMP</code> values to the local time zone when it reads them from Parquet files
@@ -1780,54 +2255,69 @@
                 automatically handle that new <code class="ph codeph">TIMESTAMP</code> encoding.
               </p>
 
+
               <p class="p">
                 See <a class="xref" href="impala_timestamp.html#timestamp">TIMESTAMP Data Type</a> for details about time zone handling and the
                 configuration options for Impala / Hive compatibility with Parquet format.
               </p>
+
             </li>
 
+
             <li class="li">
-              <p class="p">
-        In Impala 2.2.0 and higher, built-in functions that accept or return integers representing <code class="ph codeph">TIMESTAMP</code> values
-        use the <code class="ph codeph">BIGINT</code> type for parameters and return values, rather than <code class="ph codeph">INT</code>.
-        This change lets the date and time functions avoid an overflow error that would otherwise occur
-        on January 19th, 2038 (known as the
-        <a class="xref" href="http://en.wikipedia.org/wiki/Year_2038_problem" target="_blank"><span class="q">"Year 2038 problem"</span> or <span class="q">"Y2K38 problem"</span></a>).
-        This change affects the <code class="ph codeph">from_unixtime()</code> and <code class="ph codeph">unix_timestamp()</code> functions.
-        You might need to change application code that interacts with these functions, change the types of
-        columns that store the return values, or add <code class="ph codeph">CAST()</code> calls to SQL statements that
-        call these functions.
-      </p>
+              <p class="p"> In Impala 2.2.0 and higher, built-in functions
+        that accept or return integers representing <code class="ph codeph">TIMESTAMP</code>
+        values use the <code class="ph codeph">BIGINT</code> type for parameters and return
+        values, rather than <code class="ph codeph">INT</code>. This change lets the date and
+        time functions avoid an overflow error that would otherwise occur on
+        January 19th, 2038 (known as the <a class="xref" href="http://en.wikipedia.org/wiki/Year_2038_problem" target="_blank"><span class="q">"Year 2038 problem"</span> or <span class="q">"Y2K38
+        problem"</span></a>). This change affects the
+          <code class="ph codeph">FROM_UNIXTIME()</code> and <code class="ph codeph">UNIX_TIMESTAMP()</code>
+        functions. You might need to change application code that interacts with
+        these functions, change the types of columns that store the return
+        values, or add <code class="ph codeph">CAST()</code> calls to SQL statements that call
+        these functions. </p>
+
 
               <p class="p">
                 See <a class="xref" href="impala_datetime_functions.html#datetime_functions">Impala Date and Time Functions</a> for the current function
                 signatures.
               </p>
+
             </li>
+
           </ul>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             The <code class="ph codeph">SHOW FILES</code> statement lets you view the names and sizes of the files that make up
             an entire table or a specific partition. See <a class="xref" href="impala_show.html#show_files">SHOW FILES Statement</a> for details.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Impala can now run queries against Parquet data containing columns with complex or nested types, as
             long as the query only refers to columns with scalar types.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Performance improvements for queries that include <code class="ph codeph">IN()</code> operators and involve
             partitioned tables.
           </p>
+
         </li>
 
+
         <li class="li">
 
           <p class="p">
@@ -1839,8 +2329,10 @@
             interval specified in the <code class="ph codeph">logbufsecs</code> setting, every 5 seconds by default. See
             <a class="xref" href="impala_logging.html#logs_rotate">Rotating Impala Logs</a> for details.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Redaction of sensitive data from Impala log files. This feature protects details such as credit card
@@ -1848,8 +2340,10 @@
             and troubleshooting a Hadoop cluster. See <a class="xref" href="impala_logging.html#redaction">Redacting Sensitive Information from Impala Log Files</a> for background
             information for Impala users, and <span class="xref">the documentation for your Apache Hadoop distribution</span> for usage details.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Lineage information is available for data created or queried by Impala. This feature lets you track who
@@ -1858,8 +2352,10 @@
             information for Impala users, <span class="xref">the documentation for your Apache Hadoop distribution</span> for usage details and
             how to interpret the lineage information.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Impala tables and partitions can now be located on the Amazon Simple Storage Service (S3) filesystem,
@@ -1870,14 +2366,18 @@
             table or partition is in S3. See <a class="xref" href="impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details.
           </p>
 
-          <div class="note important note_important"><span class="note__title importanttitle">Important:</span> 
+
+          <div class="note important"><span class="importanttitle">Important:</span>
         <p class="p">
           Impala query support for Amazon S3 is included in <span class="keyword">Impala 2.2</span>, but is
           not supported or recommended for production use in this version.
         </p>
+
       </div>
+
         </li>
 
+
         <li class="li">
         
           <p class="p">
@@ -1886,59 +2386,74 @@
             <span class="xref">the documentation for your Apache Hadoop distribution</span> for details about using HDFS encryption with
             Impala.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Additional arithmetic function <code class="ph codeph">mod()</code>. See
             <a class="xref" href="impala_math_functions.html#math_functions">Impala Mathematical Functions</a> for details.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Flexibility to interpret <code class="ph codeph">TIMESTAMP</code> values using the UTC time zone (the traditional
             Impala behavior) or using the local time zone (for compatibility with <code class="ph codeph">TIMESTAMP</code> values
             produced by Hive).
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Enhanced support for ETL using tools such as Flume. Impala ignores temporary files typically produced
             by these tools (filenames with suffixes <code class="ph codeph">.copying</code> and <code class="ph codeph">.tmp</code>).
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             The CPU requirement for Impala, which had become more restrictive in Impala 2.0.x and 2.1.x, has now
             been relaxed.
           </p>
 
+
           <p class="p">
         The prerequisite for CPU architecture has been relaxed in Impala 2.2.0 and higher. From this release
         onward, Impala works on CPUs that have the SSSE3 instruction set. The SSE4 instruction set is no longer
         required. This relaxed requirement simplifies the upgrade planning from Impala 1.x releases, which also
         worked on SSSE3-enabled processors.
       </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Enhanced support for <code class="ph codeph">CHAR</code> and <code class="ph codeph">VARCHAR</code> types in the <code class="ph codeph">COMPUTE
             STATS</code> statement.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             The amount of memory required during setup for <span class="q">"spill to disk"</span> operations is greatly reduced. This
             enhancement reduces the chance of a memory-intensive join or aggregation query failing with an
             out-of-memory error.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Several new conditional functions provide enhanced compatibility when porting code that uses industry
@@ -1947,8 +2462,10 @@
             <code class="ph codeph">nullvalue()</code>. See <a class="xref" href="impala_conditional_functions.html#conditional_functions">Impala Conditional Functions</a>
             for details.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             The Impala debug web UI now can display a visual representation of the query plan. On the
@@ -1956,20 +2473,26 @@
             <span class="ph uicontrol">Details</span> page includes a <span class="ph uicontrol">Plan</span> tab with a plan diagram that
             you can zoom in or out (using scroll gestures through mouse wheel or trackpad).
           </p>
+
         </li>
+
       </ul>
 
 
 
+
     </div>
 
-  </article>
+
+  </div>
+
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title13" id="new_features__new_features_210">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title15" id="new_features_210">
+
+    <h2 class="title topictitle2" id="ariaid-title15">New Features in <span class="keyword">Impala 2.1</span></h2>
 
-    <h2 class="title topictitle2" id="ariaid-title13">New Features in <span class="keyword">Impala 2.1</span></h2>
 
     <div class="body conbody">
 
@@ -1977,6 +2500,7 @@
         This release contains the following enhancements to query performance and system scalability:
       </p>
 
+
       <ul class="ul">
         <li class="li">
           <p class="p">
@@ -1988,8 +2512,10 @@
             <a class="xref" href="impala_compute_stats.html#compute_stats">COMPUTE STATS Statement</a> and
             <a class="xref" href="impala_perf_stats.html#perf_stats">Table and Column Statistics</a> for details.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             Optimization for small queries lets Impala process queries that process very few rows without the
@@ -1999,33 +2525,43 @@
             <code class="ph codeph">EXEC_SINGLE_NODE_ROWS_THRESHOLD</code> query option. See
             <a class="xref" href="impala_exec_single_node_rows_threshold.html#exec_single_node_rows_threshold">EXEC_SINGLE_NODE_ROWS_THRESHOLD Query Option (Impala 2.1 or higher only)</a> for details.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             An enhancement to the statestore component lets it transmit heartbeat information independently of
             broadcasting metadata updates. This optimization improves reliability of health checking on large
             clusters with many tables and partitions.
           </p>
+
         </li>
 
+
         <li class="li">
           <p class="p">
             The memory requirement for querying gzip-compressed text is reduced. Now Impala decompresses the data
             as it is read, rather than reading the entire gzipped file and decompressing it in memory.
           </p>
+
         </li>
+
       </ul>
 
+
     </div>
 
-  </article>
+
+  </div>
+
 
 
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title14" id="new_features__new_features_200">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title16" id="new_features_200">
+
+    <h2 class="title topictitle2" id="ariaid-title16

<TRUNCATED>