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

[20/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_load_data.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_load_data.html b/docs/build/html/topics/impala_load_data.html
index 6852faa..2d78675 100644
--- a/docs/build/html/topics/impala_load_data.html
+++ b/docs/build/html/topics/impala_load_data.html
@@ -1,24 +1,44 @@
+<?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_langref_sql.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="load_data"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>LOAD DATA Statement</title></head><body id="load_data"><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="LOAD DATA Statement" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_langref_sql.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="load_data" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>LOAD DATA Statement</title>
+</head>
+<body id="load_data">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">LOAD DATA Statement</h1>
+
   
   
 
   <div class="body conbody">
 
-    <p class="p">
-      
-      The <code class="ph codeph">LOAD DATA</code> statement streamlines the ETL process for an internal Impala table by moving a
-      data file or all the data files in a directory from an HDFS location into the Impala data directory for that
-      table.
-    </p>
+    <p class="p"> The <code class="ph codeph">LOAD DATA</code> statement streamlines the ETL process for
+      an internal Impala table by moving a data file or all the data files in a
+      directory from an HDFS location into the Impala data directory for that
+      table. </p>
+
 
     <p class="p">
         <strong class="ph b">Syntax:</strong>
       </p>
 
+
 <pre class="pre codeblock"><code>LOAD DATA INPATH '<var class="keyword varname">hdfs_file_or_directory_path</var>' [OVERWRITE] INTO TABLE <var class="keyword varname">tablename</var>
   [PARTITION (<var class="keyword varname">partcol1</var>=<var class="keyword varname">val1</var>, <var class="keyword varname">partcol2</var>=<var class="keyword varname">val2</var> ...)]</code></pre>
 
@@ -28,20 +48,24 @@
       and list all the partition key columns, with a constant value specified for each.
     </p>
 
+
     <p class="p">
         <strong class="ph b">Statement type:</strong> DML (but still affected by
         <a class="xref" href="../shared/../topics/impala_sync_ddl.html#sync_ddl">SYNC_DDL</a> query option)
       </p>
 
+
     <p class="p">
         <strong class="ph b">Usage notes:</strong>
       </p>
 
+
     <ul class="ul">
       <li class="li">
         The loaded data files are moved, not copied, into the Impala data directory.
       </li>
 
+
       <li class="li">
         You can specify the HDFS path of a single file to be moved, or the HDFS path of a directory to move all the
         files inside that directory. You cannot specify any sort of wildcard to take only some of the files from a
@@ -49,12 +73,14 @@
         nested directories underneath.
       </li>
 
+
       <li class="li">
         Currently, the Impala <code class="ph codeph">LOAD DATA</code> statement only imports files from HDFS, not from the local
         filesystem. It does not support the <code class="ph codeph">LOCAL</code> keyword of the Hive <code class="ph codeph">LOAD DATA</code>
         statement. You must specify a path, not an <code class="ph codeph">hdfs://</code> URI.
       </li>
 
+
       <li class="li">
         In the interest of speed, only limited error checking is done. If the loaded files have the wrong file
         format, different columns than the destination table, or other kind of mismatch, Impala does not raise any
@@ -63,12 +89,14 @@
         to avoid mixing together uncompressed and LZO-compressed text files in the same table.
       </li>
 
+
       <li class="li">
         When you specify an HDFS directory name as the <code class="ph codeph">LOAD DATA</code> argument, any hidden files in
         that directory (files whose names start with a <code class="ph codeph">.</code>) are not moved to the Impala data
         directory.
       </li>
 
+
       <li class="li">
         The operation fails if the source directory contains any non-hidden directories.
         Prior to <span class="keyword">Impala 2.5</span> if the source directory contained any subdirectory, even a hidden one such as
@@ -77,6 +105,7 @@
         source directory, and only fails if any of the subdirectories are non-hidden.
       </li>
 
+
       <li class="li">
         The loaded data files retain their original names in the new location, unless a name conflicts with an
         existing data file, in which case the name of the new file is modified slightly to be unique. (The
@@ -84,6 +113,7 @@
         identically named files.)
       </li>
 
+
       <li class="li">
         By providing an easy way to transport files from known locations in HDFS into the Impala data directory
         structure, the <code class="ph codeph">LOAD DATA</code> statement lets you avoid memorizing the locations and layout of
@@ -92,6 +122,7 @@
         <var class="keyword varname">table_name</var></code>.)
       </li>
 
+
       <li class="li">
         The <code class="ph codeph">PARTITION</code> clause is especially convenient for ingesting new data for a partitioned
         table. As you receive new data for a time period, geographic region, or other division that corresponds to
@@ -99,12 +130,15 @@
         directory, which might be nested several levels down if the table is partitioned by multiple columns. When
         the table is partitioned, you must specify constant values for all the partitioning columns.
       </li>
+
     </ul>
 
