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:44 UTC

[18/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_max.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_max.html b/docs/build/html/topics/impala_max.html
index db7f877..ec010fc 100644
--- a/docs/build/html/topics/impala_max.html
+++ b/docs/build/html/topics/impala_max.html
@@ -1,8 +1,28 @@
+<?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_aggregate_functions.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="max"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>MAX Function</title></head><body id="max"><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="MAX Function" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_aggregate_functions.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="max" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>MAX Function</title>
+</head>
+<body id="max">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">MAX Function</h1>
+
   
   
 
@@ -17,10 +37,12 @@
       <code class="ph codeph">NULL</code>, <code class="ph codeph">MAX</code> returns <code class="ph codeph">NULL</code>.
     </p>
 
+
     <p class="p">
         <strong class="ph b">Syntax:</strong>
       </p>
 
+
 <pre class="pre codeblock"><code>MAX([DISTINCT | ALL] <var class="keyword varname">expression</var>) [OVER (<var class="keyword varname">analytic_clause</var>)]</code></pre>
 
     <p class="p">
@@ -28,21 +50,25 @@
       grouping values.
     </p>
 
+
     <p class="p">
         <strong class="ph b">Restrictions:</strong> In Impala 2.0 and higher, this function can be used as an analytic function, but with restrictions on any window clause.
         For <code class="ph codeph">MAX()</code> and <code class="ph codeph">MIN()</code>, the window clause is only allowed if the start
         bound is <code class="ph codeph">UNBOUNDED PRECEDING</code>.
       </p>
 
+
     <p class="p">
         <strong class="ph b">Return type:</strong> Same as the input value, except for <code class="ph codeph">CHAR</code> and <code class="ph codeph">VARCHAR</code>
         arguments which produce a <code class="ph codeph">STRING</code> result
       </p>
 
+
     <p class="p">
         <strong class="ph b">Usage notes:</strong>
       </p>
 
+
     <p class="p">
         If you frequently run aggregate functions such as <code class="ph codeph">MIN()</code>, <code class="ph codeph">MAX()</code>, and
         <code class="ph codeph">COUNT(DISTINCT)</code> on partition key columns, consider enabling the <code class="ph codeph">OPTIMIZE_PARTITION_KEY_SCANS</code>
@@ -52,10 +78,12 @@
         evaluated when this query option is enabled.
       </p>
 
+
     <p class="p">
         <strong class="ph b">Complex type considerations:</strong>
       </p>
 
+
     <p class="p">
         To access a column with a complex type (<code class="ph codeph">ARRAY</code>, <code class="ph codeph">STRUCT</code>, or <code class="ph codeph">MAP</code>)
         in an aggregation function, you unpack the individual elements using join notation in the query,
@@ -63,6 +91,7 @@
         See <a class="xref" href="../shared/../topics/impala_complex_types.html#complex_types">Complex Types (Impala 2.3 or higher only)</a> for details about using complex types in Impala.
       </p>
 
+
     <div class="p">
 The following example demonstrates calls to several aggregation functions
 using values from a column containing nested complex types
@@ -146,10 +175,12 @@ order by r_name;
 </code></pre>
 </div>
 
+
     <p class="p">
         <strong class="ph b">Examples:</strong>
       </p>
 
+
 <pre class="pre codeblock"><code>-- Find the largest value for this column in the table.
 select max(c1) from t1;
 -- Find the largest value for this column from a subset of the table.
@@ -286,13 +317,22 @@ ERROR: AnalysisException: RANGE is only supported with both the lower and upper
 </code></pre>
     </div>
 
+
     <p class="p">
         <strong class="ph b">Related information:</strong>
       </p>
 
+
     <p class="p">
       <a class="xref" href="impala_analytic_functions.html#analytic_functions">Impala Analytic Functions</a>, <a class="xref" href="impala_min.html#min">MIN Function</a>,
       <a class="xref" href="impala_avg.html#avg">AVG Function</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_aggregate_functions.html">Impala Aggregate Functions</a></div></div></nav></article></main></body></html>
\ No newline at end of file
+
+<div class="related-links">
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_aggregate_functions.html">Impala Aggregate Functions</a></div>
+</div>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/docs/build/html/topics/impala_max_errors.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_max_errors.html b/docs/build/html/topics/impala_max_errors.html
index 632ee9e..c106c64 100644
--- a/docs/build/html/topics/impala_max_errors.html
+++ b/docs/build/html/topics/impala_max_errors.html
@@ -1,8 +1,28 @@
+<?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_query_options.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="max_errors"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>MAX_ERRORS Query Option</title></head><body id="max_errors"><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="MAX_ERRORS Query Option" />
+<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 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="max_errors" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>MAX_ERRORS Query Option</title>
+</head>
+<body id="max_errors">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">MAX_ERRORS Query Option</h1>
+
   
   
 
@@ -15,26 +35,38 @@
       without all billion errors being logged. Unspecified or 0 indicates the built-in default value of 1000.
     </p>
 
+
     <p class="p">
       This option only controls how many errors are reported. To specify whether Impala continues or halts when it
       encounters such errors, use the <code class="ph codeph">ABORT_ON_ERROR</code> option.
     </p>
 
+
     <p class="p">
       <strong class="ph b">Type:</strong> numeric
     </p>
 
+
     <p class="p">
       <strong class="ph b">Default:</strong> 0 (meaning 1000 errors)
     </p>
 
+
     <p class="p">
         <strong class="ph b">Related information:</strong>
       </p>
+
     <p class="p">
       <a class="xref" href="impala_abort_on_error.html#abort_on_error">ABORT_ON_ERROR Query Option</a>,
       <a class="xref" href="impala_logging.html#logging">Using Impala Logging</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
+
+<div 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>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/docs/build/html/topics/impala_max_io_buffers.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_max_io_buffers.html b/docs/build/html/topics/impala_max_io_buffers.html
deleted file mode 100644
index 2d58393..0000000
--- a/docs/build/html/topics/impala_max_io_buffers.html
+++ /dev/null
@@ -1,23 +0,0 @@
-<!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_query_options.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="max_io_buffers"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>MAX_IO_BUFFERS Query Option</title></head><body id="max_io_buffers"><main role="main"><article role="article" aria-labelledby="ariaid-title1">
-
-  <h1 class="title topictitle1" id="ariaid-title1">MAX_IO_BUFFERS Query Option</h1>
-  
-  
-
-  <div class="body conbody">
-
-    <p class="p">
-      Deprecated query option. Currently has no effect.
-    </p>
-
-    <p class="p">
-      <strong class="ph b">Type:</strong> numeric
-    </p>
-
-    <p class="p">
-      <strong class="ph b">Default:</strong> 0
-    </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/impala/blob/b4ad38a9/docs/build/html/topics/impala_max_mem_estimate_for_admission.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_max_mem_estimate_for_admission.html b/docs/build/html/topics/impala_max_mem_estimate_for_admission.html
new file mode 100644
index 0000000..157fbf3
--- /dev/null
+++ b/docs/build/html/topics/impala_max_mem_estimate_for_admission.html
@@ -0,0 +1,103 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+  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="MAX_MEM_ESTIMATE_FOR_ADMISSION Query Option" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_query_options.html" />
+<meta name="prodname" content="Impala" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="max_mem_estimate_for_admission" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>MAX_MEM_ESTIMATE_FOR_ADMISSION Query Option</title>
+</head>
+<body id="max_mem_estimate_for_admission">
+
+
+  <h1 class="title topictitle1" id="ariaid-title1">MAX_MEM_ESTIMATE_FOR_ADMISSION Query Option</h1>
+
+
+
+
+
+
+  <div class="body conbody">
+
+    <p class="p">
+      Use the <code class="ph codeph">MAX_MEM_ESTIMATE_FOR_ADMISSION</code> query option to set an upper limit
+      on the memory estimates of a query as a workaround for over-estimates precluding a query
+      from being admitted.
+    </p>
+
+
+    <p class="p">
+      The query option takes effect when all of the below conditions are met:
+    </p>
+
+
+    <ul class="ul">
+      <li class="li">
+        Memory-based admission control is enabled for the pool.
+      </li>
+
+
+      <li class="li">
+        The <code class="ph codeph">MEM_LIMIT</code> query option is not set at the query, session, resource
+        pool, or global level.
+      </li>
+
+    </ul>
+
+
+    <p class="p">
+      When the above conditions are met, MIN(<code class="ph codeph">MAX_MEM_ESTIMATE_FOR_ADMISSION</code>,
+      mem_estimate) is used for admission control.
+    </p>
+
+
+    <p class="p">
+      Setting the <code class="ph codeph">MEM_LIMIT</code> query option is usually a better option. Use the
+      <code class="ph codeph">MAX_MEM_ESTIMATE_FOR_ADMISSION</code> query option when it is not feasible to
+      set <code class="ph codeph">MEM_LIMIT</code> for each individual query.
+    </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">
+      <strong class="ph b">Added in:</strong> <span class="keyword">Impala 3.1</span>
+    </p>
+
+
+    <p class="p">
+        <strong class="ph b">Usage notes:</strong>
+      </p>
+
+
+    <p class="p">
+        <strong class="ph b">Related information:</strong>
+      </p>
+
+
+  </div>
+
+
+<div 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>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/docs/build/html/topics/impala_max_num_runtime_filters.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_max_num_runtime_filters.html b/docs/build/html/topics/impala_max_num_runtime_filters.html
index c5e0452..5cf7fea 100644
--- a/docs/build/html/topics/impala_max_num_runtime_filters.html
+++ b/docs/build/html/topics/impala_max_num_runtime_filters.html
@@ -1,8 +1,28 @@
+<?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_query_options.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="max_num_runtime_filters"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>MAX_NUM_RUNTIME_FILTERS Query Option (Impala 2.5 or higher only)</title></head><body id="max_num_runtime_filters"><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="MAX_NUM_RUNTIME_FILTERS Query Option (Impala 2.5 or higher only)" />
+<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 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="max_num_runtime_filters" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>MAX_NUM_RUNTIME_FILTERS Query Option (Impala 2.5 or higher only)</title>
+</head>
+<body id="max_num_runtime_filters">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">MAX_NUM_RUNTIME_FILTERS Query Option (<span class="keyword">Impala 2.5</span> or higher only)</h1>
+
   
   
 
@@ -14,22 +34,27 @@
       sets an upper limit on the number of runtime filters that can be produced for each query.
     </p>
 
+
     <p class="p">
         <strong class="ph b">Type:</strong> integer
       </p>
 
+
     <p class="p">
       <strong class="ph b">Default:</strong> 10
     </p>
 
+
     <p class="p">
         <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.5.0</span>
       </p>
 
+
     <p class="p">
         <strong class="ph b">Usage notes:</strong>
       </p>
 
+
     <p class="p">
       Each runtime filter imposes some memory overhead on the query.
       Depending on the setting of the <code class="ph codeph">RUNTIME_BLOOM_FILTER_SIZE</code>
@@ -37,6 +62,7 @@
       per plan fragment. There are typically 5 or fewer filters per plan fragment.
     </p>
 
+
     <p class="p">
       Impala evaluates the effectiveness of each filter, and keeps the
       ones that eliminate the largest number of partitions or rows.
@@ -45,25 +71,30 @@
       while still allowing a high level of optimization for suitable queries.
     </p>
 
+
     <p class="p">
         Because the runtime filtering feature applies mainly to resource-intensive
         and long-running queries, only adjust this query option when tuning long-running queries
         involving some combination of large partitioned tables and joins involving large tables.
       </p>
 
+
     <p class="p">
         <strong class="ph b">Kudu considerations:</strong>
       </p>
 
+
     <p class="p">
         This query option affects only Bloom filters, not the min/max filters
         that are applied to Kudu tables. Therefore, it does not affect the
         performance of queries against Kudu tables.
       </p>
 
+
     <p class="p">
         <strong class="ph b">Related information:</strong>
       </p>
+
     <p class="p">
       <a class="xref" href="impala_runtime_filtering.html">Runtime Filtering for Impala Queries (Impala 2.5 or higher only)</a>,
       
@@ -71,5 +102,12 @@
       <a class="xref" href="impala_runtime_filter_mode.html#runtime_filter_mode">RUNTIME_FILTER_MODE Query Option (Impala 2.5 or higher only)</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
+
+<div 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>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/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
index ebd02e2..3cb5ad8 100644
--- a/docs/build/html/topics/impala_max_row_size.html
+++ b/docs/build/html/topics/impala_max_row_size.html
@@ -1,8 +1,28 @@
+<?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_query_options.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="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">
+  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="MAX_ROW_SIZE Query Option" />
+<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 3.0.x" />
+<meta name="version" content="Impala 3.0.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">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">MAX_ROW_SIZE Query Option</h1>
+
   
   
 
@@ -18,30 +38,37 @@
 
 
 
+
     <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>
@@ -49,15 +76,18 @@
       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
@@ -67,16 +97,19 @@
       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;
 
@@ -103,6 +136,7 @@ insert into big_strings values (repeat('12345',100000), 'short', repeat('12345',
       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;
@@ -149,6 +183,7 @@ select count(*) from big_strings;
       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;
@@ -183,6 +218,7 @@ select count(distinct s1, s2, s3) from big_strings;
       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
@@ -210,6 +246,7 @@ show column stats big_strings;
     <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>,
@@ -217,5 +254,12 @@ show column stats big_strings;
       <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
+
+<div 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>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/docs/build/html/topics/impala_max_scan_range_length.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_max_scan_range_length.html b/docs/build/html/topics/impala_max_scan_range_length.html
index f476f8c..be27e49 100644
--- a/docs/build/html/topics/impala_max_scan_range_length.html
+++ b/docs/build/html/topics/impala_max_scan_range_length.html
@@ -1,8 +1,28 @@
+<?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_query_options.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="max_scan_range_length"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>MAX_SCAN_RANGE_LENGTH Query Option</title></head><body id="max_scan_range_length"><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="MAX_SCAN_RANGE_LENGTH Query Option" />
+<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 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="max_scan_range_length" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>MAX_SCAN_RANGE_LENGTH Query Option</title>
+</head>
+<body id="max_scan_range_length">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">MAX_SCAN_RANGE_LENGTH Query Option</h1>
+
   
   
 
@@ -15,33 +35,46 @@
       range.)
     </p>
 
+
     <p class="p">
       Lowering the value can sometimes increase parallelism if you have unused CPU capacity, but a too-small value
       can limit query performance because each scan range involves extra overhead.
     </p>
 
+
     <p class="p">
       Only applicable to HDFS tables. Has no effect on Parquet tables. Unspecified or 0 indicates backend default,
       which is the same as the HDFS block size for each table.
     </p>
 
+
     <p class="p">
       Although the scan range can be arbitrarily long, Impala internally uses an 8 MB read buffer so that it can
       query tables with huge block sizes without allocating equivalent blocks of memory.
     </p>
 
+
     <p class="p">
       <strong class="ph b">Type:</strong> numeric
     </p>
 
+
     <p class="p">
       In <span class="keyword">Impala 2.7</span> and higher, the argument value can include unit specifiers,
       such as <code class="ph codeph">100m</code> or <code class="ph codeph">100mb</code>. In previous versions,
       Impala interpreted such formatted values as 0, leading to query failures.
     </p>
 
+
     <p class="p">
       <strong class="ph b">Default:</strong> 0
     </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
+
+<div 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>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/docs/build/html/topics/impala_mem_limit.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_mem_limit.html b/docs/build/html/topics/impala_mem_limit.html
index 9143941..4ac8982 100644
--- a/docs/build/html/topics/impala_mem_limit.html
+++ b/docs/build/html/topics/impala_mem_limit.html
@@ -1,19 +1,40 @@
+<?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_query_options.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="mem_limit"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>MEM_LIMIT Query Option</title></head><body id="mem_limit"><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="MEM_LIMIT Query Option" />
+<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 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="mem_limit" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>MEM_LIMIT Query Option</title>
+</head>
+<body id="mem_limit">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">MEM_LIMIT Query Option</h1>
+
   
   
 
   <div class="body conbody">
 
     <p class="p">
-      
-      When resource management is not enabled, defines the maximum amount of memory a query can allocate on each node.
-      Therefore, the total memory that can be used by a query is the <code class="ph codeph">MEM_LIMIT</code> times the number of nodes.
+      The MEM_LIMIT query option defines the maximum amount of memory a query
+      can allocate on each node. The total memory that can be used by a query is
+      the <code class="ph codeph">MEM_LIMIT</code> times the number of nodes.
     </p>
 
+
     <p class="p">
       There are two levels of memory limit for Impala.
       The <code class="ph codeph">-mem_limit</code> startup option sets an overall limit for the <span class="keyword cmdname">impalad</span> process
@@ -25,6 +46,7 @@
       and must always be less than the <span class="keyword cmdname">impalad</span> memory limit.
     </p>
 
+
     <p class="p">
       If query processing exceeds the specified memory limit on any node, either the per-query limit or the
       <span class="keyword cmdname">impalad</span> limit, Impala cancels the query automatically.
@@ -32,39 +54,29 @@
       might briefly exceed the limit without the query being cancelled.
     </p>
 
-    <p class="p">
-      When resource management is enabled, the mechanism for this option changes. If set, it overrides the
-      automatic memory estimate from Impala. Impala requests this amount of memory from YARN on each node, and the
-      query does not proceed until that much memory is available. The actual memory used by the query could be
-      lower, since some queries use much less memory than others. With resource management, the
-      <code class="ph codeph">MEM_LIMIT</code> setting acts both as a hard limit on the amount of memory a query can use on any
-      node (enforced by YARN) and a guarantee that that much memory will be available on each node while the query
-      is being executed. When resource management is enabled but no <code class="ph codeph">MEM_LIMIT</code> setting is
-      specified, Impala estimates the amount of memory needed on each node for each query, requests that much
-      memory from YARN before starting the query, and then internally sets the <code class="ph codeph">MEM_LIMIT</code> on each
-      node to the requested amount of memory during the query. Thus, if the query takes more memory than was
-      originally estimated, Impala detects that the <code class="ph codeph">MEM_LIMIT</code> is exceeded and cancels the query
-      itself.
-    </p>
 
     <p class="p">
       <strong class="ph b">Type:</strong> numeric
     </p>
 
+
     <p class="p">
       <strong class="ph b">Units:</strong> A numeric argument represents memory 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 more commonly <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">Default:</strong> 0 (unlimited)
     </p>
 
+
     <p class="p">
         <strong class="ph b">Usage notes:</strong>
       </p>
 
+
     <p class="p">
       The <code class="ph codeph">MEM_LIMIT</code> setting is primarily useful in a high-concurrency setting,
       or on a cluster with a workload shared between Impala and other data processing components.
@@ -72,6 +84,7 @@
       which could negatively impact other Impala queries.
     </p>
 
+
     <p class="p">
       Use the output of the <code class="ph codeph">SUMMARY</code> command in <span class="keyword cmdname">impala-shell</span>
       to get a report of memory used for each phase of your most heavyweight queries on each node,
@@ -80,15 +93,18 @@
       the <code class="ph codeph">SUMMARY</code> command.
     </p>
 
+
     <p class="p">
         <strong class="ph b">Examples:</strong>
       </p>
 
+
     <p class="p">
       The following examples show how to set the <code class="ph codeph">MEM_LIMIT</code> query option
       using a fixed number of bytes, or suffixes representing gigabytes or megabytes.
     </p>
 
+
 <pre class="pre codeblock"><code>
 [localhost:21000] &gt; set mem_limit=3000000000;
 MEM_LIMIT set to 3000000000
@@ -140,6 +156,7 @@ MEM_LIMIT set to 3mb
       values lead to errors for subsequent queries.
     </p>
 
+
 <pre class="pre codeblock"><code>
 [localhost:21000] &gt; set mem_limit=3tb;
 MEM_LIMIT set to 3tb
@@ -163,6 +180,7 @@ ERROR: Failed to parse query memory limit from 'xyz'.
       setting so that the same query cannot run.
     </p>
 
+
 <pre class="pre codeblock"><code>
 [localhost:21000] &gt; select count(*) from customer;
 Query: select count(*) from customer
@@ -203,4 +221,10 @@ Query did not have enough memory to get the minimum required buffers in the bloc
 </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_query_options.html">Query Options for the SET Statement</a></div></div></nav></article></main></body></html>
\ No newline at end of file
+
+<div 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>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/docs/build/html/topics/impala_min.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_min.html b/docs/build/html/topics/impala_min.html
index 1599bbe..5133536 100644
--- a/docs/build/html/topics/impala_min.html
+++ b/docs/build/html/topics/impala_min.html
@@ -1,8 +1,28 @@
+<?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_aggregate_functions.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="min"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>MIN Function</title></head><body id="min"><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="MIN Function" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_aggregate_functions.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="min" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>MIN Function</title>
+</head>
+<body id="min">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">MIN Function</h1>
+
   
   
 
@@ -17,10 +37,12 @@
       <code class="ph codeph">NULL</code>, <code class="ph codeph">MIN</code> returns <code class="ph codeph">NULL</code>.
     </p>
 
+
     <p class="p">
         <strong class="ph b">Syntax:</strong>
       </p>
 
+
 <pre class="pre codeblock"><code>MIN([DISTINCT | ALL] <var class="keyword varname">expression</var>) [OVER (<var class="keyword varname">analytic_clause</var>)]</code></pre>
 
     <p class="p">
@@ -28,21 +50,25 @@
       grouping values.
     </p>
 
+
     <p class="p">
         <strong class="ph b">Restrictions:</strong> In Impala 2.0 and higher, this function can be used as an analytic function, but with restrictions on any window clause.
         For <code class="ph codeph">MAX()</code> and <code class="ph codeph">MIN()</code>, the window clause is only allowed if the start
         bound is <code class="ph codeph">UNBOUNDED PRECEDING</code>.
       </p>
 
+
     <p class="p">
         <strong class="ph b">Return type:</strong> Same as the input value, except for <code class="ph codeph">CHAR</code> and <code class="ph codeph">VARCHAR</code>
         arguments which produce a <code class="ph codeph">STRING</code> result
       </p>
 
+
     <p class="p">
         <strong class="ph b">Usage notes:</strong>
       </p>
 
+
     <p class="p">
         If you frequently run aggregate functions such as <code class="ph codeph">MIN()</code>, <code class="ph codeph">MAX()</code>, and
         <code class="ph codeph">COUNT(DISTINCT)</code> on partition key columns, consider enabling the <code class="ph codeph">OPTIMIZE_PARTITION_KEY_SCANS</code>
@@ -52,10 +78,12 @@
         evaluated when this query option is enabled.
       </p>
 
+
     <p class="p">
         <strong class="ph b">Complex type considerations:</strong>
       </p>
 
+
     <p class="p">
         To access a column with a complex type (<code class="ph codeph">ARRAY</code>, <code class="ph codeph">STRUCT</code>, or <code class="ph codeph">MAP</code>)
         in an aggregation function, you unpack the individual elements using join notation in the query,
@@ -63,6 +91,7 @@
         See <a class="xref" href="../shared/../topics/impala_complex_types.html#complex_types">Complex Types (Impala 2.3 or higher only)</a> for details about using complex types in Impala.
       </p>
 
+
     <div class="p">
 The following example demonstrates calls to several aggregation functions
 using values from a column containing nested complex types
@@ -146,10 +175,12 @@ order by r_name;
 </code></pre>
 </div>
 
+
     <p class="p">
         <strong class="ph b">Examples:</strong>
       </p>
 
+
 <pre class="pre codeblock"><code>-- Find the smallest value for this column in the table.
 select min(c1) from t1;
 -- Find the smallest value for this column from a subset of the table.
@@ -285,13 +316,22 @@ ERROR: AnalysisException: RANGE is only supported with both the lower and upper
 </code></pre>
     </div>
 
+
     <p class="p">
         <strong class="ph b">Related information:</strong>
       </p>
 
+
     <p class="p">
       <a class="xref" href="impala_analytic_functions.html#analytic_functions">Impala Analytic Functions</a>, <a class="xref" href="impala_max.html#max">MAX Function</a>,
       <a class="xref" href="impala_avg.html#avg">AVG Function</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_aggregate_functions.html">Impala Aggregate Functions</a></div></div></nav></article></main></body></html>
\ No newline at end of file
+
+<div class="related-links">
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_aggregate_functions.html">Impala Aggregate Functions</a></div>
+</div>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/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
index 2d3bc6a..cee1ed5 100644
--- a/docs/build/html/topics/impala_min_spillable_buffer_size.html
+++ b/docs/build/html/topics/impala_min_spillable_buffer_size.html
@@ -1,8 +1,28 @@
+<?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_query_options.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="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">
+  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="MIN_SPILLABLE_BUFFER_SIZE Query Option" />
+<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 3.0.x" />
+<meta name="version" content="Impala 3.0.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">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">MIN_SPILLABLE_BUFFER_SIZE Query Option</h1>
+
   
   
 
@@ -15,37 +35,45 @@
       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.
@@ -53,10 +81,12 @@
       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
@@ -64,10 +94,12 @@
       <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;
 
@@ -76,6 +108,7 @@ set min_spillable_buffer_size=128KB;
     <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>,
@@ -83,5 +116,12 @@ set min_spillable_buffer_size=128KB;
       <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
+
+<div 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>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/docs/build/html/topics/impala_misc_functions.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_misc_functions.html b/docs/build/html/topics/impala_misc_functions.html
index e150467..d0f684a 100644
--- a/docs/build/html/topics/impala_misc_functions.html
+++ b/docs/build/html/topics/impala_misc_functions.html
@@ -1,132 +1,288 @@
+<?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_functions.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="misc_functions"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>Impala Miscellaneous Functions</title></head><body id="misc_functions"><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="Impala Miscellaneous Functions" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_functions.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="misc_functions" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>Impala Miscellaneous Functions</title>
+</head>
+<body id="misc_functions">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">Impala Miscellaneous Functions</h1>
+
+
   
+
   
 
   <div class="body conbody">
 
     <p class="p">
-      Impala supports the following utility functions that do not operate on a particular column or data type:
+      Impala supports the following utility functions that do not operate on a particular column
+      or data type:
     </p>
 
+
+    <ul class="ul">
+      <li class="li">
+        <a class="xref" href="#misc_functions__current_database">CURRENT_DATABASE</a>
+      </li>
+
+
+      <li class="li">
+        <a class="xref" href="#misc_functions__effective_user">EFFECTIVE_USER</a>
+      </li>
+
+
+      <li class="li">
+        <a class="xref" href="#misc_functions__logged_in_user">LOGGED_IN_USER</a>
+      </li>
+
+
+      <li class="li">
+        <a class="xref" href="#misc_functions__pid">PID</a>
+      </li>
+
+
+      <li class="li">
+        <a class="xref" href="#misc_functions__sleep">SLEEP</a>
+      </li>
+
+
+      <li class="li">
+        <a class="xref" href="#misc_functions__user">USER</a>
+      </li>
+
+
+      <li class="li">
+        <a class="xref" href="#misc_functions__uuid">UUID</a>
+      </li>
+
+
+      <li class="li">
+        <a class="xref" href="#misc_functions__version">VERSION</a>
+      </li>
+
+
+      <li class="li">
+        <a class="xref" href="#misc_functions__coordinator">COORDINATOR</a>
+      </li>
+
+    </ul>
+
+
     <dl class="dl">
       
 
         <dt class="dt dlterm" id="misc_functions__current_database">
-          <code class="ph codeph">current_database()</code>
+          CURRENT_DATABASE()
         </dt>
 
+
         <dd class="dd">
-          
-          <strong class="ph b">Purpose:</strong> Returns the database that the session is currently using, either <code class="ph codeph">default</code>
-          if no database has been selected, or whatever database the session switched to through a
-          <code class="ph codeph">USE</code> statement or the <span class="keyword cmdname">impalad</span><code class="ph codeph">-d</code> option.
+          <strong class="ph b">Purpose:</strong> Returns the database that the session is currently using, either
+          <code class="ph codeph">default</code> if no database has been selected, or whatever database the
+          session switched to through a <code class="ph codeph">USE</code> statement or the
+          <span class="keyword cmdname">impalad</span> <code class="ph codeph">-d</code> option.
           <p class="p">
-            <strong class="ph b">Return type:</strong> <code class="ph codeph">string</code>
+            <strong class="ph b">Return type:</strong> <code class="ph codeph">STRING</code>
           </p>
+
         </dd>
 
+
       
 
       
 
         <dt class="dt dlterm" id="misc_functions__effective_user">
-          <code class="ph codeph">effective_user()</code>
+          EFFECTIVE_USER()
         </dt>
 
+
         <dd class="dd">
-          
-          <strong class="ph b">Purpose:</strong> Typically returns the same value as <code class="ph codeph">user()</code>,
-          except if delegation is enabled, in which case it returns the ID of the delegated user.
+          <strong class="ph b">Purpose:</strong> Typically returns the same value as <code class="ph codeph">USER()</code>. If
+          delegation is enabled, it returns the ID of the delegated user.
           <p class="p">
-            <strong class="ph b">Return type:</strong> <code class="ph codeph">string</code>
+            <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.2.5</span>
           </p>
+
+        </dd>
+
+
+
+
+
+
+        <dt class="dt dlterm" id="misc_functions__logged_in_user">
+          LOGGED_IN_USER()
+        </dt>
+
+
+        <dd class="dd">
+          <strong class="ph b">Purpose:</strong> Typically returns the same value as <code class="ph codeph">USER()</code>. If
+          delegation is enabled, it returns the ID of the delegated user.
+          <p class="p">
+            <code class="ph codeph">LOGGED_IN_USER()</code> is an alias of <code class="ph codeph">EFFECTIVE_USER()</code>.
+          </p>
+
+
+          <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 3.1</span>
+          </p>
+
         </dd>
 
+
       
 
       
 
         <dt class="dt dlterm" id="misc_functions__pid">
-          <code class="ph codeph">pid()</code>
+          PID()
         </dt>
 
+
         <dd class="dd">
-          
-          <strong class="ph b">Purpose:</strong> Returns the process ID of the <span class="keyword cmdname">impalad</span> daemon that the session is
-          connected to. You can use it during low-level debugging, to issue Linux commands that trace, show the
-          arguments, and so on the <span class="keyword cmdname">impalad</span> process.
+          <strong class="ph b">Purpose:</strong> Returns the process ID of the <span class="keyword cmdname">impalad</span> daemon that
+          the session is connected to. You can use it during low-level debugging, to issue Linux
+          commands that trace, show the arguments, and so on the <span class="keyword cmdname">impalad</span>
+          process.
           <p class="p">
-            <strong class="ph b">Return type:</strong> <code class="ph codeph">int</code>
+            <strong class="ph b">Return type:</strong> <code class="ph codeph">INT</code>
           </p>
+
         </dd>
 
+
+
+
       
 
+        <dt class="dt dlterm" id="misc_functions__sleep">
+          SLEEP(INT ms)
+        </dt>
+
+
+        <dd class="dd">
+          <strong class="ph b">Purpose:</strong> Pauses the query for a specified number of milliseconds. For slowing
+          down queries with small result sets enough to monitor runtime execution, memory usage,
+          or other factors that otherwise would be difficult to capture during the brief
+          interval of query execution. When used in the <code class="ph codeph">SELECT</code> list, it is
+          called once for each row in the result set; adjust the number of milliseconds
+          accordingly. For example, a query <code class="ph codeph">SELECT *, SLEEP(5) FROM
+          table_with_1000_rows</code> would take at least 5 seconds to complete (5
+          milliseconds * 1000 rows in result set). To avoid an excessive number of concurrent
+          queries, use this function for troubleshooting on test and development systems, not
+          for production queries.
+          <p class="p">
+            <strong class="ph b">Return type:</strong> N/A
+          </p>
+
+        </dd>
+
+
       
 
       
 
         <dt class="dt dlterm" id="misc_functions__user">
-          <code class="ph codeph">user()</code>
+          USER()
         </dt>
 
+
         <dd class="dd">
-          
-          <strong class="ph b">Purpose:</strong> Returns the username of the Linux user who is connected to the <span class="keyword cmdname">impalad</span>
-          daemon. Typically called a single time, in a query without any <code class="ph codeph">FROM</code> clause, to
-          understand how authorization settings apply in a security context; once you know the logged-in username,
-          you can check which groups that user belongs to, and from the list of groups you can check which roles
-          are available to those groups through the authorization policy file.
+          <strong class="ph b">Purpose:</strong> Returns the username of the Linux user who is connected to the
+          <span class="keyword cmdname">impalad</span> daemon. Typically called a single time, in a query without
+          any <code class="ph codeph">FROM</code> clause, to understand how authorization settings apply in a
+          security context; once you know the logged-in username, you can check which groups
+          that user belongs to, and from the list of groups you can check which roles are
+          available to those groups through the authorization policy file.
           <p class="p">
         In Impala 2.0 and later, <code class="ph codeph">user()</code> returns the full Kerberos principal string, such as
         <code class="ph codeph">user@example.com</code>, in a Kerberized environment.
       </p>
+
+
           <p class="p">
-            When delegation is enabled, consider calling the <code class="ph codeph">effective_user()</code> function instead.
+            When delegation is enabled, consider calling the <code class="ph codeph">EFFECTIVE_USER()</code>
+            function instead.
           </p>
+
+
           <p class="p">
-            <strong class="ph b">Return type:</strong> <code class="ph codeph">string</code>
+            <strong class="ph b">Return type:</strong> <code class="ph codeph">STRING</code>
           </p>
+
         </dd>
 
+
       
 
       
 
         <dt class="dt dlterm" id="misc_functions__uuid">
-          <code class="ph codeph">uuid()</code>
+          UUID()
         </dt>
 
+
         <dd class="dd">
-          
-          <strong class="ph b">Purpose:</strong> Returns a <a class="xref" href="https://en.wikipedia.org/wiki/Universally_unique_identifier" target="_blank">universal unique identifier</a>, a 128-bit value encoded as a string with groups of hexadecimal digits separated by dashes.
+          <strong class="ph b">Purpose:</strong> Returns a
+          <a class="xref" href="https://en.wikipedia.org/wiki/Universally_unique_identifier" target="_blank">universal
+          unique identifier</a>, a 128-bit value encoded as a string with groups of
+          hexadecimal digits separated by dashes.
           <p class="p">
-            <strong class="ph b">Return type:</strong> <code class="ph codeph">string</code>
+            <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.5.0</span>
       </p>
+
+
           <p class="p">
         <strong class="ph b">Usage notes:</strong>
       </p>
+
+
           <p class="p">
-            Ascending numeric sequences of type <code class="ph codeph">BIGINT</code> are often used
-            as identifiers within a table, and as join keys across multiple tables.
-            The <code class="ph codeph">uuid()</code> value is a convenient alternative that does not
-            require storing or querying the highest sequence number. For example, you
-            can use it to quickly construct new unique identifiers during a data import job,
-            or to combine data from different tables without the likelihood of ID collisions.
+            Ascending numeric sequences of type <code class="ph codeph">BIGINT</code> are often used as
+            identifiers within a table, and as join keys across multiple tables. The
+            <code class="ph codeph">UUID()</code> value is a convenient alternative that does not require
+            storing or querying the highest sequence number. For example, you can use it to
+            quickly construct new unique identifiers during a data import job, or to combine
+            data from different tables without the likelihood of ID collisions.
           </p>
+
+
           <p class="p">
         <strong class="ph b">Examples:</strong>
       </p>
+
 <pre class="pre codeblock"><code>
 -- Each call to uuid() produces a new arbitrary value.
 select uuid();
@@ -150,26 +306,64 @@ select uuid() from four_row_table;
 </code></pre>
         </dd>
 
+
       
 
       
 
         <dt class="dt dlterm" id="misc_functions__version">
-          <code class="ph codeph">version()</code>
+          VERSION()
+        </dt>
+
+
+        <dd class="dd">
+          <strong class="ph b">Purpose:</strong> Returns information such as the precise version number and build date
+          for the <code class="ph codeph">impalad</code> daemon that you are currently connected to. Typically
+          used to confirm that you are connected to the expected level of Impala to use a
+          particular feature, or to connect to several nodes and confirm they are all running
+          the same level of <span class="keyword cmdname">impalad</span>.
+          <p class="p">
+            <strong class="ph b">Return type:</strong> <code class="ph codeph">STRING</code> (with one or more embedded newlines)
+          </p>
+
+        </dd>
+
+
+
+
+
+
+        <dt class="dt dlterm" id="misc_functions__coordinator">
+          COORDINATOR()
         </dt>
 
+
         <dd class="dd">
-          
-          <strong class="ph b">Purpose:</strong> Returns information such as the precise version number and build date for the
-          <code class="ph codeph">impalad</code> daemon that you are currently connected to. Typically used to confirm that you
-          are connected to the expected level of Impala to use a particular feature, or to connect to several nodes
-          and confirm they are all running the same level of <span class="keyword cmdname">impalad</span>.
+          <strong class="ph b">Purpose:</strong> Returns the name of the host which is running the
+          <code class="ph codeph">impalad</code> daemon that is acting as the <code class="ph codeph">coordinator</code> for
+          the current query.
+          <p class="p">
+            <strong class="ph b">Return type:</strong> <code class="ph codeph">STRING</code>
+          </p>
+
+
           <p class="p">
-            <strong class="ph b">Return type:</strong> <code class="ph codeph">string</code> (with one or more embedded newlines)
+            <strong class="ph b">Added in:</strong> <span class="keyword">Impala 3.1</span>
           </p>
+
         </dd>
 
+
       
     </dl>
+
+
   </div>
-<nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_functions.html">Impala Built-In Functions</a></div></div></nav></article></main></body></html>
\ No newline at end of file
+
+
+<div class="related-links">
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_functions.html">Impala Built-In Functions</a></div>
+</div>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/docs/build/html/topics/impala_mixed_security.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_mixed_security.html b/docs/build/html/topics/impala_mixed_security.html
index 53c309e..0e1ce52 100644
--- a/docs/build/html/topics/impala_mixed_security.html
+++ b/docs/build/html/topics/impala_mixed_security.html
@@ -1,8 +1,28 @@
+<?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_authentication.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="mixed_security"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>Using Multiple Authentication Methods with Impala</title></head><body id="mixed_security"><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="Using Multiple Authentication Methods with Impala" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_authentication.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="mixed_security" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>Using Multiple Authentication Methods with Impala</title>
+</head>
+<body id="mixed_security">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">Using Multiple Authentication Methods with Impala</h1>
+
   
 
   <div class="body conbody">
@@ -13,6 +33,7 @@
       special actions need to be taken if some users authenticate through Kerberos and some through LDAP.
     </p>
 
+
     <p class="p">
       Prior to Impala 2.0, you had to configure each <span class="keyword cmdname">impalad</span> to listen on a specific port
       depending on the kind of authentication, then configure your network load balancer to forward each kind of
@@ -22,5 +43,12 @@
     </p>
 
 
+
   </div>
-<nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_authentication.html">Impala Authentication</a></div></div></nav></article></main></body></html>
\ No newline at end of file
+
+<div class="related-links">
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_authentication.html">Impala Authentication</a></div>
+</div>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/docs/build/html/topics/impala_mt_dop.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_mt_dop.html b/docs/build/html/topics/impala_mt_dop.html
index 42e4166..fd46f13 100644
--- a/docs/build/html/topics/impala_mt_dop.html
+++ b/docs/build/html/topics/impala_mt_dop.html
@@ -1,8 +1,28 @@
+<?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_query_options.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="mt_dop"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>MT_DOP Query Option</title></head><body id="mt_dop"><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="MT_DOP Query Option" />
+<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 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="mt_dop" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>MT_DOP Query Option</title>
+</head>
+<body id="mt_dop">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">MT_DOP Query Option</h1>
+
   
   
 
@@ -16,7 +36,8 @@
       memory usage, and CPU usage during statement processing.
     </p>
 
-    <div class="note note note_note"><span class="note__title notetitle">Note:</span> 
+
+    <div class="note note"><span class="notetitle">Note:</span>
       <p class="p">
         The Impala execution engine is being revamped incrementally to add
         additional parallelism within a single host for certain statements and
@@ -24,10 +45,12 @@
         <span class="q">"old"</span> code path with limited intra-node parallelism.
       </p>
 
+
       <p class="p">
         Currently, the operations affected by the <code class="ph codeph">MT_DOP</code>
         query option are:
       </p>
+
       <ul class="ul">
         <li class="li">
           <p class="p">
@@ -35,7 +58,9 @@
             <code class="ph codeph">MT_DOP=4</code> for <code class="ph codeph">COMPUTE STATS</code> and
             <code class="ph codeph">COMPUTE INCREMENTAL STATS</code> statements on Parquet tables.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Queries with execution plans containing only scan and aggregation operators,
@@ -44,45 +69,57 @@
             value. Therefore, this query option is typically only set for the duration of
             specific long-running, CPU-intensive queries.
           </p>
+
         </li>
+
       </ul>
 
+
     </div>
 
+
     <p class="p">
         <strong class="ph b">Type:</strong> integer
       </p>
+
     <p class="p">
         <strong class="ph b">Default:</strong> <code class="ph codeph">0</code>
       </p>
+
     <p class="p">
       Because <code class="ph codeph">COMPUTE STATS</code> and <code class="ph codeph">COMPUTE INCREMENTAL STATS</code>
       statements for Parquet tables benefit substantially from extra intra-node
       parallelism, Impala automatically sets <code class="ph codeph">MT_DOP=4</code> when computing stats
       for Parquet tables.
     </p>
+
     <p class="p">
       <strong class="ph b">Range:</strong> 0 to 64
     </p>
 
+
     <p class="p">
         <strong class="ph b">Examples:</strong>
       </p>
 
-    <div class="note note note_note"><span class="note__title notetitle">Note:</span> 
+
+    <div class="note note"><span class="notetitle">Note:</span>
       <p class="p">
         Any timing figures in the following examples are on a small, lightly loaded development cluster.
         Your mileage may vary. Speedups depend on many factors, including the number of rows, columns, and
         partitions within each table.
       </p>
+
     </div>
 
+
     <p class="p">
       The following example shows how to run a <code class="ph codeph">COMPUTE STATS</code>
       statement against a Parquet table with or without an explicit <code class="ph codeph">MT_DOP</code>
       setting:
     </p>
 
+
 <pre class="pre codeblock"><code>
 -- Explicitly setting MT_DOP to 0 selects the old code path.
 set mt_dop = 0;
@@ -132,6 +169,7 @@ compute stats billion_rows_parquet;
       for a query involving only scan and aggregation operations for a Parquet table:
     </p>
 
+
 <pre class="pre codeblock"><code>
 set mt_dop = 0;
 MT_DOP set to 0
@@ -167,6 +205,7 @@ Fetched 1 row(s) in 17.19s
       is set:
     </p>
 
+
 <pre class="pre codeblock"><code>
 set mt_dop=1;
 MT_DOP set to 1
@@ -181,10 +220,18 @@ ERROR: NotImplementedException: MT_DOP not supported for plans with
     <p class="p">
         <strong class="ph b">Related information:</strong>
       </p>
+
     <p class="p">
       <a class="xref" href="impala_compute_stats.html">COMPUTE STATS Statement</a>,
       <a class="xref" href="impala_aggregate_functions.html">Impala Aggregate Functions</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
+
+<div 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>
+</div></body>
+</html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/impala/blob/b4ad38a9/docs/build/html/topics/impala_ndv.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_ndv.html b/docs/build/html/topics/impala_ndv.html
index 9cdb2e0..8a4609a 100644
--- a/docs/build/html/topics/impala_ndv.html
+++ b/docs/build/html/topics/impala_ndv.html
@@ -1,8 +1,28 @@
+<?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_aggregate_functions.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="ndv"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>NDV Function</title></head><body id="ndv"><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="NDV Function" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_aggregate_functions.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="ndv" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>NDV Function</title>
+</head>
+<body id="ndv">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">NDV Function</h1>
+
   
   
 
@@ -16,27 +36,32 @@
       thus is less memory-intensive for columns with high cardinality.
     </p>
 
+
     <p class="p">
         <strong class="ph b">Syntax:</strong>
       </p>
 
+
 <pre class="pre codeblock"><code>NDV([DISTINCT | ALL] <var class="keyword varname">expression</var>)</code></pre>
 
     <p class="p">
         <strong class="ph b">Usage notes:</strong>
       </p>
 
+
     <p class="p">
       This is the mechanism used internally by the <code class="ph codeph">COMPUTE STATS</code> statement for computing the
       number of distinct values in a column.
     </p>
 
+
     <p class="p">
       Because this number is an estimate, it might not reflect the precise number of different values in the
       column, especially if the cardinality is very low or very high. If the estimated number is higher than the
       number of rows in the table, Impala adjusts the value internally during query planning.
     </p>
 
+
     <p class="p">
         <strong class="ph b">Return type:</strong> <code class="ph codeph">DOUBLE</code> in Impala 2.0 and higher; <code class="ph codeph">STRING</code> in earlier
         releases
@@ -44,10 +69,12 @@
 
 
 
+
     <p class="p">
         <strong class="ph b">Complex type considerations:</strong>
       </p>
 
+
     <p class="p">
         To access a column with a complex type (<code class="ph codeph">ARRAY</code>, <code class="ph codeph">STRUCT</code>, or <code class="ph codeph">MAP</code>)
         in an aggregation function, you unpack the individual elements using join notation in the query,
@@ -55,6 +82,7 @@
         See <a class="xref" href="../shared/../topics/impala_complex_types.html#complex_types">Complex Types (Impala 2.3 or higher only)</a> for details about using complex types in Impala.
       </p>
 
+
     <div class="p">
 The following example demonstrates calls to several aggregation functions
 using values from a column containing nested complex types
@@ -138,18 +166,22 @@ order by r_name;
 </code></pre>
 </div>
 
+
     <p class="p">
         <strong class="ph b">Restrictions:</strong>
       </p>
 
+
     <p class="p">
         This function cannot be used in an analytic context. That is, the <code class="ph codeph">OVER()</code> clause is not allowed at all with this function.
       </p>
 
+
     <p class="p">
         <strong class="ph b">Examples:</strong>
       </p>
 
+
     <p class="p">
       The following example queries a billion-row table to illustrate the relative performance of
       <code class="ph codeph">COUNT(DISTINCT)</code> and <code class="ph codeph">NDV()</code>. It shows how <code class="ph codeph">COUNT(DISTINCT)</code>
@@ -157,6 +189,7 @@ order by r_name;
       The <code class="ph codeph">NDV()</code> function gives an approximate result but is much faster.
     </p>
 
+
 <pre class="pre codeblock"><code>select count(distinct col1) from sample_data;
 +---------------------+
 | count(distinct col1)|
@@ -180,6 +213,7 @@ Fetched 1 row(s) in 8.91s
       running a sequence of queries with <code class="ph codeph">COUNT(DISTINCT)</code> calls.
     </p>
 
+
 <pre class="pre codeblock"><code>select cast(ndv(col1) as bigint) as col1, cast(ndv(col2) as bigint) as col2,
     cast(ndv(col3) as bigint) as col3, cast(ndv(col4) as bigint) as col4
   from sample_data;
@@ -223,4 +257,10 @@ select count(distinct col4) from sample_data;
 Fetched 1 row(s) in 266.95s
 </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_aggregate_functions.html">Impala Aggregate Functions</a></div></div></nav></article></main></body></html>
\ No newline at end of file
+
+<div class="related-links">
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_aggregate_functions.html">Impala Aggregate Functions</a></div>
+</div>
+</div></body>
+</html>
\ No newline at end of file