+
     <p class="p">
         <strong class="ph b">Complex type considerations:</strong>
       </p>
 
+
     <p class="p">
       Because Impala currently cannot create Parquet data files containing complex types
       (<code class="ph codeph">ARRAY</code>, <code class="ph codeph">STRUCT</code>, and <code class="ph codeph">MAP</code>), the
@@ -116,6 +150,7 @@
       See <a class="xref" href="impala_complex_types.html#complex_types">Complex Types (Impala 2.3 or higher only)</a> for details about using complex types.
     </p>
 
+
     <p class="p">
         If you connect to different Impala nodes within an <span class="keyword cmdname">impala-shell</span> session for
         load-balancing purposes, you can enable the <code class="ph codeph">SYNC_DDL</code> query option to make each DDL
@@ -123,7 +158,8 @@
         nodes. See <a class="xref" href="../shared/../topics/impala_sync_ddl.html#sync_ddl">SYNC_DDL Query Option</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>
         After adding or replacing data in a table used in performance-critical queries, issue a <code class="ph codeph">COMPUTE
         STATS</code> statement to make sure all statistics are up-to-date. Consider updating statistics for a
         table after any <code class="ph codeph">INSERT</code>, <code class="ph codeph">LOAD DATA</code>, or <code class="ph codeph">CREATE TABLE AS
@@ -132,16 +168,19 @@
         are very large, used in join queries, or both.
       </div>
 
+
     <p class="p">
         <strong class="ph b">Examples:</strong>
       </p>
 
+
     <p class="p">
       First, we use a trivial Python script to write different numbers of strings (one per line) into files stored
       in the <code class="ph codeph">doc_demo</code> HDFS user account. (Substitute the path for your own HDFS user account when
       doing <span class="keyword cmdname">hdfs dfs</span> operations like these.)
     </p>
 
+
 <pre class="pre codeblock"><code>$ random_strings.py 1000 | hdfs dfs -put - /user/doc_demo/thousand_strings.txt
 $ random_strings.py 100 | hdfs dfs -put - /user/doc_demo/hundred_strings.txt
 $ random_strings.py 10 | hdfs dfs -put - /user/doc_demo/ten_strings.txt</code></pre>
@@ -154,6 +193,7 @@ $ random_strings.py 10 | hdfs dfs -put - /user/doc_demo/ten_strings.txt</code></
       into Impala tables that use the corresponding file format.
     </p>
 
+
 <pre class="pre codeblock"><code>[localhost:21000] &gt; create table t1 (s string);
 [localhost:21000] &gt; load data inpath '/user/doc_demo/thousand_strings.txt' into table t1;
 Query finished, fetching results ...
@@ -180,6 +220,7 @@ ERROR: AnalysisException: INPATH location '/user/doc_demo/thousand_strings.txt'
       the destination table, keeping its original filename:
     </p>
 
+
 <pre class="pre codeblock"><code>$ hdfs dfs -ls /user/hive/warehouse/load_data_testing.db/t1
 Found 1 items
 -rw-r--r--   1 doc_demo doc_demo      13926 2013-06-26 15:40 /user/hive/warehouse/load_data_testing.db/t1/thousand_strings.txt</code></pre>
@@ -193,6 +234,7 @@ Found 1 items
       the just-loaded data file.
     </p>
 
+
 <pre class="pre codeblock"><code>[localhost:21000] &gt; load data inpath '/user/doc_demo/hundred_strings.txt' into table t1;
 Query finished, fetching results ...
 +----------------------------------------------------------+
@@ -229,6 +271,7 @@ Returned 1 row(s) in 0.62s</code></pre>
     <p class="p">
         <strong class="ph b">Amazon S3 considerations:</strong>
       </p>
+
     <p class="p">
         In <span class="keyword">Impala 2.6</span> and higher, the Impala DML statements (<code class="ph codeph">INSERT</code>, <code class="ph codeph">LOAD DATA</code>,
         and <code class="ph codeph">CREATE TABLE AS SELECT</code>) can write data into a table or partition that resides in the
@@ -240,6 +283,7 @@ Returned 1 row(s) in 0.62s</code></pre>
         If you bring data into S3 using the normal S3 transfer mechanisms instead of Impala DML statements,
         issue a <code class="ph codeph">REFRESH</code> statement for the table before using Impala to query the S3 data.
       </p>
+
     <p class="p">
         Because of differences between S3 and traditional filesystems, DML operations
         for S3 tables can take longer than for tables on HDFS. For example, both the
@@ -255,31 +299,41 @@ Returned 1 row(s) in 0.62s</code></pre>
         It does not apply to <code class="ph codeph">INSERT OVERWRITE</code> or <code class="ph codeph">LOAD DATA</code> statements.
         See <a class="xref" href="../shared/../topics/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.
       </p>
+
     <p class="p">See <a class="xref" href="impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details about reading and writing S3 data with Impala.</p>
 
+
     <p class="p">
         <strong class="ph b">ADLS considerations:</strong>
       </p>
-    <p class="p">
-        In <span class="keyword">Impala 2.9</span> and higher, the Impala DML statements (<code class="ph codeph">INSERT</code>, <code class="ph codeph">LOAD DATA</code>,
-        and <code class="ph codeph">CREATE TABLE AS SELECT</code>) can write data into a table or partition that resides in the
-        Azure Data Lake Store (ADLS).
-        The syntax of the DML statements is the same as for any other tables, because the ADLS location for tables and
-        partitions is specified by an <code class="ph codeph">adl://</code> prefix in the
-        <code class="ph codeph">LOCATION</code> attribute of
-        <code class="ph codeph">CREATE TABLE</code> or <code class="ph codeph">ALTER TABLE</code> statements.
-        If you bring data into ADLS using the normal ADLS transfer mechanisms instead of Impala DML statements,
-        issue a <code class="ph codeph">REFRESH</code> statement for the table before using Impala to query the ADLS data.
-      </p>
+
+    <p class="p"> In <span class="keyword">Impala 2.9</span> and higher, the Impala DML statements
+          (<code class="ph codeph">INSERT</code>, <code class="ph codeph">LOAD DATA</code>, and
+          <code class="ph codeph">CREATE TABLE AS SELECT</code>) can write data into a table
+        or partition that resides in the Azure Data Lake Store (ADLS). ADLS Gen2
+        is supported in <span class="keyword">Impala 3.1</span> and higher.</p>
+<p class="p">In the<code class="ph codeph">CREATE TABLE</code> or
+          <code class="ph codeph">ALTER TABLE</code> statements, specify the ADLS location for
+        tables and partitions with the <code class="ph codeph">adl://</code> prefix for ADLS
+        Gen1 and <code class="ph codeph">abfs://</code> or <code class="ph codeph">abfss://</code> for ADLS
+        Gen2 in the <code class="ph codeph">LOCATION</code> attribute.</p>
+<p class="p">If you bring data into ADLS
+        using the normal ADLS transfer mechanisms instead of Impala DML
+        statements, issue a <code class="ph codeph">REFRESH</code> statement for the table
+        before using Impala to query the ADLS data. </p>
+
     <p class="p">See <a class="xref" href="impala_adls.html#adls">Using Impala with the Azure Data Lake Store (ADLS)</a> for details about reading and writing ADLS data with Impala.</p>
 
+
     <p class="p">
         <strong class="ph b">Cancellation:</strong> Cannot be cancelled.
       </p>
 
+
     <p class="p">
         <strong class="ph b">HDFS permissions:</strong>
       </p>
+
     <p class="p">
       The user ID that the <span class="keyword cmdname">impalad</span> daemon runs under,
       typically the <code class="ph codeph">impala</code> user, must have read and write
@@ -287,29 +341,36 @@ Returned 1 row(s) in 0.62s</code></pre>
       permission for the destination directory.
     </p>
 
+
     <p class="p">
         <strong class="ph b">Kudu considerations:</strong>
       </p>
+
     <p class="p">
         The <code class="ph codeph">LOAD DATA</code> statement cannot be used with Kudu tables.
       </p>
 
+
     <p class="p">
         <strong class="ph b">HBase considerations:</strong>
       </p>
+
     <p class="p">
         The <code class="ph codeph">LOAD DATA</code> statement cannot be used with HBase tables.
       </p>
 
+
     <p class="p">
         <strong class="ph b">Related information:</strong>
       </p>
+
     <p class="p">
       The <code class="ph codeph">LOAD DATA</code> statement is an alternative to the
       <code class="ph codeph"><a class="xref" href="impala_insert.html#insert">INSERT</a></code> statement.
       Use <code class="ph codeph">LOAD DATA</code>
       when you have the data files in HDFS but outside of any Impala table.
     </p>
+
     <p class="p">
       The <code class="ph codeph">LOAD DATA</code> statement is also an alternative
       to the <code class="ph codeph">CREATE EXTERNAL TABLE</code> statement. Use
@@ -318,5 +379,12 @@ Returned 1 row(s) in 0.62s</code></pre>
       from their original location. See <a class="xref" href="impala_tables.html#external_tables">External Tables</a>
       for information about working with external tables.
     </p>
+
   </div>
-<nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_langref_sql.html">Impala SQL Statements</a></div></div></nav></article></main></body></html>
\ No newline at end of file
+
+<div class="related-links">
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_langref_sql.html">Impala SQL Statements</a></div>
+</div>
+</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_logging.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_logging.html b/docs/build/html/topics/impala_logging.html
index 96a47c7..3fcf552 100644
--- a/docs/build/html/topics/impala_logging.html
+++ b/docs/build/html/topics/impala_logging.html
@@ -1,8 +1,41 @@
+<?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="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="prodname" content="Impala"><meta name="version" content="Impala 2.12x"><meta name="version" content="Impala 2.12x"><meta name="version" content="Impala 2.12x"><meta name="version" content="Impala 2.12x"><meta name="version" content="Impala 2.12x"><meta name="version" content="Impala 2.12x"><meta name="version" content="Impala 2.12x"><meta name="version" content="Impala 2.12x"><meta name="version" content="Impa
 la 2.12x"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="logging"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>Using Impala Logging</title></head><body id="logging"><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 Impala Logging" />
+<meta name="prodname" content="Impala" />
+<meta name="prodname" content="Impala" />
+<meta name="prodname" content="Impala" />
+<meta name="prodname" content="Impala" />
+<meta name="prodname" content="Impala" />
+<meta name="prodname" content="Impala" />
+<meta name="prodname" content="Impala" />
+<meta name="prodname" content="Impala" />
+<meta name="prodname" content="Impala" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<meta name="version" content="Impala 3.0.x" />
+<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="logging" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>Using Impala Logging</title>
+</head>
+<body id="logging">
+
 
   <h1 class="title topictitle1" id="ariaid-title1">Using Impala Logging</h1>
+
   
   
 
@@ -12,22 +45,27 @@
       The Impala logs record information about:
     </p>
 
+
     <ul class="ul">
       <li class="li">
         Any errors Impala encountered. If Impala experienced a serious error during startup, you must diagnose and
         troubleshoot that problem before you can do anything further with Impala.
       </li>
 
+
       <li class="li">
         How Impala is configured.
       </li>
 
+
       <li class="li">
         Jobs Impala has completed.
       </li>
+
     </ul>
 
-    <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">
         Formerly, the logs contained the query profile for each query, showing low-level details of how the work is
         distributed among nodes and how intermediate and final results are transmitted across the network. To save
@@ -38,11 +76,13 @@
         query execution.
       </p>
 
+
       <p class="p">
         The auditing feature introduced in Impala 1.1.1 produces a separate set of audit log files when
         enabled. See <a class="xref" href="impala_auditing.html#auditing">Auditing Impala Operations</a> for details.
       </p>
 
+
       <p class="p">
         In <span class="keyword">Impala 2.9</span> and higher, you can control how many
         audit event log files are kept on each host through the
@@ -51,20 +91,26 @@
         option for regular log files.
       </p>
 
+
       <p class="p">
         The lineage feature introduced in Impala 2.2.0 produces a separate lineage log file when
         enabled. See <a class="xref" href="impala_lineage.html#lineage">Viewing Lineage Information for Impala Data</a> for details.
       </p>
+
     </div>
 
+
     <p class="p toc inpage"></p>
 
+
   </div>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title2" id="logging__logs_details">
+
+  <div class="topic concept nested1" aria-labelledby="ariaid-title2" id="logs_details">
 
     <h2 class="title topictitle2" id="ariaid-title2">Locations and Names of Impala Log Files</h2>
 
+
     <div class="body conbody">
 
       <ul class="ul">
@@ -74,12 +120,14 @@
           <a class="xref" href="impala_processes.html#processes">Starting Impala</a>.
         </li>
 
+
         <li class="li">
           The significant files for the <code class="ph codeph">impalad</code> process are <span class="ph filepath">impalad.INFO</span>,
           <span class="ph filepath">impalad.WARNING</span>, and <span class="ph filepath">impalad.ERROR</span>. You might also see a file
           <span class="ph filepath">impalad.FATAL</span>, although this is only present in rare conditions.
         </li>
 
+
         <li class="li">
           The significant files for the <code class="ph codeph">statestored</code> process are
           <span class="ph filepath">statestored.INFO</span>, <span class="ph filepath">statestored.WARNING</span>, and
@@ -87,27 +135,32 @@
           although this is only present in rare conditions.
         </li>
 
+
         <li class="li">
           The significant files for the <code class="ph codeph">catalogd</code> process are <span class="ph filepath">catalogd.INFO</span>,
           <span class="ph filepath">catalogd.WARNING</span>, and <span class="ph filepath">catalogd.ERROR</span>. You might also see a file
           <span class="ph filepath">catalogd.FATAL</span>, although this is only present in rare conditions.
         </li>
 
+
         <li class="li">
           Examine the <code class="ph codeph">.INFO</code> files to see configuration settings for the processes.
         </li>
 
+
         <li class="li">
           Examine the <code class="ph codeph">.WARNING</code> files to see all kinds of problem information, including such
           things as suboptimal settings and also serious runtime errors.
         </li>
 
+
         <li class="li">
           Examine the <code class="ph codeph">.ERROR</code> and/or <code class="ph codeph">.FATAL</code> files to see only the most serious
           errors, if the processes crash, or queries fail to complete. These messages are also in the
           <code class="ph codeph">.WARNING</code> file.
         </li>
 
+
         <li class="li">
           A new set of log files is produced each time the associated daemon is restarted. These log files have
           long names including a timestamp. The <code class="ph codeph">.INFO</code>, <code class="ph codeph">.WARNING</code>, and
@@ -115,30 +168,36 @@
           files.
         </li>
 
+
         <li class="li">
           The init script for the <code class="ph codeph">impala-server</code> service also produces a consolidated log file
           <code class="ph codeph">/var/logs/impalad/impala-server.log</code>, with all the same information as the
           corresponding<code class="ph codeph">.INFO</code>, <code class="ph codeph">.WARNING</code>, and <code class="ph codeph">.ERROR</code> files.
         </li>
 
+
         <li class="li">
           The init script for the <code class="ph codeph">impala-state-store</code> service also produces a consolidated log file
           <code class="ph codeph">/var/logs/impalad/impala-state-store.log</code>, with all the same information as the
           corresponding<code class="ph codeph">.INFO</code>, <code class="ph codeph">.WARNING</code>, and <code class="ph codeph">.ERROR</code> files.
         </li>
+
       </ul>
 
+
       <p class="p">
         Impala stores information using the <code class="ph codeph">glog_v</code> logging system. You will see some messages
         referring to C++ file names. Logging is affected by:
       </p>
 
+
       <ul class="ul">
         <li class="li">
           The <code class="ph codeph">GLOG_v</code> environment variable specifies which types of messages are logged. See
           <a class="xref" href="#log_levels">Setting Logging Levels</a> for details.
         </li>
 
+
         <li class="li">
           The <code class="ph codeph">--logbuflevel</code> startup flag for the <span class="keyword cmdname">impalad</span> daemon specifies how
           often the log information is written to disk. The default is 0, meaning that the log is immediately
@@ -146,15 +205,20 @@
           important messages such as informational ones are buffered in memory rather than being flushed to disk
           immediately.
         </li>
+
       </ul>
 
+
     </div>
 
-  </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title3" id="logging__logs_managing">
+  </div>
+
+
+  <div class="topic concept nested1" aria-labelledby="ariaid-title3" id="logs_managing">
 
     <h2 class="title topictitle2" id="ariaid-title3">Managing Impala Logs</h2>
+
   
 
     <div class="body conbody">
@@ -163,13 +227,17 @@
         Review Impala log files on each host, when you have traced an issue back to a specific system.
       </p>
 
+
     </div>
 
-  </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title4" id="logging__logs_rotate">
+  </div>
+
+
+  <div class="topic concept nested1" aria-labelledby="ariaid-title4" id="logs_rotate">
 
     <h2 class="title topictitle2" id="ariaid-title4">Rotating Impala Logs</h2>
+
   
 
     <div class="body conbody">
@@ -179,36 +247,73 @@
         to remove the old files if they are no longer needed.
       </p>
 
-      <p class="p">
-        Impala can automatically remove older unneeded log files, a feature known as <dfn class="term">log rotation</dfn>.
 
+      <p class="p">
+        Impala can automatically remove older unneeded log files, a feature
+        known as <dfn class="term">log rotation</dfn>.
       </p>
 
+
+      <div class="p">
+        In Impala 2.2 and higher, the <code class="ph codeph">--max_log_files</code>
+        configuration option specifies how many log files to keep at each
+        severity level (<code class="ph codeph">INFO</code>, <code class="ph codeph">WARNING</code>,
+          <code class="ph codeph">ERROR</code>, and <code class="ph codeph">FATAL</code>). You can specify
+        an appropriate setting for each Impala-related daemon
+          (<span class="keyword cmdname">impalad</span>, <span class="keyword cmdname">statestored</span>, and
+          <span class="keyword cmdname">catalogd</span>).
+        <ul class="ul">
+          <li class="li">
+            A value of 0 preserves all log files, in which case you would set
+            up set up manual log rotation using your Linux tool or technique of
+            choice.
+          </li>
+
+          <li class="li">
+            A value of 1 preserves only the very latest log file.
+          </li>
+
+          <li class="li">
+            The default value is 10.
+          </li>
+
+        </ul>
+
+      </div>
+
       <p class="p">
-        In Impala 2.2 and higher, the <code class="ph codeph">--max_log_files</code> configuration option specifies how many log
-        files to keep at each severity level. You can specify an appropriate setting for each Impala-related daemon
-        (<span class="keyword cmdname">impalad</span>, <span class="keyword cmdname">statestored</span>, and <span class="keyword cmdname">catalogd</span>). The default
-        value is 10, meaning that Impala preserves the latest 10 log files for each severity level
-        (<code class="ph codeph">INFO</code>, <code class="ph codeph">WARNING</code>, <code class="ph codeph">ERROR</code>, and <code class="ph codeph">FATAL</code>).
-        Impala checks to see if any old logs need to be removed based on the interval specified in the
-        <code class="ph codeph">logbufsecs</code> setting, every 5 seconds by default.
+        Impala checks to see if any old logs need to be removed based on the
+        interval specified in the <code class="ph codeph">--logbufsecs</code> setting, every 5
+        seconds by default.
       </p>
 
-
+      <p class="p">
+        For some log levels, Impala logs are first temporarily buffered in
+        memory and only written to disk periodically. The
+          <code class="ph codeph">--logbufsecs</code> setting controls the maximum time that
+        log messages are buffered for. For example, with the default value of 5
+        seconds, there may be up to a 5 second delay before a logged message
+        shows up in the log file.
+      </p>
 
       <p class="p">
-        A value of 0 preserves all log files, in which case you would set up set up manual log rotation using your
-        Linux tool or technique of choice. A value of 1 preserves only the very latest log file.
+        It is not recommended that you set <code class="ph codeph">--logbufsecs</code> to 0
+        as the setting makes the Impala daemon to spin in the thread that tries
+        to delete old log files.
       </p>
 
+
     </div>
 
-  </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title5" id="logging__logs_debug">
+  </div>
+
+
+  <div class="topic concept nested1" aria-labelledby="ariaid-title5" id="logs_debug">
 
     <h2 class="title topictitle2" id="ariaid-title5">Reviewing Impala Logs</h2>
 
+
     <div class="body conbody">
 
       <p class="p">
@@ -220,23 +325,28 @@
         subsets of messages indicating potential problems.)
       </p>
 
+
       <p class="p">
         On a machine named <code class="ph codeph">impala.example.com</code> with default settings, you could view the Impala
         logs on that machine by using a browser to access <code class="ph codeph">http://impala.example.com:25000/logs</code>.
       </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 web interface limits the amount of logging information displayed. To view every log entry, access the
           log files directly through the file system.
         </p>
+
       </div>
 
+
       <p class="p">
         You can view the contents of the <code class="ph codeph">impalad.INFO</code> log file in the file system. With the
         default configuration settings, the start of the log file appears as follows:
       </p>
 
+
 <pre class="pre codeblock"><code>[user@example impalad]$ pwd
 /var/log/impalad
 [user@example impalad]$ more impalad.INFO
@@ -253,19 +363,23 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we
 --classpath=
 --hostname=impala.example.com</code></pre>
 
-      <div class="note note note_note"><span class="note__title notetitle">Note:</span> 
+      <div class="note note"><span class="notetitle">Note:</span>
         The preceding example shows only a small part of the log file. Impala log files are often several megabytes
         in size.
       </div>
 
+
     </div>
 
-  </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title6" id="logging__log_format">
+  </div>
+
+
+  <div class="topic concept nested1" aria-labelledby="ariaid-title6" id="log_format">
 
     <h2 class="title topictitle2" id="ariaid-title6">Understanding Impala Log Contents</h2>
 
+
     <div class="body conbody">
 
       <p class="p">
@@ -273,56 +387,71 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we
         is started and may include:
       </p>
 
+
       <ul class="ul">
         <li class="li">
           Machine name.
         </li>
 
+
         <li class="li">
           Impala version number.
         </li>
 
+
         <li class="li">
           Flags used to start Impala.
         </li>
 
+
         <li class="li">
           CPU information.
         </li>
 
+
         <li class="li">
           The number of available disks.
         </li>
+
       </ul>
 
+
       <p class="p">
         There is information about each job Impala has run. Because each Impala job creates an additional set of
         data about queries, the amount of job specific data may be very large. Logs may contained detailed
         information on jobs. These detailed log entries may include:
       </p>
 
+
       <ul class="ul">
         <li class="li">
           The composition of the query.
         </li>
 
+
         <li class="li">
           The degree of data locality.
         </li>
 
+
         <li class="li">
           Statistics on data throughput and response times.
         </li>
+
       </ul>
 
+
     </div>
 
-  </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title7" id="logging__log_levels">
+  </div>
+
+
+  <div class="topic concept nested1" aria-labelledby="ariaid-title7" id="log_levels">
 
     <h2 class="title topictitle2" id="ariaid-title7">Setting Logging Levels</h2>
 
+
     <div class="body conbody">
 
       <p class="p">
@@ -331,20 +460,23 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we
         similar to the following on each node before starting <code class="ph codeph">impalad</code>:
       </p>
 
+
 <pre class="pre codeblock"><code>export GLOG_v=1</code></pre>
 
-      <div class="note note note_note"><span class="note__title notetitle">Note:</span> 
+      <div class="note note"><span class="notetitle">Note:</span>
         For performance reasons, do not enable the most verbose logging level of 3 unless there is
         no other alternative for troubleshooting.
       </div>
 
+
       <p class="p">
         For more information on how to configure GLOG, including how to set variable logging levels for different
         system components, see
         <a class="xref" href="https://github.com/google/glog" target="_blank">documentation for the glog project on github</a>.
       </p>
 
-      <section class="section" id="log_levels__loglevels_details"><h3 class="title sectiontitle">Understanding What is Logged at Different Logging Levels</h3>
+
+      <div class="section" id="log_levels__loglevels_details"><h3 class="title sectiontitle">Understanding What is Logged at Different Logging Levels</h3>
 
         
 
@@ -353,44 +485,55 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we
           records everything GLOG_v=1 records, as well as additional information.
         </p>
 
+
         <p class="p">
           Increasing logging levels imposes performance overhead and increases log size. Where practical, use
           GLOG_v=1 for most cases: this level has minimal performance impact but still captures useful
           troubleshooting information.
         </p>
 
+
         <p class="p">
           Additional information logged at each level is as follows:
         </p>
 
+
         <ul class="ul">
           <li class="li">
             GLOG_v=1 - The default level. Logs information about each connection and query that is initiated to an
             <code class="ph codeph">impalad</code> instance, including runtime profiles.
           </li>
 
+
           <li class="li">
             GLOG_v=2 - Everything from the previous level plus information for each RPC initiated. This level also
             records query execution progress information, including details on each file that is read.
           </li>
 
+
           <li class="li">
             GLOG_v=3 - Everything from the previous level plus logging of every row that is read. This level is
             only applicable for the most serious troubleshooting and tuning scenarios, because it can produce
             exceptionally large and detailed log files, potentially leading to its own set of performance and
             capacity problems.
           </li>
+
         </ul>
 
-      </section>
+
+      </div>
+
 
     </div>
 
-  </article>
 
-  <article class="topic concept nested1" aria-labelledby="ariaid-title8" id="logging__redaction">
+  </div>
+
+
+  <div class="topic concept nested1" aria-labelledby="ariaid-title8" id="redaction">
 
     <h2 class="title topictitle2" id="ariaid-title8">Redacting Sensitive Information from Impala Log Files</h2>
+
     
 
     <div class="body conbody">
@@ -404,6 +547,7 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we
         they would normally be recorded in log files or displayed in administration or debugging user interfaces.
       </p>
 
+
       <p class="p">
         In a security context, the log redaction feature is complementary to the Sentry authorization framework.
         Sentry prevents unauthorized users from being able to directly access table data. Redaction prevents
@@ -411,13 +555,18 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we
         information (PII) that might appear in queries issued by those authorized users.
       </p>
 
+
       <p class="p">
         See <span class="xref">the documentation for your Apache Hadoop distribution</span> for details about how to enable this feature and set
         up the regular expressions to detect and redact sensitive information within SQL statement text.
       </p>
 
+
     </div>
 
-  </article>
 
-</article></main></body></html>
\ No newline at end of file
+  </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_map.html
----------------------------------------------------------------------
diff --git a/docs/build/html/topics/impala_map.html b/docs/build/html/topics/impala_map.html
index 0d094f4..654bd6d 100644
--- a/docs/build/html/topics/impala_map.html
+++ b/docs/build/html/topics/impala_map.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_datatypes.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="map"><link rel="stylesheet" type="text/css" href="../commonltr.css"><title>MAP Complex Type (Impala 2.3 or higher only)</title></head><body id="map"><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="MAP Complex Type (Impala 2.3 or higher only)" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_datatypes.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="map" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>MAP Complex Type (Impala 2.3 or higher only)</title>
+</head>
+<body id="map">
+
 
     <h1 class="title topictitle1" id="ariaid-title1">MAP Complex Type (<span class="keyword">Impala 2.3</span> or higher only)</h1>
 
+
     
 
     <div class="body conbody">
@@ -15,10 +35,12 @@
         or <code class="ph codeph">MAP</code>).
       </p>
 
+
       <p class="p">
         <strong class="ph b">Syntax:</strong>
       </p>
 
+
 <pre class="pre codeblock"><code><var class="keyword varname">column_name</var> MAP &lt; <var class="keyword varname">primitive_type</var>, <var class="keyword varname">type</var> &gt;
 
 type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword varname">complex_type</var>
@@ -28,6 +50,7 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
         <strong class="ph b">Usage notes:</strong>
       </p>
 
+
       <p class="p">
         Because complex types are often used in combination,
         for example an <code class="ph codeph">ARRAY</code> of <code class="ph codeph">STRUCT</code>
@@ -36,6 +59,7 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
         background information and usage examples.
       </p>
 
+
       <p class="p">
         The <code class="ph codeph">MAP</code> complex data type represents a set of key-value pairs.
         Each element of the map is indexed by a primitive type such as <code class="ph codeph">BIGINT</code> or
@@ -44,6 +68,7 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
         Python dictionary or Java HashMap, where a single scalar value serves as the lookup key.
       </p>
 
+
       <p class="p">
         In a big data context, the keys in a map column might represent a numeric sequence of events during a
         manufacturing process, or <code class="ph codeph">TIMESTAMP</code> values corresponding to sensor observations.
@@ -51,7 +76,8 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
         (such as a recorded <code class="ph codeph">TIMESTAMP</code>) or synthetic (such as a random global universal ID).
       </p>
 
-      <div class="note note note_note"><span class="note__title notetitle">Note:</span> 
+
+      <div class="note note"><span class="notetitle">Note:</span>
         Behind the scenes, the <code class="ph codeph">MAP</code> type is implemented in a similar way as the
         <code class="ph codeph">ARRAY</code> type. Impala does not enforce any uniqueness constraint on the
         <code class="ph codeph">KEY</code> values, and the <code class="ph codeph">KEY</code> values are processed by
@@ -60,6 +86,7 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
         algorithms from non-SQL contexts, rather than optimizing the performance of key lookups.
       </div>
 
+
       <p class="p">
         You can pass a multi-part qualified name to <code class="ph codeph">DESCRIBE</code>
         to specify an <code class="ph codeph">ARRAY</code>, <code class="ph codeph">STRUCT</code>, or <code class="ph codeph">MAP</code>
@@ -77,57 +104,74 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
         <code class="ph codeph">KEY</code> and <code class="ph codeph">VALUE</code> columns.
       </p>
 
+
       <p class="p">
         <strong class="ph b">Added in:</strong> <span class="keyword">Impala 2.3.0</span>
       </p>
 
+
       <p class="p">
         <strong class="ph b">Restrictions:</strong>
       </p>
 
+
       <ul class="ul">
         <li class="li">
           <p class="p">
             Columns with this data type can only be used in tables or partitions with the Parquet file format.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             Columns with this data type cannot be used as partition key columns in a partitioned table.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             The <code class="ph codeph">COMPUTE STATS</code> statement does not produce any statistics for columns of this data type.
           </p>
+
         </li>
+
         <li class="li">
-          <p class="p" id="map__d6e3246">
+          <p class="p" id="map__d6e3270">
             The maximum length of the column definition for any complex type, including declarations for any nested types,
             is 4000 characters.
           </p>
+
         </li>
+
         <li class="li">
           <p class="p">
             See <a class="xref" href="../shared/../topics/impala_complex_types.html#complex_types_limits">Limitations and Restrictions for Complex Types</a> for a full list of limitations
             and associated guidelines about complex type columns.
           </p>
+
         </li>
+
       </ul>
 
+
       <p class="p">
         <strong class="ph b">Kudu considerations:</strong>
       </p>
+
       <p class="p">
         Currently, the data types <code class="ph codeph">CHAR</code>, <code class="ph codeph">VARCHAR</code>,
         <code class="ph codeph">ARRAY</code>, <code class="ph codeph">MAP</code>, and <code class="ph codeph">STRUCT</code> cannot be used with Kudu tables.
       </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>
       Many of the complex type examples refer to tables
       such as <code class="ph codeph">CUSTOMER</code> and <code class="ph codeph">REGION</code>
       adapted from the tables used in the TPC-H benchmark.
@@ -135,6 +179,7 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
       for the table definitions.
       </div>
 
+
       <p class="p">
         The following example shows a table with various kinds of <code class="ph codeph">MAP</code> columns,
         both at the top level and nested within other complex types.
@@ -147,6 +192,7 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
         using empty tables, until you can visualize a complex data structure and construct corresponding SQL statements reliably.
       </p>
 
+
 <pre class="pre codeblock"><code>create TABLE map_demo
 (
   country_id BIGINT,
@@ -280,6 +326,7 @@ DESCRIBE map_demo.mountains.item.facts;
         numeric or character-based keys without worrying about exceeding any size or length constraints.
       </p>
 
+
 <pre class="pre codeblock"><code>CREATE TABLE map_demo_obscure
 (
   id BIGINT,
@@ -319,6 +366,7 @@ CREATE TABLE airlines (name STRING, special_meals MAP &lt; STRING, MAP &lt; STRI
         <strong class="ph b">Related information:</strong>
       </p>
 
+
       <p class="p">
         <a class="xref" href="impala_complex_types.html#complex_types">Complex Types (Impala 2.3 or higher only)</a>,
         <a class="xref" href="impala_array.html#array">ARRAY Complex Type (Impala 2.3 or higher only)</a>,
@@ -326,6 +374,13 @@ CREATE TABLE airlines (name STRING, special_meals MAP &lt; STRING, MAP &lt; STRI
         
       </p>
 
+
     </div>
 
-  <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_datatypes.html">Data Types</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_datatypes.html">Data Types</a></div>
+</div>
+</div></body>
+</html>
\ No newline at end of file