You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by jo...@apache.org on 2020/04/24 17:27:44 UTC

[impala] 02/03: [DOCS] Impala 3.4 docs to be published

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

joemcdonnell pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/impala.git

commit 05b84cca5494795c2d4926152603648f3c89a74c
Author: Joe McDonnell <jo...@cloudera.com>
AuthorDate: Fri Apr 17 13:21:35 2020 -0700

    [DOCS] Impala 3.4 docs to be published
    
     - Add docs from Impala branch-3.4.0
     - hash 9f1c31c
    
    Change-Id: I65343187983b1f0f9833055598b4acf256f770da
    Reviewed-on: http://gerrit.cloudera.org:8080/15750
    Reviewed-by: Tim Armstrong <ta...@cloudera.com>
    Tested-by: Joe McDonnell <jo...@cloudera.com>
---
 docs/build/html/index.html                         |    6 +-
 docs/build/html/topics/impala_abort_on_error.html  |    8 +-
 docs/build/html/topics/impala_adls.html            |    6 +-
 docs/build/html/topics/impala_admin.html           |    8 +-
 docs/build/html/topics/impala_admission.html       |    8 +-
 .../build/html/topics/impala_admission_config.html |    6 +-
 .../html/topics/impala_aggregate_functions.html    |    8 +-
 docs/build/html/topics/impala_aliases.html         |    8 +-
 .../topics/impala_allow_erasure_coded_files.html   |    6 +-
 .../topics/impala_allow_unsupported_formats.html   |    8 +-
 docs/build/html/topics/impala_alter_database.html  |    6 +-
 docs/build/html/topics/impala_alter_table.html     |   10 +-
 docs/build/html/topics/impala_alter_view.html      |    8 +-
 .../html/topics/impala_analytic_functions.html     |   42 +-
 .../html/topics/impala_appx_count_distinct.html    |    8 +-
 docs/build/html/topics/impala_appx_median.html     |    8 +-
 docs/build/html/topics/impala_array.html           |   10 +-
 docs/build/html/topics/impala_auditing.html        |   53 +-
 docs/build/html/topics/impala_authentication.html  |    8 +-
 docs/build/html/topics/impala_authorization.html   |  219 ++-
 docs/build/html/topics/impala_avg.html             |    8 +-
 docs/build/html/topics/impala_avro.html            |  197 ++-
 docs/build/html/topics/impala_batch_size.html      |    8 +-
 docs/build/html/topics/impala_bigint.html          |    8 +-
 docs/build/html/topics/impala_bit_functions.html   |    8 +-
 docs/build/html/topics/impala_boolean.html         |    8 +-
 docs/build/html/topics/impala_breakpad.html        |    8 +-
 .../html/topics/impala_broadcast_bytes_limit.html  |   76 +
 .../html/topics/impala_buffer_pool_limit.html      |    8 +-
 docs/build/html/topics/impala_char.html            |    8 +-
 docs/build/html/topics/impala_client.html          |   78 +-
 docs/build/html/topics/impala_comment.html         |    6 +-
 docs/build/html/topics/impala_comments.html        |    8 +-
 docs/build/html/topics/impala_complex_types.html   |    8 +-
 docs/build/html/topics/impala_components.html      |   14 +-
 .../html/topics/impala_compression_codec.html      |    8 +-
 docs/build/html/topics/impala_compute_stats.html   |   10 +-
 .../impala_compute_stats_min_sample_size.html      |    8 +-
 docs/build/html/topics/impala_concepts.html        |    8 +-
 .../html/topics/impala_conditional_functions.html  |    8 +-
 docs/build/html/topics/impala_config.html          |    8 +-
 docs/build/html/topics/impala_config_options.html  |    8 +-
 .../html/topics/impala_config_performance.html     |    8 +-
 docs/build/html/topics/impala_connecting.html      |    8 +-
 .../html/topics/impala_conversion_functions.html   | 1490 +++++++++++++++++++-
 docs/build/html/topics/impala_count.html           |    8 +-
 docs/build/html/topics/impala_create_database.html |   10 +-
 docs/build/html/topics/impala_create_function.html |    8 +-
 docs/build/html/topics/impala_create_role.html     |    8 +-
 docs/build/html/topics/impala_create_table.html    |  151 +-
 docs/build/html/topics/impala_create_view.html     |    8 +-
 .../build/html/topics/impala_custom_timezones.html |    6 +-
 docs/build/html/topics/impala_data_cache.html      |    6 +-
 docs/build/html/topics/impala_databases.html       |    8 +-
 docs/build/html/topics/impala_datatypes.html       |   56 +-
 docs/build/html/topics/impala_date.html            |   74 +-
 .../html/topics/impala_datetime_functions.html     |  500 ++++---
 docs/build/html/topics/impala_ddl.html             |   10 +-
 docs/build/html/topics/impala_debug_action.html    |    8 +-
 docs/build/html/topics/impala_decimal.html         |   54 +-
 docs/build/html/topics/impala_decimal_v2.html      |    6 +-
 .../html/topics/impala_dedicated_coordinator.html  |    8 +-
 .../html/topics/impala_default_file_format.html    |    6 +-
 .../impala_default_hints_insert_statement.html     |    6 +-
 .../impala_default_join_distribution_mode.html     |    8 +-
 .../impala_default_spillable_buffer_size.html      |    8 +-
 .../topics/impala_default_transactional_type.html  |    6 +-
 docs/build/html/topics/impala_delegation.html      |    8 +-
 docs/build/html/topics/impala_delete.html          |    8 +-
 docs/build/html/topics/impala_describe.html        |    8 +-
 docs/build/html/topics/impala_development.html     |    8 +-
 docs/build/html/topics/impala_disable_codegen.html |    8 +-
 .../impala_disable_codegen_rows_threshold.html     |    8 +-
 .../impala_disable_hbase_num_rows_estimate.html    |   93 ++
 .../impala_disable_row_runtime_filtering.html      |    8 +-
 .../impala_disable_streaming_preaggregations.html  |    8 +-
 .../html/topics/impala_disable_unsafe_spills.html  |    8 +-
 docs/build/html/topics/impala_disk_space.html      |  279 +++-
 docs/build/html/topics/impala_distinct.html        |    8 +-
 docs/build/html/topics/impala_dml.html             |   10 +-
 docs/build/html/topics/impala_double.html          |    8 +-
 docs/build/html/topics/impala_drop_database.html   |   10 +-
 docs/build/html/topics/impala_drop_function.html   |    8 +-
 docs/build/html/topics/impala_drop_role.html       |    8 +-
 docs/build/html/topics/impala_drop_stats.html      |    8 +-
 docs/build/html/topics/impala_drop_table.html      |   52 +-
 docs/build/html/topics/impala_drop_view.html       |    8 +-
 .../html/topics/impala_enable_expr_rewrites.html   |    6 +-
 .../impala_exec_single_node_rows_threshold.html    |    8 +-
 .../html/topics/impala_exec_time_limit_s.html      |    8 +-
 docs/build/html/topics/impala_explain.html         |    8 +-
 docs/build/html/topics/impala_explain_level.html   |    8 +-
 docs/build/html/topics/impala_explain_plan.html    |  290 ++--
 docs/build/html/topics/impala_faq.html             |    8 +-
 .../html/topics/impala_fetch_rows_timeout_ms.html  |   71 +
 docs/build/html/topics/impala_file_formats.html    |  126 +-
 docs/build/html/topics/impala_fixed_issues.html    |    8 +-
 docs/build/html/topics/impala_float.html           |    8 +-
 docs/build/html/topics/impala_functions.html       |   40 +-
 .../html/topics/impala_functions_overview.html     |    8 +-
 docs/build/html/topics/impala_grant.html           |   13 +-
 docs/build/html/topics/impala_group_by.html        |    8 +-
 docs/build/html/topics/impala_group_concat.html    |    8 +-
 docs/build/html/topics/impala_hadoop.html          |    8 +-
 docs/build/html/topics/impala_having.html          |    8 +-
 docs/build/html/topics/impala_hbase.html           |   55 +-
 .../html/topics/impala_hbase_cache_blocks.html     |    8 +-
 docs/build/html/topics/impala_hbase_caching.html   |    8 +-
 docs/build/html/topics/impala_hints.html           |    8 +-
 docs/build/html/topics/impala_hudi.html            |   93 ++
 docs/build/html/topics/impala_identifiers.html     |    8 +-
 .../html/topics/impala_idle_session_timeout.html   |    6 +-
 docs/build/html/topics/impala_impala_shell.html    |    8 +-
 .../html/topics/impala_incompatible_changes.html   |  190 +--
 docs/build/html/topics/impala_insert.html          |  103 +-
 docs/build/html/topics/impala_install.html         |    8 +-
 docs/build/html/topics/impala_int.html             |    8 +-
 docs/build/html/topics/impala_intro.html           |    6 +-
 .../html/topics/impala_invalidate_metadata.html    |    8 +-
 docs/build/html/topics/impala_isilon.html          |    8 +-
 docs/build/html/topics/impala_jdbc.html            |  437 ++----
 docs/build/html/topics/impala_joins.html           |    8 +-
 docs/build/html/topics/impala_kerberos.html        |   22 +-
 docs/build/html/topics/impala_known_issues.html    |   89 +-
 docs/build/html/topics/impala_kudu.html            |    8 +-
 docs/build/html/topics/impala_kudu_read_mode.html  |    6 +-
 docs/build/html/topics/impala_langref.html         |    8 +-
 docs/build/html/topics/impala_langref_sql.html     |   11 +-
 .../html/topics/impala_langref_unsupported.html    |   60 +-
 docs/build/html/topics/impala_ldap.html            |    8 +-
 docs/build/html/topics/impala_limit.html           |    8 +-
 docs/build/html/topics/impala_lineage.html         |    8 +-
 docs/build/html/topics/impala_literals.html        |    8 +-
 docs/build/html/topics/impala_live_progress.html   |   53 +-
 docs/build/html/topics/impala_live_summary.html    |   72 +-
 docs/build/html/topics/impala_load_data.html       |   72 +-
 docs/build/html/topics/impala_logging.html         |  146 +-
 docs/build/html/topics/impala_map.html             |   10 +-
 docs/build/html/topics/impala_math_functions.html  |    8 +-
 docs/build/html/topics/impala_max.html             |    8 +-
 docs/build/html/topics/impala_max_errors.html      |    8 +-
 .../impala_max_mem_estimate_for_admission.html     |    6 +-
 .../topics/impala_max_num_runtime_filters.html     |    8 +-
 .../topics/impala_max_result_spooling_mem.html     |   62 +
 docs/build/html/topics/impala_max_row_size.html    |    8 +-
 .../html/topics/impala_max_scan_range_length.html  |    8 +-
 .../impala_max_spilled_result_spooling_mem.html    |   67 +
 docs/build/html/topics/impala_mem_limit.html       |   30 +-
 docs/build/html/topics/impala_metadata.html        |   55 +-
 docs/build/html/topics/impala_min.html             |    8 +-
 .../topics/impala_min_spillable_buffer_size.html   |    8 +-
 docs/build/html/topics/impala_misc_functions.html  |    8 +-
 docs/build/html/topics/impala_mixed_security.html  |    8 +-
 docs/build/html/topics/impala_mt_dop.html          |    8 +-
 docs/build/html/topics/impala_ndv.html             |    8 +-
 docs/build/html/topics/impala_new_features.html    |  505 +++++--
 docs/build/html/topics/impala_num_nodes.html       |    8 +-
 .../topics/impala_num_rows_produced_limit.html     |    6 +-
 .../html/topics/impala_num_scanner_threads.html    |    8 +-
 docs/build/html/topics/impala_odbc.html            |    8 +-
 docs/build/html/topics/impala_offset.html          |    8 +-
 docs/build/html/topics/impala_operators.html       |   72 +-
 .../impala_optimize_partition_key_scans.html       |    8 +-
 docs/build/html/topics/impala_orc.html             |   42 +-
 docs/build/html/topics/impala_order_by.html        |   35 +-
 docs/build/html/topics/impala_parquet.html         |  111 +-
 .../impala_parquet_annotate_strings_utf8.html      |    8 +-
 .../topics/impala_parquet_array_resolution.html    |    8 +-
 .../topics/impala_parquet_compression_codec.html   |    8 +-
 .../impala_parquet_dictionary_filtering.html       |    6 +-
 .../impala_parquet_fallback_schema_resolution.html |    8 +-
 .../html/topics/impala_parquet_file_size.html      |    8 +-
 .../impala_parquet_object_store_split_size.html    |   46 +
 .../impala_parquet_page_row_count_limit.html       |    6 +-
 .../topics/impala_parquet_read_page_index.html     |    6 +-
 .../topics/impala_parquet_read_statistics.html     |    6 +-
 .../topics/impala_parquet_write_page_index.html    |    6 +-
 docs/build/html/topics/impala_partitioning.html    |   36 +-
 .../html/topics/impala_perf_benchmarking.html      |    8 +-
 docs/build/html/topics/impala_perf_cookbook.html   |    8 +-
 .../html/topics/impala_perf_hdfs_caching.html      |    8 +-
 docs/build/html/topics/impala_perf_joins.html      |   14 +-
 docs/build/html/topics/impala_perf_resources.html  |    8 +-
 docs/build/html/topics/impala_perf_skew.html       |    8 +-
 docs/build/html/topics/impala_perf_stats.html      |    8 +-
 docs/build/html/topics/impala_perf_testing.html    |   20 +-
 docs/build/html/topics/impala_performance.html     |   10 +-
 docs/build/html/topics/impala_planning.html        |    8 +-
 docs/build/html/topics/impala_porting.html         |    8 +-
 docs/build/html/topics/impala_ports.html           |  592 +-------
 docs/build/html/topics/impala_prefetch_mode.html   |    8 +-
 docs/build/html/topics/impala_prereqs.html         |    8 +-
 docs/build/html/topics/impala_processes.html       |    8 +-
 docs/build/html/topics/impala_proxy.html           |  212 +--
 docs/build/html/topics/impala_query_options.html   |   35 +-
 .../html/topics/impala_query_results_spooling.html |  169 +++
 docs/build/html/topics/impala_query_timeout_s.html |    8 +-
 docs/build/html/topics/impala_rcfile.html          |   28 +-
 docs/build/html/topics/impala_real.html            |    8 +-
 docs/build/html/topics/impala_refresh.html         |    8 +-
 .../html/topics/impala_refresh_authorization.html  |    6 +-
 .../html/topics/impala_refresh_functions.html      |    6 +-
 docs/build/html/topics/impala_release_notes.html   |    8 +-
 docs/build/html/topics/impala_relnotes.html        |    6 +-
 .../html/topics/impala_replica_preference.html     |    8 +-
 docs/build/html/topics/impala_request_pool.html    |    8 +-
 docs/build/html/topics/impala_reserved_words.html  |    8 +-
 .../html/topics/impala_resource_management.html    |    8 +-
 .../html/topics/impala_resource_trace_ratio.html   |    6 +-
 docs/build/html/topics/impala_revoke.html          |    8 +-
 .../topics/impala_runtime_bloom_filter_size.html   |    8 +-
 .../topics/impala_runtime_filter_max_size.html     |    8 +-
 .../topics/impala_runtime_filter_min_size.html     |    8 +-
 .../html/topics/impala_runtime_filter_mode.html    |    8 +-
 .../topics/impala_runtime_filter_wait_time_ms.html |    8 +-
 .../html/topics/impala_runtime_filtering.html      |    8 +-
 docs/build/html/topics/impala_s3.html              |  999 +++++--------
 .../html/topics/impala_s3_skip_insert_staging.html |   10 +-
 docs/build/html/topics/impala_scalability.html     |   55 +-
 docs/build/html/topics/impala_scaling_limits.html  |    6 +-
 .../build/html/topics/impala_scan_bytes_limit.html |    6 +-
 .../topics/impala_schedule_random_replica.html     |    8 +-
 docs/build/html/topics/impala_schema_design.html   |    8 +-
 docs/build/html/topics/impala_schema_objects.html  |    8 +-
 docs/build/html/topics/impala_scratch_limit.html   |    8 +-
 docs/build/html/topics/impala_security.html        |    8 +-
 docs/build/html/topics/impala_security_files.html  |    8 +-
 .../html/topics/impala_security_guidelines.html    |    8 +-
 .../build/html/topics/impala_security_install.html |    8 +-
 .../html/topics/impala_security_metastore.html     |    8 +-
 docs/build/html/topics/impala_security_webui.html  |    8 +-
 docs/build/html/topics/impala_select.html          |   53 +-
 docs/build/html/topics/impala_seqfile.html         |   28 +-
 docs/build/html/topics/impala_set.html             |    8 +-
 docs/build/html/topics/impala_shell_commands.html  |  104 +-
 docs/build/html/topics/impala_shell_options.html   |  386 ++---
 .../html/topics/impala_shell_running_commands.html |    8 +-
 docs/build/html/topics/impala_show.html            |   32 +-
 .../html/topics/impala_shuffle_distinct_exprs.html |    8 +-
 docs/build/html/topics/impala_shutdown.html        |   38 +-
 docs/build/html/topics/impala_smallint.html        |    8 +-
 .../html/topics/impala_spool_query_results.html    |   69 +
 docs/build/html/topics/impala_ssl.html             |  131 +-
 docs/build/html/topics/impala_stddev.html          |    8 +-
 docs/build/html/topics/impala_string.html          |    8 +-
 .../build/html/topics/impala_string_functions.html |  481 +++++--
 docs/build/html/topics/impala_struct.html          |   10 +-
 docs/build/html/topics/impala_subqueries.html      |    8 +-
 docs/build/html/topics/impala_sum.html             |    8 +-
 .../html/topics/impala_support_start_over.html     |    8 +-
 docs/build/html/topics/impala_sync_ddl.html        |    8 +-
 docs/build/html/topics/impala_tables.html          |   12 +-
 docs/build/html/topics/impala_tablesample.html     |    8 +-
 .../impala_thread_reservation_aggregate_limit.html |    6 +-
 .../topics/impala_thread_reservation_limit.html    |    6 +-
 docs/build/html/topics/impala_timeouts.html        |    8 +-
 docs/build/html/topics/impala_timestamp.html       |    8 +-
 docs/build/html/topics/impala_timezone.html        |    6 +-
 docs/build/html/topics/impala_tinyint.html         |    8 +-
 .../build/html/topics/impala_topn_bytes_limit.html |    6 +-
 docs/build/html/topics/impala_transactions.html    |   10 +-
 docs/build/html/topics/impala_troubleshooting.html |   62 +-
 docs/build/html/topics/impala_truncate_table.html  |   10 +-
 docs/build/html/topics/impala_tutorial.html        |   38 +-
 docs/build/html/topics/impala_txtfile.html         |  137 +-
 docs/build/html/topics/impala_udf.html             |   52 +-
 docs/build/html/topics/impala_union.html           |    8 +-
 docs/build/html/topics/impala_update.html          |    8 +-
 docs/build/html/topics/impala_upgrading.html       |   38 +-
 docs/build/html/topics/impala_upsert.html          |    8 +-
 docs/build/html/topics/impala_use.html             |    8 +-
 docs/build/html/topics/impala_values.html          |  115 ++
 docs/build/html/topics/impala_varchar.html         |    8 +-
 docs/build/html/topics/impala_variance.html        |    8 +-
 docs/build/html/topics/impala_views.html           |    8 +-
 docs/build/html/topics/impala_webui.html           |  403 +++---
 docs/build/html/topics/impala_with.html            |    8 +-
 docs/build/impala-3.4.pdf                          |  Bin 0 -> 3389169 bytes
 278 files changed, 7471 insertions(+), 4872 deletions(-)

diff --git a/docs/build/html/index.html b/docs/build/html/index.html
index 2761a54..c551bf8 100644
--- a/docs/build/html/index.html
+++ b/docs/build/html/index.html
@@ -4,12 +4,12 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="map" />
 <meta name="DC.Title" content="Apache Impala Guide" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="impala" />
 <link rel="stylesheet" type="text/css" href="commonltr.css" />
 <title>Apache Impala Guide</title></head>
-<body id="impala"><h1 class="title topictitle1">Apache Impala Guide</h1><div><ul class="map"><li class="topicref"><a href="topics/impala_intro.html">Introducing Apache Impala</a></li><li class="topicref"><a href="topics/impala_concepts.html">Concepts and Architecture</a><ul><li class="topicref"><a href="topics/impala_components.html">Components</a></li><li class="topicref"><a href="topics/impala_development.html">Developing Applications</a></li><li class="topicref"><a href="topics/impala [...]
\ No newline at end of file
+<body id="impala"><h1 class="title topictitle1">Apache Impala Guide</h1><div><ul class="map"><li class="topicref"><a href="topics/impala_intro.html">Introducing Apache Impala</a></li><li class="topicref"><a href="topics/impala_concepts.html">Concepts and Architecture</a><ul><li class="topicref"><a href="topics/impala_components.html">Components</a></li><li class="topicref"><a href="topics/impala_development.html">Developing Applications</a></li><li class="topicref"><a href="topics/impala [...]
\ No newline at end of file
diff --git a/docs/build/html/topics/impala_abort_on_error.html b/docs/build/html/topics/impala_abort_on_error.html
index 6e4eccb..a2f17eb 100644
--- a/docs/build/html/topics/impala_abort_on_error.html
+++ b/docs/build/html/topics/impala_abort_on_error.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="ABORT_ON_ERROR 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="abort_on_error" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_adls.html b/docs/build/html/topics/impala_adls.html
index cb08957..226cbcc 100644
--- a/docs/build/html/topics/impala_adls.html
+++ b/docs/build/html/topics/impala_adls.html
@@ -4,12 +4,12 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Using Impala with the Azure Data Lake Store (ADLS)" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="adls" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_admin.html b/docs/build/html/topics/impala_admin.html
index 3c5a786..5883763 100644
--- a/docs/build/html/topics/impala_admin.html
+++ b/docs/build/html/topics/impala_admin.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Administration" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_timeouts.html" />
@@ -13,8 +13,8 @@
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_disk_space.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="admin" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_admission.html b/docs/build/html/topics/impala_admission.html
index da7e057..ff08edb 100644
--- a/docs/build/html/topics/impala_admission.html
+++ b/docs/build/html/topics/impala_admission.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Admission Control and Query Queuing" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_resource_management.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="admission_control" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_admission_config.html b/docs/build/html/topics/impala_admission_config.html
index 9644f97..74cf877 100644
--- a/docs/build/html/topics/impala_admission_config.html
+++ b/docs/build/html/topics/impala_admission_config.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Configuring Admission Control" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_resource_management.html" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="admission_control" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_aggregate_functions.html b/docs/build/html/topics/impala_aggregate_functions.html
index 8a6352a..01c2ef7 100644
--- a/docs/build/html/topics/impala_aggregate_functions.html
+++ b/docs/build/html/topics/impala_aggregate_functions.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Aggregate Functions" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_functions.html" />
@@ -21,8 +21,8 @@
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_variance.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="aggregate_functions" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_aliases.html b/docs/build/html/topics/impala_aliases.html
index 93d511a..f4b10d8 100644
--- a/docs/build/html/topics/impala_aliases.html
+++ b/docs/build/html/topics/impala_aliases.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Overview of Impala Aliases" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_schema_objects.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="aliases" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_allow_erasure_coded_files.html b/docs/build/html/topics/impala_allow_erasure_coded_files.html
index c6a0b7e..021a725 100644
--- a/docs/build/html/topics/impala_allow_erasure_coded_files.html
+++ b/docs/build/html/topics/impala_allow_erasure_coded_files.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="ALLOW_ERASURE_CODED_FILES 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.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="allow_erasure_coded_files" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_allow_unsupported_formats.html b/docs/build/html/topics/impala_allow_unsupported_formats.html
index 2757318..c1e5629 100644
--- a/docs/build/html/topics/impala_allow_unsupported_formats.html
+++ b/docs/build/html/topics/impala_allow_unsupported_formats.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="ALLOW_UNSUPPORTED_FORMATS 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="allow_unsupported_formats" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_alter_database.html b/docs/build/html/topics/impala_alter_database.html
index ad4690f..9a3be2e 100644
--- a/docs/build/html/topics/impala_alter_database.html
+++ b/docs/build/html/topics/impala_alter_database.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="ALTER DATABASE Statement" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_langref_sql.html" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="alter_database" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_alter_table.html b/docs/build/html/topics/impala_alter_table.html
index bed66a2..f24982b 100644
--- a/docs/build/html/topics/impala_alter_table.html
+++ b/docs/build/html/topics/impala_alter_table.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="ALTER TABLE 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="alter_table" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -281,7 +281,7 @@ alter table fast_growing_data partition (year = 2016, month in (10,11,12)) set f
         PARTITION</code> can create or remove folders as needed in the Amazon S3 system. Prior
         to <span class="keyword">Impala 2.6</span>, you had to create folders yourself and point
         Impala database, tables, or partitions at them, and manually remove folders when no
-        longer needed. See <a class="xref" href="../shared/../topics/impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details about reading
+        longer needed. See <a class="xref" href="../shared/../topics/impala_s3.html#s3">Using Impala with Amazon S3 Object Store</a> for details about reading
         and writing S3 data with Impala.
       </p>
 
diff --git a/docs/build/html/topics/impala_alter_view.html b/docs/build/html/topics/impala_alter_view.html
index df2501b..6393075 100644
--- a/docs/build/html/topics/impala_alter_view.html
+++ b/docs/build/html/topics/impala_alter_view.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="ALTER VIEW 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="alter_view" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_analytic_functions.html b/docs/build/html/topics/impala_analytic_functions.html
index 0108a8a..580c0ef 100644
--- a/docs/build/html/topics/impala_analytic_functions.html
+++ b/docs/build/html/topics/impala_analytic_functions.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Analytic Functions" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_functions.html" />
@@ -28,25 +28,25 @@
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="analytic_functions" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_appx_count_distinct.html b/docs/build/html/topics/impala_appx_count_distinct.html
index 0c45575..2cdc8af 100644
--- a/docs/build/html/topics/impala_appx_count_distinct.html
+++ b/docs/build/html/topics/impala_appx_count_distinct.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="APPX_COUNT_DISTINCT Query Option (Impala 2.0 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="appx_count_distinct" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_appx_median.html b/docs/build/html/topics/impala_appx_median.html
index d052e31..eb4fa09 100644
--- a/docs/build/html/topics/impala_appx_median.html
+++ b/docs/build/html/topics/impala_appx_median.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="APPX_MEDIAN 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="appx_median" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_array.html b/docs/build/html/topics/impala_array.html
index 30a12c5..f2a733a 100644
--- a/docs/build/html/topics/impala_array.html
+++ b/docs/build/html/topics/impala_array.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="ARRAY 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="array" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -160,7 +160,7 @@ type ::= <var class="keyword varname">primitive_type</var> | <var class="keyword
 
 
         <li class="li">
-          <p class="p" id="array__d6e3282">
+          <p class="p" id="array__d6e3283">
             The maximum length of the column definition for any complex type, including
             declarations for any nested types, is 4000 characters.
           </p>
diff --git a/docs/build/html/topics/impala_auditing.html b/docs/build/html/topics/impala_auditing.html
index 87f94f1..7224cf8 100644
--- a/docs/build/html/topics/impala_auditing.html
+++ b/docs/build/html/topics/impala_auditing.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Auditing Impala Operations" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_security.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="auditing" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -274,42 +274,37 @@
 
     <div class="body conbody">
 
-      <p class="p">
-        The kinds of SQL queries represented in the audit log are:
-      </p>
+      <p class="p"> The following types of SQL operations are recorded in the audit
+        log:</p>
 
 
       <ul class="ul">
-        <li class="li">
-          Queries that are prevented due to lack of authorization.
-        </li>
+        <li class="li"> Queries that are prevented due to lack of authorization. </li>
 
+        <li class="li"> Queries that Impala can analyze and parse to determine that they
+          are authorized. The audit data is recorded immediately after Impala
+          finishes its analysis, before the query is actually executed. </li>
 
-        <li class="li">
-          Queries that Impala can analyze and parse to determine that they are authorized. The
-          audit data is recorded immediately after Impala finishes its analysis, before the
-          query is actually executed.
-        </li>
+        <li class="li"> Queries whose results are available to be fetched by clients.</li>
+
+        <li class="li">Finished DDL operations.</li>
 
       </ul>
 
 
-      <p class="p">
-        The audit log does not contain entries for queries that could not be parsed and
-        analyzed. For example, a query that fails due to a syntax error is not recorded in the
-        audit log. The audit log also does not contain queries that fail due to a reference to a
-        table that does not exist, if you would be authorized to access the table if it did
-        exist.
-      </p>
+      <p class="p"> The audit log does not contain entries for queries that could not be
+        parsed and analyzed. For example, a query that fails due to a syntax
+        error is not recorded in the audit log. </p>
 
+      <p class="p">The audit log does not contain queries that fail due to a reference to
+        a table that does not exist. </p>
 
-      <p class="p">
-        Certain statements in the <span class="keyword cmdname">impala-shell</span> interpreter, such as
-        <code class="ph codeph">CONNECT</code>, <code class="ph codeph">SUMMARY</code>,
-        <code class="ph codeph">PROFILE</code>, <code class="ph codeph">SET</code>, and <code class="ph codeph">QUIT</code>, do not
-        correspond to actual SQL queries, and these statements are not reflected in the audit
-        log.
-      </p>
+
+      <p class="p"> Certain statements in the <span class="keyword cmdname">impala-shell</span> interpreter,
+        such as <code class="ph codeph">CONNECT</code>, <code class="ph codeph">SUMMARY</code>,
+          <code class="ph codeph">PROFILE</code>, <code class="ph codeph">SET</code>, and
+          <code class="ph codeph">QUIT</code>, do not correspond to actual SQL queries, and
+        these statements are not recorded in the audit log. </p>
 
 
     </div>
diff --git a/docs/build/html/topics/impala_authentication.html b/docs/build/html/topics/impala_authentication.html
index 6425da5..7e769c6 100644
--- a/docs/build/html/topics/impala_authentication.html
+++ b/docs/build/html/topics/impala_authentication.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Authentication" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_security.html" />
@@ -15,8 +15,8 @@
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_delegation.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="authentication" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_authorization.html b/docs/build/html/topics/impala_authorization.html
index 1077433..58b9c7f 100644
--- a/docs/build/html/topics/impala_authorization.html
+++ b/docs/build/html/topics/impala_authorization.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Authorization" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_security.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="authorization" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -96,6 +96,9 @@
         SQL statements in <span class="keyword">Impala 3.0</span> and higher. The following notations
         are used:
         <ul class="ul">
+          <li class="li">The <strong class="ph b">SERVER</strong> resource type in Ranger implies all databases,
+            all tables, all columns, all UDFs, and all URIs.</li>
+
           <li class="li">
             <strong class="ph b">ANY</strong> denotes the <code class="ph codeph">SELECT</code>, <code class="ph codeph">INSERT</code>,
             <code class="ph codeph">CREATE</code>, <code class="ph codeph">ALTER</code>, <code class="ph codeph">DROP</code>,
@@ -126,7 +129,7 @@
         </ul>
 
         
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="sentry_priv_model__d6e172" class="table" frame="border" border="1" rules="all"><colgroup><col /><col /><col /></colgroup><tbody class="tbody">
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="sentry_priv_model__d6e178" class="table" frame="border" border="1" rules="all"><colgroup><col /><col /><col /></colgroup><tbody class="tbody">
               <tr class="row">
                 <td class="entry cellrowborder" style="vertical-align:top;">
                   <strong class="ph b">SQL Statement</strong>
@@ -1311,9 +1314,58 @@
   </div>
 
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title4" id="secure_startup">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title4" id="concept_fgf_smj_bjb">
+
+    <h2 class="title topictitle2" id="ariaid-title4">Object Ownership in Ranger</h2>
+
+
+    <div class="body conbody">
+
+      <p class="p">
+        Object ownership for tables, views and databases is enabled by default in Impala.
+      </p>
+
+
+      <p class="p">
+        To define owner specific privileges, go to ranger UI and define appropriate policies on
+        the <code class="ph codeph">{OWNER}</code> user.
+      </p>
+
+
+      <p class="p">
+        The <code class="ph codeph">CREATE</code> statements implicitly make the user running the statement
+        the owner of the object. For example, if <var class="keyword varname">User A</var> creates a database,
+        <var class="keyword varname">foo</var>, via the <code class="ph codeph">CREATE DATABASE</code> statement,
+        <var class="keyword varname">User A</var> now owns the <var class="keyword varname">foo</var> database and is authorized
+        to perform any operation on the <var class="keyword varname">foo</var> database.
+      </p>
+
+
+      <p class="p">
+        An ownership can be transferred to another user or role via the <code class="ph codeph">ALTER
+        DATABASE</code>, <code class="ph codeph">ALTER TABLE</code>, or <code class="ph codeph">ALTER VIEW</code> with the
+        <code class="ph codeph">SET OWNER</code> clause.
+      </p>
+
+
+      <div class="note note" id="concept_fgf_smj_bjb__impala-8937"><span class="notetitle">Note:</span> 
+        Currently, due to a known issue
+        (<a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-8937" target="_blank">IMPALA-8937</a>),
+        until the ownership information is fully loaded in the coordinator catalog cache, the
+        owner of a table might not be able to see the table when executing the <code class="ph codeph">SHOW
+        TABLES</code> statement The owner can still query the table.
+      </div>
+
+
+    </div>
+
+
+  </div>
+
+
+  <div class="topic concept nested1" aria-labelledby="ariaid-title5" id="secure_startup">
 
-    <h2 class="title topictitle2" id="ariaid-title4">Starting Impala with Sentry Authorization Enabled</h2>
+    <h2 class="title topictitle2" id="ariaid-title5">Starting Impala with Sentry Authorization Enabled</h2>
 
 
     
@@ -1361,9 +1413,9 @@
   </div>
 
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title5" id="enable_ranger_authz">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title6" id="enable_ranger_authz">
 
-    <h2 class="title topictitle2" id="ariaid-title5">Starting Impala with Ranger Authorization Enabled</h2>
+    <h2 class="title topictitle2" id="ariaid-title6">Starting Impala with Ranger Authorization Enabled</h2>
 
 
     <div class="body conbody">
@@ -1417,9 +1469,9 @@
   </div>
 
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title6" id="sentry_service">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title7" id="sentry_service">
 
-    <h2 class="title topictitle2" id="ariaid-title6">Managing Privileges</h2>
+    <h2 class="title topictitle2" id="ariaid-title7">Managing Privileges</h2>
 
 
     <div class="body conbody">
@@ -1441,9 +1493,9 @@
     </div>
 
 
-    <div class="topic concept nested2" aria-labelledby="ariaid-title7" id="changing_privileges">
+    <div class="topic concept nested2" aria-labelledby="ariaid-title8" id="changing_privileges">
 
-      <h3 class="title topictitle3" id="ariaid-title7">Changing Privileges from Outside of Impala</h3>
+      <h3 class="title topictitle3" id="ariaid-title8">Changing Privileges from Outside of Impala</h3>
 
 
       <div class="body conbody">
@@ -1497,9 +1549,9 @@
     </div>
 
 
-    <div class="topic concept nested2" aria-labelledby="ariaid-title8" id="granting_on_uri">
+    <div class="topic concept nested2" aria-labelledby="ariaid-title9" id="granting_on_uri">
 
-      <h3 class="title topictitle3" id="ariaid-title8">Granting Privileges on URI</h3>
+      <h3 class="title topictitle3" id="ariaid-title9">Granting Privileges on URI</h3>
 
 
       <div class="body conbody">
@@ -1550,9 +1602,9 @@ GRANT ALL ON URI hdfs://namenode:port/path/to/dir TO &lt;role&gt;</code></pre>
     </div>
 
 
-    <div class="topic concept nested2" aria-labelledby="ariaid-title9" id="concept_k45_lbm_f2b">
+    <div class="topic concept nested2" aria-labelledby="ariaid-title10" id="concept_k45_lbm_f2b">
 
-      <h3 class="title topictitle3" id="ariaid-title9">Examples of Setting up Authorization for Security Scenarios</h3>
+      <h3 class="title topictitle3" id="ariaid-title10">Examples of Setting up Authorization for Security Scenarios</h3>
 
 
       <div class="body conbody">
@@ -1750,9 +1802,9 @@ GRANT SELECT ON TABLE training1.course1 TO ROLE student;</code></pre>
   </div>
 
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title10" id="security_schema">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title11" id="security_schema">
 
-    <h2 class="title topictitle2" id="ariaid-title10">Setting Up Schema Objects for a Secure Impala Deployment</h2>
+    <h2 class="title topictitle2" id="ariaid-title11">Setting Up Schema Objects for a Secure Impala Deployment</h2>
 
 
     <div class="body conbody">
@@ -1778,9 +1830,9 @@ GRANT SELECT ON TABLE training1.course1 TO ROLE student;</code></pre>
   </div>
 
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title11" id="sec_ex_default">
+  <div class="topic concept nested1" aria-labelledby="ariaid-title12" id="sec_ex_default">
 
-    <h2 class="title topictitle2" id="ariaid-title11">The DEFAULT Database in a Secure Deployment</h2>
+    <h2 class="title topictitle2" id="ariaid-title12">The DEFAULT Database in a Secure Deployment</h2>
 
 
     <div class="body conbody">
@@ -1800,6 +1852,131 @@ GRANT SELECT ON TABLE training1.course1 TO ROLE student;</code></pre>
 
   </div>
 
+  <div class="topic concept nested1" aria-labelledby="ariaid-title13" id="sec_ranger_col_masking">
+    <h2 class="title topictitle2" id="ariaid-title13">Ranger Column Masking</h2>
+
+    <div class="body conbody">
+    <p class="p"> Ranger column masking hides sensitive columnar data in Impala query output. For example, you
+        can define a policy that reveals only the first or last four characters of column data.
+        Column masking is enabled by default. The Impala behavior mimics Hive behavior with respect
+        to column masking. For more information, see the <a class="xref" href="https://cwiki.apache.org/confluence/display/RANGER/Row-level+filtering+and+column-masking+using+Apache+Ranger+policies+in+Apache+Hive" target="_blank">Apache Ranger documentation</a>.</p>
+
+
+      <div class="p">
+        The following table lists all supported, built-in mask types for defining column masking in
+        a policy using the Ranger REST API. 
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="sec_ranger_col_masking__table_mask_types" class="table" frame="border" border="1" rules="all"><colgroup><col /><col /><col /><col /></colgroup><thead class="thead" style="text-align:left;">
+              <tr class="row">
+                <th class="entry cellrowborder" style="vertical-align:top;" id="d21258e1869">Type</th>
+
+                <th class="entry cellrowborder" style="vertical-align:top;" id="d21258e1872">Name</th>
+
+                <th class="entry cellrowborder" style="vertical-align:top;" id="d21258e1875">Description</th>
+
+                <th class="entry cellrowborder" style="vertical-align:top;" id="d21258e1878">Transformer</th>
+
+              </tr>
+
+            </thead>
+<tbody class="tbody">
+              <tr class="row">
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1869 ">MASK</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1872 ">Redact</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1875 ">Replace lowercase with 'x', uppercase with 'X', digits with '0'</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1878 ">mask({col})</td>
+
+              </tr>
+
+              <tr class="row">
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1869 ">MASK_SHOW_LAST_4</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1872 ">Partial mask: show last 4</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1875 ">Show last 4 characters; replace rest with 'x'</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1878 ">mask_show_last_n({col}, 4, 'x', 'x', 'x', -1, '1')</td>
+
+              </tr>
+
+              <tr class="row">
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1869 ">MASK_SHOW_FIRST_4</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1872 ">Partial mask: show first 4</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1875 ">Show first 4 characters; replace rest with 'x'</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1878 ">mask_show_first_n({col}, 4, 'x', 'x', 'x', -1, '1')</td>
+
+              </tr>
+
+              <tr class="row">
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1869 ">MASK_HASH</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1872 ">Hash</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1875 ">Hash the value</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1878 ">mask_hash({col})</td>
+
+              </tr>
+
+              <tr class="row">
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1869 ">MASK_NULL</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1872 ">Nullify</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1875 ">Replace with NULL</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1878 "> N/A</td>
+
+              </tr>
+
+              <tr class="row">
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1869 ">MASK_NONE</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1872 ">Unmasked (retain original value)</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1875 ">No masking</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1878 "> N/A</td>
+
+              </tr>
+
+              <tr class="row">
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1869 ">MASK_DATE_SHOW_YEAR</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1872 ">Date: show only year</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1875 ">Date: show only year</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1878 ">mask({col}, 'x', 'x', 'x', -1, '1', 1, 0, -1)</td>
+
+              </tr>
+
+              <tr class="row">
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1869 ">CUSTOM</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1872 ">Custom</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1875 ">Custom</td>
+
+                <td class="entry cellrowborder" style="vertical-align:top;" headers="d21258e1878 ">N/A</td>
+
+              </tr>
+
+            </tbody>
+</table>
+</div>
+
+      </div>
+
+    </div>
+
+  </div>
+
 
 </body>
 </html>
\ No newline at end of file
diff --git a/docs/build/html/topics/impala_avg.html b/docs/build/html/topics/impala_avg.html
index 80778a3..0432cdf 100644
--- a/docs/build/html/topics/impala_avg.html
+++ b/docs/build/html/topics/impala_avg.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="AVG 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="avg" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_avro.html b/docs/build/html/topics/impala_avro.html
index 386e862..05b4070 100644
--- a/docs/build/html/topics/impala_avro.html
+++ b/docs/build/html/topics/impala_avro.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Using the Avro File Format with Impala Tables" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_file_formats.html" />
@@ -20,17 +20,17 @@
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="avro" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -55,23 +55,23 @@
     
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" class="table" frame="border" border="1" rules="all"><caption><span class="tablecap"><span class="table--title-label">Table 1. </span>Avro Format Support in Impala</span></caption><colgroup><col style="width:10%" /><col style="width:10%" /><col style="width:20%" /><col style="width:30%" /><col style="width:30%" /></colgroup><thead class="thead" style="text-align:left;">
           <tr class="row">
-            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d24841e170">
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d25374e170">
               File Type
             </th>
 
-            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d24841e173">
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d25374e173">
               Format
             </th>
 
-            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d24841e176">
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d25374e176">
               Compression Codecs
             </th>
 
-            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d24841e179">
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d25374e179">
               Impala Can CREATE?
             </th>
 
-            <th class="entry cell-norowborder" style="vertical-align:top;" id="d24841e182">
+            <th class="entry cell-norowborder" style="vertical-align:top;" id="d25374e182">
               Impala Can INSERT?
             </th>
 
@@ -80,23 +80,23 @@
         </thead>
 <tbody class="tbody">
           <tr class="row">
-            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d24841e170 ">
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d25374e170 ">
               <a class="xref" href="impala_avro.html#avro">Avro</a>
             </td>
 
-            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d24841e173 ">
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d25374e173 ">
               Structured
             </td>
 
-            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d24841e176 ">
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d25374e176 ">
               Snappy, gzip, deflate
             </td>
 
-            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d24841e179 ">
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d25374e179 ">
               Yes, in Impala 1.4.0 and higher. In lower versions, create the table using Hive.
             </td>
 
-            <td class="entry cellrowborder" style="vertical-align:top;" headers="d24841e182 ">
+            <td class="entry cellrowborder" style="vertical-align:top;" headers="d25374e182 ">
               No. Import data by using <code class="ph codeph">LOAD DATA</code> on data files already in the
               right format, or use <code class="ph codeph">INSERT</code> in Hive followed by <code class="ph codeph">REFRESH
               <var class="keyword varname">table_name</var></code> in Impala.
@@ -158,8 +158,6 @@
       </div>
 
 
-      
-
       <p class="p">
         The following examples demonstrate creating an Avro table in Impala, using either an inline column
         specification or one taken from a JSON file stored in HDFS:
@@ -602,50 +600,129 @@ ALTER TABLE avro_table SET TBLPROPERTIES (
 
 
     <div class="body conbody">
+      <p class="p"> The Avro format defines a set of data types whose names differ from
+        the names of the corresponding Impala data types. If you are preparing
+        Avro files using other Hadoop components such as Pig or MapReduce, you
+        might need to work with the type names defined by Avro. The following
+        figure lists the Avro-defined types and the equivalent types in Impala. </p>
 
-      <p class="p">
-        The Avro format defines a set of data types whose names differ from the names of the corresponding Impala
-        data types. If you are preparing Avro files using other Hadoop components such as Pig or MapReduce, you
-        might need to work with the type names defined by Avro. The following figure lists the Avro-defined types
-        and the equivalent types in Impala.
-      </p>
+      <p class="p"><strong class="ph b">Primitive types:</strong></p>
 
+      
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="avro_data_types__table_uvv_plj_gjb" class="table" frame="border" border="1" rules="all"><colgroup><col style="width:143.44pt" /><col style="width:165.77pt" /></colgroup><thead class="thead" style="text-align:left;">
+            <tr class="row">
+              <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d25374e848">Avro type</th>
 
-<pre class="pre codeblock"><code>Primitive Types (Avro -&gt; Impala)
---------------------------------
-STRING -&gt; STRING
-STRING -&gt; CHAR
-STRING -&gt; VARCHAR
-INT -&gt; INT
-BOOLEAN -&gt; BOOLEAN
-LONG -&gt;  BIGINT
-FLOAT -&gt;  FLOAT
-DOUBLE -&gt; DOUBLE
+              <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d25374e851">Impala type</th>
 
-Logical Types
--------------
-BYTES + logicalType = "decimal" -&gt; DECIMAL
+            </tr>
 
-Avro Types with No Impala Equivalent
-------------------------------------
-RECORD, MAP, ARRAY, UNION,  ENUM, FIXED, NULL
+          </thead>
+<tbody class="tbody">
+            <tr class="row">
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e848 ">STRING</td>
 
-Impala Types with No Avro Equivalent
-------------------------------------
-TIMESTAMP
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e851 ">STRING</td>
 
-</code></pre>
+            </tr>
 
-      <p class="p">
-        The Avro specification allows string values up to 2**64 bytes in length. Impala queries
-        for Avro tables use 32-bit integers to hold string lengths. In
-        <span class="keyword">Impala 2.5</span> and higher, Impala truncates <code class="ph codeph">CHAR</code> and
-        <code class="ph codeph">VARCHAR</code> values in Avro tables to (2**31)-1 bytes. If a query encounters
-        a <code class="ph codeph">STRING</code> value longer than (2**31)-1 bytes in an Avro table, the query
-        fails. In earlier releases, encountering such long values in an Avro table could cause a
-        crash.
-      </p>
+            <tr class="row">
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e848 ">STRING</td>
+
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e851 ">CHAR</td>
+
+            </tr>
+
+            <tr class="row">
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e848 ">STRING</td>
+
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e851 ">VARCHAR</td>
+
+            </tr>
+
+            <tr class="row">
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e848 ">INT</td>
+
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e851 ">INT</td>
+
+            </tr>
+
+            <tr class="row">
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e848 ">BOOLEAN</td>
+
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e851 ">BOOLEAN</td>
+
+            </tr>
+
+            <tr class="row">
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e848 ">LONG</td>
+
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e851 ">BIGINT</td>
+
+            </tr>
+
+            <tr class="row">
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e848 ">FLOAT</td>
+
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e851 ">FLOAT</td>
+
+            </tr>
+
+            <tr class="row">
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e848 ">DOUBLE</td>
+
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e851 ">DOUBLE</td>
+
+            </tr>
+
+          </tbody>
+</table>
+</div>
+
+      <p class="p">The Avro specification allows string values up to 2**64 bytes in
+        length. Impala queries for Avro tables use 32-bit integers to hold
+        string lengths. </p>
+
+      <p class="p">In <span class="keyword">Impala 2.5</span> and higher, Impala truncates
+          <code class="ph codeph">CHAR</code> and <code class="ph codeph">VARCHAR</code> values in Avro
+        tables to (2**31)-1 bytes. If a query encounters a
+          <code class="ph codeph">STRING</code> value longer than (2**31)-1 bytes in an Avro
+        table, the query fails. In earlier releases, encountering such long
+        values in an Avro table could cause a crash.</p>
+
+      <p class="p"><strong class="ph b">Logical types:</strong></p>
+
+      
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="avro_data_types__table_ch2_1mj_gjb" class="table" frame="border" border="1" rules="all"><colgroup><col style="width:151.26pt" /><col style="width:149.58pt" /></colgroup><thead class="thead" style="text-align:left;">
+            <tr class="row">
+              <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d25374e969">Avro type</th>
+
+              <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d25374e972">Impala type</th>
+
+            </tr>
+
+          </thead>
+<tbody class="tbody">
+            <tr class="row">
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e969 ">BYTES annotated</td>
+
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e972 ">DECIMAL</td>
+
+            </tr>
+
+            <tr class="row">
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e969 ">INT32 annotated</td>
+
+              <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d25374e972 ">DATE</td>
+
+            </tr>
+
+          </tbody>
+</table>
+</div>
 
+      <p class="p">Impala does not support the following Avro data types: RECORD, MAP,
+        ARRAY, UNION,  ENUM, FIXED, NULL</p>
 
     </div>
 
diff --git a/docs/build/html/topics/impala_batch_size.html b/docs/build/html/topics/impala_batch_size.html
index fbbd290..3fae7b9 100644
--- a/docs/build/html/topics/impala_batch_size.html
+++ b/docs/build/html/topics/impala_batch_size.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="BATCH_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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="batch_size" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_bigint.html b/docs/build/html/topics/impala_bigint.html
index 3c66710..5d24b50 100644
--- a/docs/build/html/topics/impala_bigint.html
+++ b/docs/build/html/topics/impala_bigint.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="BIGINT Data Type" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="bigint" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_bit_functions.html b/docs/build/html/topics/impala_bit_functions.html
index 4688ad9..07baf75 100644
--- a/docs/build/html/topics/impala_bit_functions.html
+++ b/docs/build/html/topics/impala_bit_functions.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Bit 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="bit_functions" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_boolean.html b/docs/build/html/topics/impala_boolean.html
index d2aa53a..17a6a66 100644
--- a/docs/build/html/topics/impala_boolean.html
+++ b/docs/build/html/topics/impala_boolean.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="BOOLEAN Data Type" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="boolean" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_breakpad.html b/docs/build/html/topics/impala_breakpad.html
index 3600775..c9140c9 100644
--- a/docs/build/html/topics/impala_breakpad.html
+++ b/docs/build/html/topics/impala_breakpad.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Breakpad Minidumps for Impala (Impala 2.6 or higher only)" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_troubleshooting.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="breakpad" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_broadcast_bytes_limit.html b/docs/build/html/topics/impala_broadcast_bytes_limit.html
new file mode 100644
index 0000000..09db0e3
--- /dev/null
+++ b/docs/build/html/topics/impala_broadcast_bytes_limit.html
@@ -0,0 +1,76 @@
+<?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 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
+<meta name="DC.Type" content="concept" />
+<meta name="DC.Title" content="BROADCAST_BYTES_LIMIT 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.4.x" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="broadcast_bytes_limit" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>BROADCAST_BYTES_LIMIT Query Option</title>
+</head>
+<body id="broadcast_bytes_limit">
+
+
+    <h1 class="title topictitle1" id="ariaid-title1">BROADCAST_BYTES_LIMIT Query Option</h1>
+
+
+    
+
+    
+
+    <div class="body conbody">
+
+        <p class="p">
+             Sets the limit
+            for the size of the broadcast input based on estimated size.
+        </p>
+
+        <p class="p">
+            The Impala planner may in rare cases make a bad choice to broadcast a large table or intermediate
+            result and encounter performance problems due to high memory pressure. Setting this limit will
+            make the planner pick a partition based hash join instead of broadcast and avoid such performance problems.
+        </p>
+
+        <p class="p">
+        <strong class="ph b">Type:</strong> integer
+      </p>
+
+
+        <p class="p">
+        <strong class="ph b">Default:</strong>
+      </p>
+
+
+        <p class="p">
+            The default value is 34359738368 (32 GB). A value of 0 causes the option to be ignored.
+        </p>
+
+        <p class="p">
+        <strong class="ph b">Examples:</strong>
+      </p>
+
+
+<pre class="pre codeblock"><code>
+-- Change the limit to 16GB.
+set broadcast_bytes_limit=17179869184;
+
+-- Disable the BROADCAST_BYTES_LIMIT.
+set broadcast_bytes_limit=0;
+
+</code></pre>
+    </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
diff --git a/docs/build/html/topics/impala_buffer_pool_limit.html b/docs/build/html/topics/impala_buffer_pool_limit.html
index 37a5b47..191c5d5 100644
--- a/docs/build/html/topics/impala_buffer_pool_limit.html
+++ b/docs/build/html/topics/impala_buffer_pool_limit.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="BUFFER_POOL_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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="buffer_pool_limit" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_char.html b/docs/build/html/topics/impala_char.html
index 27cff29..80d7392 100644
--- a/docs/build/html/topics/impala_char.html
+++ b/docs/build/html/topics/impala_char.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="CHAR Data Type (Impala 2.0 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="char" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_client.html b/docs/build/html/topics/impala_client.html
index 82f8a77..f22fc95 100644
--- a/docs/build/html/topics/impala_client.html
+++ b/docs/build/html/topics/impala_client.html
@@ -4,15 +4,16 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Client Access" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_impala_shell.html" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_odbc.html" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_jdbc.html" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_query_results_spooling.html" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="intro_client" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -24,6 +25,8 @@
   <h1 class="title topictitle1" id="ariaid-title1">Impala Client Access</h1>
 
 
+  
+
   <div class="body conbody">
 
     <p class="p">
@@ -251,6 +254,37 @@
         
 
           <dt class="dt dlterm">
+            --hs2_http_port
+          </dt>
+
+
+          <dd class="dd">
+            Specifies the port for clients to connect to Impala server over HTTP.
+            <p class="p">
+              The default port is 28000.
+            </p>
+
+
+            <p class="p">
+              You can disable the HTTP end point for clients by setting the flag to
+              <code class="ph codeph">0</code>.
+            </p>
+
+
+            <p class="p">
+              To enable TLS/SSL for HiveServer2 HTTP endpoint use
+              <code class="ph codeph">--ssl_server_certificate</code> and <code class="ph codeph">--ssl_private_key</code>.
+              See <a class="xref" href="impala_ssl.html#ssl">Configuring TLS/SSL for Impala</a> for detail.
+            </p>
+
+          </dd>
+
+
+        
+
+        
+
+          <dt class="dt dlterm">
             --idle_client_poll_time_s
           </dt>
 
@@ -288,22 +322,44 @@
         
 
           <dt class="dt dlterm">
-            --hs2_http_port
+            --max_cookie_lifetime_s
           </dt>
 
 
           <dd class="dd">
-            Specifies the port for clients to connect to Impala server over HTTP.
+            Starting in Impala 3.4.0, Impala uses cookies for authentication when clients
+            connect via HiveServer2 over HTTP. Use the <code class="ph codeph">--max_cookie_lifetime_s</code>
+            startup flag to control how long generated cookies are valid for.
             <p class="p">
-              You can disable the HTTP end point for clients by setting the flag to
-              <code class="ph codeph">0</code>.
+              Specify the value in seconds.
+            </p>
+
+            <p class="p">
+              The default value is 1 day.
             </p>
 
 
             <p class="p">
-              To enable TLS/SSL for HiveServer2 HTTP endpoint use
-              <code class="ph codeph">--ssl_server_certificate</code> and <code class="ph codeph">--ssl_private_key</code>.
-              See <a class="xref" href="impala_ssl.html#ssl">Configuring TLS/SSL for Impala</a> for detail.
+              Setting the flag to <code class="ph codeph">0</code> disables cookie support.
+            </p>
+
+
+            <p class="p">
+              When an unexpired cookie is successfully verified, the user name contained in the
+              cookie is set on the connection.
+            </p>
+
+
+            <p class="p">
+              Each <code class="ph codeph">impalad</code> uses its own key to generate the signature, so
+              clients that reconnect to a different <code class="ph codeph">impalad</code> have to
+              re-authenticate.
+            </p>
+
+
+            <p class="p">
+              On a single <code class="ph codeph">impalad</code>, cookies are valid across sessions and
+              connections.
             </p>
 
           </dd>
@@ -327,6 +383,8 @@
 </li>
 <li class="link ulchildlink"><strong><a href="../topics/impala_jdbc.html">Configuring Impala to Work with JDBC</a></strong><br />
 </li>
+<li class="link ulchildlink"><strong><a href="../topics/impala_query_results_spooling.html">Spooling Impala Query Results</a></strong><br />
+</li>
 </ul>
 </div></body>
 </html>
\ No newline at end of file
diff --git a/docs/build/html/topics/impala_comment.html b/docs/build/html/topics/impala_comment.html
index 94196af..86db0a0 100644
--- a/docs/build/html/topics/impala_comment.html
+++ b/docs/build/html/topics/impala_comment.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="COMMENT Statement" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_langref_sql.html" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="comment" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_comments.html b/docs/build/html/topics/impala_comments.html
index 89602f7..a7688fe 100644
--- a/docs/build/html/topics/impala_comments.html
+++ b/docs/build/html/topics/impala_comments.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Comments" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_langref.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="comments" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_complex_types.html b/docs/build/html/topics/impala_complex_types.html
index 93d46db..e03a006 100644
--- a/docs/build/html/topics/impala_complex_types.html
+++ b/docs/build/html/topics/impala_complex_types.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Complex Types (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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="complex_types" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_components.html b/docs/build/html/topics/impala_components.html
index 01c6566..850928e 100644
--- a/docs/build/html/topics/impala_components.html
+++ b/docs/build/html/topics/impala_components.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Components of the Impala Server" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_concepts.html" />
@@ -14,11 +14,11 @@
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="intro_components" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_compression_codec.html b/docs/build/html/topics/impala_compression_codec.html
index 3ee4467..2e9f9bc 100644
--- a/docs/build/html/topics/impala_compression_codec.html
+++ b/docs/build/html/topics/impala_compression_codec.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="COMPRESSION_CODEC Query Option (Impala 2.0 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="compression_codec" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_compute_stats.html b/docs/build/html/topics/impala_compute_stats.html
index 5ae804c..288fe16 100644
--- a/docs/build/html/topics/impala_compute_stats.html
+++ b/docs/build/html/topics/impala_compute_stats.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="COMPUTE STATS 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="compute_stats" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -328,7 +328,7 @@ compute incremental stats int_partitions partition (x != 150);
 
     <p class="p">
       <code class="ph codeph">COMPUTE STATS</code> also works for tables where data resides in the Amazon Simple Storage Service (S3).
-      See <a class="xref" href="impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details.
+      See <a class="xref" href="impala_s3.html#s3">Using Impala with Amazon S3 Object Store</a> for details.
     </p>
 
 
diff --git a/docs/build/html/topics/impala_compute_stats_min_sample_size.html b/docs/build/html/topics/impala_compute_stats_min_sample_size.html
index 18ae008..4bfb5d5 100644
--- a/docs/build/html/topics/impala_compute_stats_min_sample_size.html
+++ b/docs/build/html/topics/impala_compute_stats_min_sample_size.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="COMPUTE_STATS_MIN_SAMPLE_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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="compute_stats_sample_min_sample_size" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_concepts.html b/docs/build/html/topics/impala_concepts.html
index 497309a..609f5bf 100644
--- a/docs/build/html/topics/impala_concepts.html
+++ b/docs/build/html/topics/impala_concepts.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Concepts and Architecture" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_components.html" />
@@ -13,8 +13,8 @@
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_hadoop.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="concepts" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_conditional_functions.html b/docs/build/html/topics/impala_conditional_functions.html
index a4dade7..24e76e1 100644
--- a/docs/build/html/topics/impala_conditional_functions.html
+++ b/docs/build/html/topics/impala_conditional_functions.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Conditional 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="conditional_functions" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_config.html b/docs/build/html/topics/impala_config.html
index 9f97bb3..99dec4a 100644
--- a/docs/build/html/topics/impala_config.html
+++ b/docs/build/html/topics/impala_config.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Managing Impala" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_config_performance.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="config" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_config_options.html b/docs/build/html/topics/impala_config_options.html
index d6a5b82..403b3c0 100644
--- a/docs/build/html/topics/impala_config_options.html
+++ b/docs/build/html/topics/impala_config_options.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Modifying Impala Startup Options" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_processes.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="config_options" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_config_performance.html b/docs/build/html/topics/impala_config_performance.html
index 3d4795f..74d28ff 100644
--- a/docs/build/html/topics/impala_config_performance.html
+++ b/docs/build/html/topics/impala_config_performance.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Post-Installation Configuration for Impala" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_config.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="config_performance" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_connecting.html b/docs/build/html/topics/impala_connecting.html
index 46595e8..02ef89f 100644
--- a/docs/build/html/topics/impala_connecting.html
+++ b/docs/build/html/topics/impala_connecting.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Connecting to Impala Daemon from impala-shell" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_impala_shell.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="connecting" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_conversion_functions.html b/docs/build/html/topics/impala_conversion_functions.html
index 24811b9..c751f27 100644
--- a/docs/build/html/topics/impala_conversion_functions.html
+++ b/docs/build/html/topics/impala_conversion_functions.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Type Conversion 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="conversion_functions" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -24,9 +24,9 @@
   <h1 class="title topictitle1" id="ariaid-title1">Impala Type Conversion Functions</h1>
 
 
+  
 
-
-
+  
 
   <div class="body conbody">
 
@@ -65,7 +65,7 @@
 
 
     <dl class="dl">
-
+      
 
         <dt class="dt dlterm" id="conversion_functions__cast">
           CAST(expression AS type)
@@ -151,10 +151,1482 @@
         </dd>
 
 
+      
+
+      
+
+        <dt class="dt dlterm" id="conversion_functions__cast_format">
+          CAST(expression AS type FORMAT pattern)
+        </dt>
+
+
+        <dd class="dd">
+          <strong class="ph b">Purpose:</strong> Returns <var class="keyword varname">expression</var> converted to the
+          <var class="keyword varname">type</var> data type based on the <var class="keyword varname">pattern</var> format
+          string. This signature of <code class="ph codeph">CAST()</code> with the <code class="ph codeph">FORMAT</code>
+          clause is supported only for casts between <code class="ph codeph">STRING</code> /
+          <code class="ph codeph">CHAR</code> / <code class="ph codeph">VARCHAR</code> types and <code class="ph codeph">TIMESTAMP</code>
+          / <code class="ph codeph">DATE</code> types.
+          <div class="note note"><span class="notetitle">Note:</span> 
+            The patterns allowed in the <code class="ph codeph">FORMAT</code> clause support ISO SQL:2016
+            standard patterns. Those patterns are not the same format patterns used with the
+            other Impala conversion functions, e.g. <code class="ph codeph">TO_TIMESTAMP()</code> and
+            <code class="ph codeph">FROM_TIMESTAMP()</code>.
+          </div>
+
+
+          <div class="p">
+            The following rules apply to <var class="keyword varname">pattern</var>. Any exceptions to these
+            rules are noted in the Details column of the table below.
+            <ul class="ul">
+              <li class="li">
+                <var class="keyword varname">pattern</var> is a case-insensitive <code class="ph codeph">STRING</code> unless
+                noted otherwise in the table below.
+              </li>
+
+
+              <li class="li">
+                If <var class="keyword varname">pattern</var> is <code class="ph codeph">NULL</code>, an empty string, or a
+                number, an error returns.
+              </li>
+
+
+              <li class="li">
+                A fewer digits in <var class="keyword varname">expression</var> than specified in the
+                <var class="keyword varname">pattern</var> is accepted if a separator is correctly specified in
+                the <var class="keyword varname">pattern</var>. For example, <code class="ph codeph">CAST('5-01-2017' AS DATE
+                FORMAT 'MM-dd-yyyy')</code> returns <code class="ph codeph">DATE'2017-05-01'</code>.
+              </li>
+
+
+              <li class="li">
+                If fewer number of digits are in <var class="keyword varname">expression</var> than specified in
+                the <var class="keyword varname">pattern</var>, the current date is used to complete the year
+                pattern. For example, <code class="ph codeph">CAST('19/05' AS DATE FORMAT 'YYYY/MM')</code>
+                will return <code class="ph codeph">DATE'2019-05-01'</code> when executed on August 8, 2019.
+              </li>
+
+            </ul>
+
+          </div>
+
+
+          <div class="p">
+            The following format patterns are supported in the <code class="ph codeph">FORMAT</code> clause.
+            
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="conversion_functions__table_gbt_5ym_r3b" class="table" frame="border" border="1" rules="all"><colgroup><col style="width:10.695187165775401%" /><col style="width:18.71657754010695%" /><col style="width:70.58823529411764%" /></colgroup><thead class="thead" style="text-align:left;">
+                  <tr class="row">
+                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d40515e394">
+                      Pattern
+                    </th>
+
+                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d40515e397">
+                      Description
+                    </th>
+
+                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d40515e400">
+                      Details
+                    </th>
+
+                  </tr>
+
+                </thead>
+<tbody class="tbody">
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">YYYY</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      4-digit year.
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 "> </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">YYY</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Last 3 digits of a year.
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 "> </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">YY</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Last 2 digits of a year.
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 "> </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">Y</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Last digit of a year
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 "> </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">RRRR</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      4-digit round year
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        If 1,3 or 4-digit year values are provided in
+                        <var class="keyword varname">expression</var>, treated as <code class="ph codeph">YYYY</code>.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        If 2-digit years are provided in <var class="keyword varname">expression</var>, treated
+                        as <code class="ph codeph">RR</code>.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        For date/time to string conversions, treated as <code class="ph codeph">YYYY</code>.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        If <code class="ph codeph">YYYY</code>, <code class="ph codeph">YYY</code>, <code class="ph codeph">YY</code>,
+                        <code class="ph codeph">Y</code>, or <code class="ph codeph">RR</code> is given in the same
+                        <var class="keyword varname">pattern</var> for a string to date/time conversion, an
+                        error returns.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">RR</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      2-digit round year.
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        For date/time to string conversions, same as <code class="ph codeph">YY</code>.
+                      </p>
+
+
+
+
+                      <div class="p">
+                        For string to date/time conversions, the first 2 digits of the year in
+                        the return value depends on the specified two-digit year and the last
+                        two digits of the current year as follows:
+                        <ul class="ul">
+                          <li class="li">
+                            <p class="p">
+                              If the specified 2-digit year is 00 to 49:
+                            </p>
+
+                            <ul class="ul">
+                              <li class="li">
+                                <p class="p">
+                                  If the last 2 digits of the current year are 00 to 49, the
+                                  returned year has the same first 2 digits as the current year.
+                                </p>
+
+                              </li>
+
+
+                              <li class="li">
+                                <p class="p">
+                                  If the last 2 digits of the current year are 50 to 99, the
+                                  first 2 digits of the returned year are 1 greater than the
+                                  first 2 digits of the current year.
+                                </p>
+
+                              </li>
+
+                            </ul>
+
+                          </li>
+
+
+                          <li class="li">
+                            <p class="p">
+                              If the specified 2-digit year is 50 to 99:
+                            </p>
+
+                            <ul class="ul">
+                              <li class="li">
+                                <p class="p">
+                                  If the last 2 digits of the current year are 00 to 49, the
+                                  first 2 digits of the returned year are 1 less than the first
+                                  2 digits of the current year.
+                                </p>
+
+                              </li>
+
+
+                              <li class="li">
+                                <p class="p">
+                                  If the last 2 digits of the current year are 50 to 99, the
+                                  returned year has the same first 2 digits as the current year.
+                                </p>
+
+                              </li>
+
+                            </ul>
+
+                          </li>
+
+                        </ul>
+
+                      </div>
+
+
+
+
+                      <p class="p">
+                        If <code class="ph codeph">YYYY</code>, <code class="ph codeph">YYY</code>, <code class="ph codeph">YY</code>,
+                        <code class="ph codeph">Y</code>, or <code class="ph codeph">RR</code> is given in the same
+                        <var class="keyword varname">pattern</var> for a string to date/time conversion, an
+                        error returns.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        If 1-digit year values are provided in <var class="keyword varname">expression</var>, it
+                        is treated as <code class="ph codeph">YYYY</code>.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">Q</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Quarter of year (1-4)
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        Not supported in string to date/time conversions.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">MM</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Month number
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p"> In date/time to string conversions, 1-digit months are
+                        prefixed with a zero. </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">MONTH</code>
+
+                      <p class="p">
+                        <code class="ph codeph">Month</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">month</code>
+                      </p>
+
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Full month name
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      In string to date/time conversions:
+
+                      <ul class="ul">
+                        <li class="li"> Converts a textual month name to a 2-digit month
+                          number. </li>
+
+
+                        <li class="li">
+                          The input strings are expected without trailing spaces, e.g.
+                          "<code class="ph codeph">June</code>", "<code class="ph codeph">August</code>".
+                        </li>
+
+
+                        <li class="li">
+                          If the <code class="ph codeph">FX</code> modifier is active for the token, a
+                          9-character-long full month name with trailing spaces is expected for
+                          the input string.
+                        </li>
+
+                      </ul>
+
+
+                      <div class="p">
+                        In date/time to string conversions:
+                        <ul class="ul">
+                          <li class="li">
+                            Converts to a 9-character-long full month name with trailing spaces.
+                          </li>
+
+
+                          <li class="li">
+                            If the <code class="ph codeph">FM</code> modifier is active for this token,
+                            converts to a month name without trailing spaces.
+                          </li>
+
+                        </ul>
+
+                      </div>
+
+
+
+
+                      <p class="p">
+                        This pattern token is case sensitive. <code class="ph codeph">MONTH</code>,
+                        <code class="ph codeph">Month</code>, <code class="ph codeph">month</code> would require different
+                        casing of the input in string to date/time conversions and would produce
+                        cased outputs in date/time to string conversions, For example,
+                        <code class="ph codeph">MONTH</code>, <code class="ph codeph">Month</code>, <code class="ph codeph">month</code>
+                        would convert respectively <code class="ph codeph">JULY</code>, <code class="ph codeph">July</code>,
+                        and <code class="ph codeph">july</code>.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">MON</code>
+
+                      <p class="p">
+                        <code class="ph codeph">Mon</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">mon</code>
+                      </p>
+
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Abbreviated 3-character month name
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        This pattern token is case sensitive. <code class="ph codeph">MON</code>,
+                        <code class="ph codeph">Mon</code>, <code class="ph codeph">mon</code> would require different
+                        casing of the input in string to date/time conversions and would produce
+                        cased outputs in date/time to string conversions, For example,
+                        <code class="ph codeph">MON</code>, <code class="ph codeph">Mon</code>, <code class="ph codeph">mon</code> would
+                        convert respectively <code class="ph codeph">JUL</code>, <code class="ph codeph">Jul</code>, and
+                        <code class="ph codeph">jul</code>.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">WW</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Week of year (1-53)
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p"> Not supported in string to date/time conversions. </p>
+
+
+
+
+                      <p class="p"> The 1st week begins on January 1st and ends on January
+                        7th. </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">W</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Week of month (1-5)
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        Not supported in string to date/time conversions.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        1st week begins on the 1st of the month and ends on the 7th.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">D</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Day of week (1-7)
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        Not supported in string to date/time conversions.
+                      </p>
+
+
+                      In date/time to string conversions, converts to a day number, for example,
+                      1 for Sunday, 2 for Monday.
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">DD</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Day of month (1-31)
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p"> In date/time to string conversions, 1-digit days are
+                        prefixed with a zero. </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">DDD</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Day of year (1-366)
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        In string to date/time conversions, providing <code class="ph codeph">MM</code> and
+                        <code class="ph codeph">DD</code> along with <code class="ph codeph">DDD</code> results an error,
+                        e.g. <code class="ph codeph">YYYY-MM-DDD</code>.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">DAY</code>
+
+                      <p class="p">
+                        <code class="ph codeph">Day</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">day</code>
+                      </p>
+
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Day name
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        Not supported in string to date/time conversions.
+                      </p>
+
+
+
+
+                      <div class="p">
+                        In date/time to string conversions:
+                        <ul class="ul">
+                          <li class="li">
+                            Converts to a 9-character-long full day name with trailing spaces.
+                          </li>
+
+
+                          <li class="li">
+                            If the <code class="ph codeph">FM</code> modifier is active for this token,
+                            converts to a day name without trailing spaces.
+                          </li>
+
+                        </ul>
+
+                      </div>
+
+
+
+
+                      <p class="p">
+                        This pattern token is case sensitive. <code class="ph codeph">DAY</code>,
+                        <code class="ph codeph">Day</code>, <code class="ph codeph">day</code> would produce cased outputs
+                        in date/time to string conversions, For example, <code class="ph codeph">DAY</code>,
+                        <code class="ph codeph">Day</code>, <code class="ph codeph">day</code> would convert respectively
+                        <code class="ph codeph">MONDAY</code>, <code class="ph codeph">Monday</code>, and
+                        <code class="ph codeph">monday</code>.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">DY</code>
+
+                      <p class="p">
+                        <code class="ph codeph">Dy</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">dy</code>
+                      </p>
+
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Abbreviated 3-character day name
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        Not supported in string to date/time conversions.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        This pattern token is case sensitive. <code class="ph codeph">DY</code>,
+                        <code class="ph codeph">Dy</code>, <code class="ph codeph">dy</code> would produce cased outputs in
+                        date/time to string conversions, For example, <code class="ph codeph">DY</code>,
+                        <code class="ph codeph">Dy</code>, <code class="ph codeph">dy</code> would convert respectively
+                        <code class="ph codeph">MON</code>, <code class="ph codeph">Mon</code>, and <code class="ph codeph">mon</code>.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">HH</code>
+
+                      <p class="p">
+                        <code class="ph codeph">HH12</code>
+                      </p>
+
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Hour of day (1-12)
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        In date/time to string conversions, 1-digit hours are prefixed with a
+                        zero.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        If provided hour in <var class="keyword varname">expression</var> is not between 1 and
+                        12, returns an error.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        If no AM/PM is provided in <var class="keyword varname">expression</var>, the default is
+                        <code class="ph codeph">AM</code>.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">HH24</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Hour of day (0-23)
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        In string to date/time conversions, if <code class="ph codeph">HH12</code>,
+                        <code class="ph codeph">AM</code>, <code class="ph codeph">PM</code> are given in the same
+                        <var class="keyword varname">pattern</var>, an error returns.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">MI</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Minute of hour (0-59)
+                    </td>
 
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        In date/time to string conversions, 1-digit minutes are prefixed with a
+                        zero.
+                      </p>
 
+                    </td>
 
+                  </tr>
 
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">SS</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Second of minute (0-59)
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        In date/time to string conversions, 1-digit seconds are prefixed with a
+                        zero.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">SSSSS</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Second of Day (0-86399)
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        In string to timestamp conversions, if <code class="ph codeph">SS</code>,
+                        <code class="ph codeph">HH</code>, <code class="ph codeph">HH12</code>, <code class="ph codeph">HH24</code>,
+                        <code class="ph codeph">MI</code>, <code class="ph codeph">AM</code>/<code class="ph codeph">PM</code> are given
+                        in the same <var class="keyword varname">pattern</var>, an error returns.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">FF</code>
+
+                      <p class="p">
+                        <code class="ph codeph">FF1</code>, ..., <code class="ph codeph">FF9</code>
+                      </p>
+
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Fractional second
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        A number, 1 to 9, can be used to indicate the number of digits.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">FF</code> specifies a 9 digits fractional second.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">AM</code>
+
+                      <p class="p">
+                        <code class="ph codeph">PM</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">A.M.</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">P.M.</code>
+                      </p>
+
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Meridiem indicator
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        For date/time to string conversions, <code class="ph codeph">AM</code> and
+                        <code class="ph codeph">PM</code> are treated as synonyms. For example, casting
+                        <code class="ph codeph">'2019-01-01 11:00 am'</code> to <code class="ph codeph">TIMESTAMP</code>
+                        with the <code class="ph codeph">'YYYY-MM-DD HH12:MI PM'</code> pattern returns
+                        <code class="ph codeph">01-JAN-19 11.00.00.000000 AM</code>.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        For string to date/time conversion, <code class="ph codeph">HH24</code> in the same
+                        <var class="keyword varname">pattern</var> returns an error.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">TZH</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Timezone offset hour
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        An optional sign, + or -, and 2 digits for the value of signed numbers
+                        are allowed for the source <var class="keyword varname">expression</var>, e.g.
+                        <code class="ph codeph">+10</code>, <code class="ph codeph">-05</code>, <code class="ph codeph">04</code>.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        The allowed values are from <code class="ph codeph">-15</code> to <code class="ph codeph">+5</code>.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">TZM</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Timezone offset minute
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        Unsigned numbers are allowed for the source
+                        <var class="keyword varname">expression</var>.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        The allowed values are from <code class="ph codeph">0</code> to <code class="ph codeph">59</code>.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">-</code>
+
+                      <p class="p">
+                        <code class="ph codeph">.</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">/</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">,</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">'</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">;</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        <code class="ph codeph">:</code>
+                      </p>
+
+
+
+
+                      <p class="p">
+                        &lt;space&gt;
+                      </p>
+
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Separator
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        For string to date/time conversions, any separator character in the
+                        <var class="keyword varname">pattern</var> string would match any separator character in
+                        the input <var class="keyword varname">expression</var>.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        For example, <code class="ph codeph">CAST(“20191010” AS DATE FORMAT
+                        “YYYY-MM-DD”)</code> returns an error, but <code class="ph codeph">CAST("2019-.;10
+                        10" AS DATE FORMAT "YYYY-MM-DD")</code> succeeds.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">T</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Separates the date from the time.
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        This pattern is used for accepting ISO 8601 date/time formats.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        Example: <code class="ph codeph">YYYY-MM-DD<strong class="ph b">T</strong>HH24:MI:SS.FF9Z</code>
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">Z</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Indicates the zero hour offset from UTC.
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        This pattern is used for accepting ISO 8601 date/time formats.
+                      </p>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">FX</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Forces an exact match between the format pattern,
+                      <var class="keyword varname">pattern</var>, and the input argument,
+                      <var class="keyword varname">expression</var>.
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        Must be specified at the beginning of the format
+                        <var class="keyword varname">pattern</var> and is valid for the whole
+                        <var class="keyword varname">pattern</var>.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        In string to date/time conversions:
+                      </p>
+
+
+                      <ul class="ul">
+                        <li class="li">
+                          Forces strict separator matching, including the separator character.
+                        </li>
+
+
+                        <li class="li">
+                          Expects all the tokens to have the maximum possible length.
+                        </li>
+
+                      </ul>
+
+
+                      <p class="p">
+                        In date/time to string conversions, the outputs are padded as follows:
+                      </p>
+
+
+                      <ul class="ul">
+                        <li class="li">
+                          Numeric outputs are left padded with zeros.
+                        </li>
+
+
+                        <li class="li">
+                          Text outputs are right padded with spaces.
+                        </li>
+
+                      </ul>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      <code class="ph codeph">FM</code>
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Overrides <code class="ph codeph">FX</code>.
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        In a date/time to string conversions, <code class="ph codeph">FM</code> suppresses
+                        blank padding for the element immediately following the
+                        <code class="ph codeph">FM</code> in the <var class="keyword varname">pattern</var> string, e.g.
+                        "<code class="ph codeph">2010-1-9</code>".
+                      </p>
+
+
+
+
+                      <div class="p">
+                        In string to date/time conversions, <code class="ph codeph">FM</code> is used to
+                        override the effect of <code class="ph codeph">FX</code> for certain tokens as
+                        follows:
+                        <ul class="ul">
+                          <li class="li">
+                            <p class="p">
+                              The length of the token in the input argument can be shorter than
+                              the max length of that token type if followed by a separator, e.g.
+                              1-digit month, less than 4-digit year.
+                            </p>
+
+                          </li>
+
+
+                          <li class="li">
+                            <p class="p">
+                              <code class="ph codeph">FM</code> modifier skips the separators and affects the
+                              next non-separator token. For example, <code class="ph codeph">CAST('1999-10-2' AS
+                              TIMESTAMP FORMAT 'FXYYYY-MM<strong class="ph b">FM</strong>-DD') </code>returns
+                              <code class="ph codeph">1999-10-02 00:00:00</code> as <code class="ph codeph">FM</code> is
+                              applied to <code class="ph codeph">DD</code> and not to the
+                              separator(<code class="ph codeph">-</code>).
+                            </p>
+
+                          </li>
+
+                        </ul>
+
+                      </div>
+
+                    </td>
+
+                  </tr>
+
+                  <tr class="row">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e394 ">
+                      Free text
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e397 ">
+                      Nested string
+                    </td>
+
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e400 ">
+                      <p class="p">
+                        You can specify a free text with surrounding double quotes (") in
+                        <var class="keyword varname">pattern</var> where the same text is expected in the input
+                        argument without surrounding double quotes.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        In date/time to string conversions, the string is included in the output
+                        with the characters' case preserved.
+                      </p>
+
+
+
+
+                      <p class="p">
+                        In string to date/time conversions, the nested string is not included in
+                        the resulting date/time object. However, the nested string has to match
+                        the related part of the input string, including the case.
+                      </p>
+
+
+
+
+                      <div class="p">
+                        The following rules apply:
+                        <ul class="ul">
+                          <li class="li">
+                            <p class="p">
+                              If the <var class="keyword varname">pattern</var> is surrounded by double quotes,
+                              double quotes surrounding the free text token must be escaped with
+                              a single backslash (<code class="ph codeph">\"</code>).
+                            </p>
+
+
+                            <p class="p">
+                              For example: <code class="ph codeph">CAST('"Date:"2019-11-10' AS DATE FORMAT
+                              "<strong class="ph b">\"Date:\"</strong>YYYY-MM-DD")</code>
+                            </p>
+
+                          </li>
+
+
+                          <li class="li">
+                            <p class="p">
+                              If the <var class="keyword varname">pattern</var> is surrounded by double quotes,
+                              and there is an escaped double quotes inside a text token that is
+                              itself surrounded by escaped double quotes, escape the double
+                              quotes in the free text token with a triple backslash:
+                              (<code class="ph codeph">\\\"</code>)
+                            </p>
+
+
+                            <p class="p">
+                              For example: <code class="ph codeph">CAST("1985 some \"text 11-28" AS DATE'''
+                              FORMAT "YYYY<strong class="ph b">\" some \\\"text \"</strong>MM-DD")</code>
+                            </p>
+
+                          </li>
+
+
+                          <li class="li">
+                            <p class="p">
+                              If the <var class="keyword varname">pattern</var> is surrounded by single quotes,
+                              the free text token can be surrounded by (non-escaped) double
+                              quotes. To include double quotes within the free text token, those
+                              double quotes must be escaped by a single backslash.
+                            </p>
+
+
+                            <p class="p">
+                              For example: <code class="ph codeph">CAST('"Date:"2019-11-10' AS DATE FORMAT
+                              '"<strong class="ph b">\"Date:\"</strong>"YYYY-MM-DD')</code>
+                            </p>
+
+                          </li>
+
+
+                          <li class="li">
+                            <p class="p">
+                              Literal single quotes/apostrophes (<code class="ph codeph">'</code>) in the
+                              nested string must be escaped with a single backslash if the whole
+                              pattern string is delimited by single quotes.
+                            </p>
+
+                          </li>
+
+
+                          <li class="li">
+                            <p class="p">
+                              If a free text token contains any separator characters in the
+                              beginning, and the text token is right after a separator token
+                              sequence, an error returns as it's not trivial to find where the
+                              separator sequence ends and where the free text starts. In this
+                              case, use <code class="ph codeph">FX</code> for strict matching.
+                            </p>
+
+
+                            <p class="p">
+                              For example: <code class="ph codeph">CAST("1985-11- ' 10" AS DATE FORMAT
+                              "YYYY-MM-<strong class="ph b">\" ' \"</strong>DD")</code> returns an error, but
+                              removing the dash before the text token makes this succeed.
+                            </p>
+
+                          </li>
+
+                        </ul>
+
+                      </div>
+
+                    </td>
+
+                  </tr>
+
+                </tbody>
+</table>
+</div>
+
+          </div>
+
+
+          <p class="p">
+            <strong class="ph b">Examples:</strong>
+          </p>
+
+          
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="conversion_functions__table_qqg_txn_r3b" class="table" frame="border" border="1" rules="all"><colgroup><col style="width:50%" /><col style="width:50%" /></colgroup><thead class="thead" style="text-align:left;">
+                <tr class="row">
+                  <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d40515e1766">
+                    Input
+                  </th>
+
+                  <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d40515e1769">
+                    Output
+                  </th>
+
+                </tr>
+
+              </thead>
+<tbody class="tbody">
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST("02-11-2014" AS DATE FORMAT 'dd-mm-yyyy')</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    2014-11-02
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST("365 2014" AS DATE FORMAT 'DDD-YYYY')</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    2014-12-31
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST("5-01-26" AS DATE FORMAT 'YY-MM-DD')</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    Executed at 2019-01-01 11:11:11:
+
+                    <p class="p">
+                      2015-01-26
+                    </p>
+
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST('2018-11-10T15:11:04Z' AS TIMESTAMP
+   FORMAT 'YYYY-MM-DDTHH24:MI:SSZ')</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    2018-11-10 15:11:04
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST("95-01-28" AS DATE
+   FORMAT 'YYY-MM-DD')</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    Executed at 2019-01-01 11:11:11:
+
+                    <p class="p">
+                      2095-01-28
+                    </p>
+
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST("49-01-15" AS DATE 
+   FORMAT 'RR-MM-DD')</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    Round year when last 2 digits of current year is greater than 49.
+
+                    <p class="p">
+                      Executed at 2099-01-01 11:11:11:
+                    </p>
+
+
+
+
+                    <p class="p">
+                      2149-01-15
+                    </p>
+
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST('2019.10.10 13:30:40.123456 +01:30'
+   AS TIMESTAMP
+   FORMAT 'YYYY-MM-DD HH24:MI:SS.FF9 TZH:TZM') </code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    2019-10-10 13:30:40.123456000
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST('2001-03-01 03:10:15.123456 -01:30'
+   AS TIMESTAMP
+   FORMAT 'FXYYYY-MM-DD HH12:MI:SS.FF6 TZH:TZM')</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    2001-03-01 03:10:15.123456000
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST('2001-03-02 03:10:15'
+   AS TIMESTAMP
+   FORMAT 'FXYYYY MM-DD HH12:MI:SS')</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    NULL because the separator between the year and month do not match.
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST('2001-3-05'
+   AS TIMESTAMP
+   FORMAT 'FXYYYY-MM-DD')</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    NULL because the length of the month token does not match the
+                    <var class="keyword varname">pattern</var>.
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST('2001-3-11 3:15:00.12345'
+   AS TIMESTAMP
+   FORMAT 'FXYYYY-FMMM-DD FMHH12:MI:SS.FMFF')</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    2001-03-11 03:15:00.123450000
+
+                    <p class="p">
+                      The multiple <code class="ph codeph">FM</code> modifiers for the month and hour override
+                      the <code class="ph codeph">FX</code> and suppress padding.
+                    </p>
+
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST('2019-01-01 01:01:01'
+   AS TIMESTAMP
+   FORMAT 'FMHH12:MI:FMSS')</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    1:01:1
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1766 ">
+<pre class="pre codeblock"><code>CAST('Date: 2019-11-10'
+   AS DATE
+   FORMAT '"Date: "YYYY-MM-DD')
+</code></pre>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d40515e1769 ">
+                    2019-11-10
+                  </td>
+
+                </tr>
+
+              </tbody>
+</table>
+</div>
+
+        </dd>
+
+
+      
+
+      
 
         <dt class="dt dlterm" id="conversion_functions__typeof">
           TYPEOF(expression)
@@ -199,7 +1671,7 @@
         </dd>
 
 
-
+      
     </dl>
 
 
@@ -211,4 +1683,4 @@
 <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>
+</html>
\ No newline at end of file
diff --git a/docs/build/html/topics/impala_count.html b/docs/build/html/topics/impala_count.html
index a18d9de..96eb5f3 100644
--- a/docs/build/html/topics/impala_count.html
+++ b/docs/build/html/topics/impala_count.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="COUNT 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="count" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_create_database.html b/docs/build/html/topics/impala_create_database.html
index 684ee4d..08fca5d 100644
--- a/docs/build/html/topics/impala_create_database.html
+++ b/docs/build/html/topics/impala_create_database.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="CREATE DATABASE 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="create_database" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -170,7 +170,7 @@ show functions in _impala_builtins like '*<var class="keyword varname">substring
         PARTITION</code> can create or remove folders as needed in the Amazon S3 system. Prior
         to <span class="keyword">Impala 2.6</span>, you had to create folders yourself and point
         Impala database, tables, or partitions at them, and manually remove folders when no
-        longer needed. See <a class="xref" href="../shared/../topics/impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details about reading
+        longer needed. See <a class="xref" href="../shared/../topics/impala_s3.html#s3">Using Impala with Amazon S3 Object Store</a> for details about reading
         and writing S3 data with Impala.
       </p>
 
diff --git a/docs/build/html/topics/impala_create_function.html b/docs/build/html/topics/impala_create_function.html
index 8d47c55..ed46747 100644
--- a/docs/build/html/topics/impala_create_function.html
+++ b/docs/build/html/topics/impala_create_function.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="CREATE FUNCTION 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="create_function" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_create_role.html b/docs/build/html/topics/impala_create_role.html
index 858af49..6ea16bb 100644
--- a/docs/build/html/topics/impala_create_role.html
+++ b/docs/build/html/topics/impala_create_role.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="CREATE ROLE Statement (Impala 2.0 or higher only)" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="create_role" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_create_table.html b/docs/build/html/topics/impala_create_table.html
index 26c60b5..691eb9e 100644
--- a/docs/build/html/topics/impala_create_table.html
+++ b/docs/build/html/topics/impala_create_table.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="CREATE TABLE 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="create_table" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -81,6 +81,7 @@
 
 <pre class="pre codeblock"><code>CREATE [EXTERNAL] TABLE [IF NOT EXISTS] [<var class="keyword varname">db_name</var>.]<var class="keyword varname">table_name</var>
   (<var class="keyword varname">col_name</var> <var class="keyword varname">data_type</var>
+    [<var class="keyword varname">constraint_specification</var>]
     [COMMENT '<var class="keyword varname">col_comment</var>']
     [, ...]
   )
@@ -138,6 +139,13 @@ array_type: ARRAY &lt; <var class="keyword varname">primitive_or_complex_type</v
 
 map_type: MAP &lt; <var class="keyword varname">primitive_type</var>, <var class="keyword varname">primitive_or_complex_type</var> &gt;
 </span>
+
+constraint_specification:
+  PRIMARY KEY (<var class="keyword varname">col_name</var>, ...) [DISABLE] [NOVALIDATE] [RELY], [<var class="keyword varname">foreign_key_specification</var>, ...]
+
+foreign_key_specification:
+  FOREIGN KEY (<var class="keyword varname">col_name</var>, ...) REFERENCES table_name(<var class="keyword varname">col_name</var>, ...) [DISABLE] [NOVALIDATE] [RELY]
+
 row_format:
   DELIMITED [FIELDS TERMINATED BY '<var class="keyword varname">char</var>' [ESCAPED BY '<var class="keyword varname">char</var>']]
   [LINES TERMINATED BY '<var class="keyword varname">char</var>']
@@ -178,7 +186,7 @@ data_type:
 </code></pre>
 
     <p class="p">
-      <strong class="ph b">Kudu tables:</strong>
+      <strong class="ph b">Internal Kudu tables:</strong>
     </p>
 
 
@@ -237,12 +245,54 @@ range_comparison_operator ::= { &lt; | &lt;= }
     </p>
 
 
+    <p class="p">In Impala 3.4 and earlier, you can create an external Kudu table based on a pre-existing Kudu
+      schema using the table property <code class="ph codeph">'kudu.table_name'='internal_kudu_name'</code>. </p>
+
+
+<pre class="pre codeblock"><code>CREATE EXTERNAL TABLE [IF NOT EXISTS] [<var class="keyword varname">db_name</var>.]<var class="keyword varname">table_name</var>
+  [COMMENT '<var class="keyword varname">col_comment</var>']
+  STORED AS KUDU
+  [TBLPROPERTIES ('<var class="keyword varname">kudu.table.name</var>'='<var class="keyword varname">internal_kudu_name</var>', '<var class="keyword varname">key1</var>'='<var class="keyword varname">value1</var>',...)]
+</code></pre>
+
+    <p class="p">Alternatively, in Impala 3.4 and higher, you can also create an external Kudu table as follows:</p>
+
+
 <pre class="pre codeblock"><code>CREATE EXTERNAL TABLE [IF NOT EXISTS] [<var class="keyword varname">db_name</var>.]<var class="keyword varname">table_name</var>
+  (<var class="keyword varname">col_name</var> <var class="keyword varname">data_type</var>
+  [<var class="keyword varname">kudu_column_attribute</var> ...]
+  [COMMENT '<var class="keyword varname">col_comment</var>']
+  [, ...]
+  [PRIMARY KEY (<var class="keyword varname">col_name</var>[, ...])]
+  )
+  [PARTITION BY <var class="keyword varname">kudu_partition_clause</var>]
   [COMMENT '<var class="keyword varname">table_comment</var>']
   STORED AS KUDU
-  [TBLPROPERTIES ('kudu.table_name'='<var class="keyword varname">internal_kudu_name</var>')]
+  [TBLPROPERTIES ('external.table.purge'='true', '<var class="keyword varname">key1</var>'='<var class="keyword varname">value1</var>',...)]
 </code></pre>
 
+    <ul class="ul">
+      <li class="li">Use a Hive metastore (HMS) 3 or later.</li>
+
+      <li class="li">Provide column specifications to define the schema when you create the table, similar to
+        creating an internal table. </li>
+
+      <li class="li">Omit the <code class="ph codeph">kudu.table_name</code> table property as there is no pre-existing
+        schema. </li>
+
+      <li class="li">Include the required <code class="ph codeph">external.table.purge</code> property.</li>
+
+    </ul>
+
+
+    <p class="p"> Only the schema metadata is stored in HMS when you create an external table; however, using
+      this create table syntax, drop table on the Kudu external table deletes the data stored
+      outside HMS in Kudu as well as the metadata (schema) inside HMS. Likewise, renaming the table
+      changes the name of the table in HMS and in Kudu. Kudu synchronizes changes to the actual data
+      and metadata; consequently, operations such as dropping a table or altering a table name
+      simulate internal table operations. </p>
+
+
     <p class="p">
       <strong class="ph b">CREATE TABLE AS SELECT for Kudu tables:</strong>
     </p>
@@ -282,14 +332,39 @@ AS
     </p>
 
 
+    <p class="p"> With the basic <code class="ph codeph">CREATE TABLE</code> syntax, you must list one or more columns, its
+      name, type, optionally constraints, and optionally a comment, in addition to any columns used
+      as partitioning keys. There is one exception where the column list is not required: when
+      creating an Avro table with the <code class="ph codeph">STORED AS AVRO</code> clause, you can omit the list
+      of columns and specify the same metadata as part of the <code class="ph codeph">TBLPROPERTIES</code> clause. </p>
+
+
     <p class="p">
-      With the basic <code class="ph codeph">CREATE TABLE</code> syntax, you must list one or more columns,
-      its name, type, and optionally a comment, in addition to any columns used as partitioning
-      keys. There is one exception where the column list is not required: when creating an Avro
-      table with the <code class="ph codeph">STORED AS AVRO</code> clause, you can omit the list of columns
-      and specify the same metadata as part of the <code class="ph codeph">TBLPROPERTIES</code> clause.
+      <strong class="ph b">Constraints:</strong>
     </p>
 
+    <div class="p">Constraints are advisory and intended for estimating cardinality during query planning in a
+      future release; there is no attempt to enforce constraints. Add primary and foreign key
+      information after column definitions. Do not include a constraint name; the constraint name is
+      generated internally as a UUID. The following constraint states are supported: <ul class="ul" id="create_table__ul_gbz_3kl_4kb">
+        <li class="li">DISABLE</li>
+
+        <li class="li">NOVALIDATE</li>
+
+        <li class="li">RELY</li>
+
+      </ul>
+The ENABLE, VALIDATE, and NORELY options are not supported. The foreign key must be
+      defined as the primary key in the referenced table. </div>
+
+    <div class="p"> Constraint examples: <pre class="pre codeblock"><code>CREATE TABLE pk(col1 INT, col2 STRING, PRIMARY KEY(col1, col2));</code></pre>
+      <pre class="pre codeblock"><code>CREATE TABLE fk(id INT, col1 INT, col2 STRING, PRIMARY KEY(id),
+  FOREIGN KEY(col1, col2) REFERENCES pk(col1, col2));</code></pre>
+      <pre class="pre codeblock"><code>CREATE TABLE pk(id INT, PRIMARY KEY(id) DISABLE, NOVALIDATE, RELY);</code></pre>
+      <pre class="pre codeblock"><code>CREATE TABLE fk(id INT, col1 INT, col2 STRING, PRIMARY KEY(id),
+  FOREIGN KEY(col1, col2) REFERENCES pk(col1, col2));</code></pre>
+    </div>
+
 
     <p class="p">
         <strong class="ph b">Complex type considerations:</strong>
@@ -331,15 +406,12 @@ AS
     </p>
 
 
-    <p class="p">
-      By default, Impala creates an <span class="q">"internal"</span> table, where Impala manages the underlying
-      data files for the table, and physically deletes the data files when you drop the table.
-      If you specify the <code class="ph codeph">EXTERNAL</code> clause, Impala treats the table as an
-      <span class="q">"external"</span> table, where the data files are typically produced outside Impala and
-      queried from their original locations in HDFS, and Impala leaves the data files in place
-      when you drop the table. For details about internal and external tables, see
-      <a class="xref" href="impala_tables.html#tables">Overview of Impala Tables</a>.
-    </p>
+    <p class="p"> By default, Impala creates an internal table, where Impala manages the underlying data files
+      for the table, and physically deletes the data files when you drop the table. If you specify
+      the <code class="ph codeph">EXTERNAL</code> clause, Impala treats the table as an <span class="q">"external"</span> table,
+      where the data files are typically produced outside Impala and queried from their original
+      locations in HDFS, and Impala leaves the data files in place when you drop the table. For
+      details about internal and external tables, see <a class="xref" href="impala_tables.html#tables">Overview of Impala Tables</a>. </p>
 
 
     <p class="p">
@@ -578,8 +650,8 @@ CREATE TABLE kudu_t3 (id BIGINT, year INT, s STRING,
 </code></pre>
 
     <p class="p">
-      Here is an example of creating an external Kudu table:
-    </p>
+      Here is an example of creating an external Kudu table based on an pre-existing table
+      identified by the table property: </p>
 
 
 <pre class="pre codeblock"><code>
@@ -592,6 +664,39 @@ CREATE EXTERNAL TABLE external_t1 STORED AS KUDU
 </code></pre>
 
     <p class="p">
+      In Impala 3.4 and higher, by default HMS implicitly translates internal Kudu tables to
+      external Kudu tables with the 'external.table.purge' property set to true. You can explicitly
+      create such external Kudu tables similar to the way you create internal Kudu tables. You must
+      set the table property <code class="ph codeph">'external.table.purge'</code> to true. Here is an example of
+      creating an external Kudu table:
+    </p>
+
+
+<pre class="pre codeblock"><code>CREATE EXTERNAL TABLE myextkudutbl (
+  id int PRIMARY KEY,
+  name string)
+  PARTITION BY HASH PARTITIONS 8
+  STORED AS KUDU
+  TBLPROPERTIES ('external.table.purge'='true');
+</code></pre>
+    <p class="p">
+      Operations on the resulting external table in Impala, HMS, and Kudu table metadata is 
+      synchronized. HMS-Kudu integration does not need to be enabled for external table 
+      synchronization. Such synchronized tables behave similar to internal tables. For example, 
+      dropping a table removes the underlying Kudu table data as well as the table metadata in HMS. 
+    </p>
+
+    <p class="p">
+      If you want to drop only the HMS metadata and not drop the Kudu table, you
+      can set <code class="ph codeph">external.table.purge</code> to false, as shown in the following example:
+    </p>
+
+
+<pre class="pre codeblock"><code>
+  ALTER TABLE myextkudutbl set tblproperties('external.table.purge'='false');
+</code></pre>
+
+    <p class="p">
       Here is an example of <code class="ph codeph">CREATE TABLE AS SELECT</code> syntax for a Kudu table:
     </p>
 
@@ -1457,7 +1562,7 @@ ERROR: AnalysisException: Partition column name mismatch: year != month
         PARTITION</code> can create or remove folders as needed in the Amazon S3 system. Prior
         to <span class="keyword">Impala 2.6</span>, you had to create folders yourself and point
         Impala database, tables, or partitions at them, and manually remove folders when no
-        longer needed. See <a class="xref" href="../shared/../topics/impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details about reading
+        longer needed. See <a class="xref" href="../shared/../topics/impala_s3.html#s3">Using Impala with Amazon S3 Object Store</a> for details about reading
         and writing S3 data with Impala.
       </p>
 
diff --git a/docs/build/html/topics/impala_create_view.html b/docs/build/html/topics/impala_create_view.html
index 73ec9fe..3f69474 100644
--- a/docs/build/html/topics/impala_create_view.html
+++ b/docs/build/html/topics/impala_create_view.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="CREATE VIEW 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="create_view" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_custom_timezones.html b/docs/build/html/topics/impala_custom_timezones.html
index d5250ca..a8e4bb2 100644
--- a/docs/build/html/topics/impala_custom_timezones.html
+++ b/docs/build/html/topics/impala_custom_timezones.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Customizing Time Zones" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_timestamp.html" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="custom_timezone" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_data_cache.html b/docs/build/html/topics/impala_data_cache.html
index a7c98bf..7c53815 100644
--- a/docs/build/html/topics/impala_data_cache.html
+++ b/docs/build/html/topics/impala_data_cache.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Data Cache for Remote Reads" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_performance.html" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="data_cache" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_databases.html b/docs/build/html/topics/impala_databases.html
index 68c491d..7df4444 100644
--- a/docs/build/html/topics/impala_databases.html
+++ b/docs/build/html/topics/impala_databases.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Overview of Impala Databases" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_schema_objects.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="databases" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_datatypes.html b/docs/build/html/topics/impala_datatypes.html
index 6dd18f2..d76a065 100644
--- a/docs/build/html/topics/impala_datatypes.html
+++ b/docs/build/html/topics/impala_datatypes.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Data Types" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_langref.html" />
@@ -29,8 +29,8 @@
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_complex_types.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="datatypes" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -44,33 +44,45 @@
   
 
   <div class="body conbody">
+    <p class="p">Impala supports a set of data types that you can use for table columns,
+      expression values, and function arguments and return values. </p>
 
-    <p class="p">
-      
-      Impala supports a set of data types that you can use for table columns, expression values, and function
-      arguments and return values.
-    </p>
+    <div class="note note"><span class="notetitle">Note:</span>  Currently, Impala supports only scalar types, not composite or nested
+      types. Accessing a table containing any columns with unsupported types
+      causes an error. </div>
 
+    <p class="p toc"></p>
 
-    <div class="note note"><span class="notetitle">Note:</span> 
-      Currently, Impala supports only scalar types, not composite or nested types. Accessing a table containing any
-      columns with unsupported types causes an error.
-    </div>
+    <p class="p"> For the notation to write literals of each of these data types, see
+        <a class="xref" href="impala_literals.html#literals">Literals</a>. </p>
 
+    
+      <p class="p"> Impala supports a limited set of implicit casts to avoid undesired
+      results from unexpected casting behavior. </p>
 
-    <p class="p toc"></p>
+    <ul class="ul">
+      <li class="li"> Impala does not implicitly cast between string and numeric or Boolean
+        types. Always use <code class="ph codeph">CAST()</code> for these conversions. </li>
 
+      <li class="li"> Impala does perform implicit casts among the numeric types, when
+        going from a smaller or less precise type to a larger or more precise
+        one. For example, Impala will implicitly convert a
+          <code class="ph codeph">SMALLINT</code> to a <code class="ph codeph">BIGINT</code> or
+          <code class="ph codeph">FLOAT</code>, but to convert from <code class="ph codeph">DOUBLE</code> to
+          <code class="ph codeph">FLOAT</code> or <code class="ph codeph">INT</code> to
+          <code class="ph codeph">TINYINT</code> requires a call to <code class="ph codeph">CAST()</code> in
+        the query. </li>
 
-    <p class="p">
-      For the notation to write literals of each of these data types, see
-      <a class="xref" href="impala_literals.html#literals">Literals</a>.
-    </p>
+      <li class="li"> Impala does perform implicit casts from <code class="ph codeph">STRING</code> to
+          <code class="ph codeph">TIMESTAMP</code>. Impala has a restricted set of literal
+        formats for the <code class="ph codeph">TIMESTAMP</code> data type and the
+          <code class="ph codeph">FROM_UNIXTIME()</code> format string; see <a class="xref" href="impala_timestamp.html#timestamp">TIMESTAMP Data Type</a> for details. </li>
 
+    </ul>
 
-    <p class="p">
-      See <a class="xref" href="impala_langref_unsupported.html#langref_hiveql_delta">SQL Differences Between Impala and Hive</a> for differences between Impala and
-      Hive data types.
-    </p>
+    <p class="p">See the topics under this section for full details on implicit and
+      explicit casting for each data type, and see <a class="xref" href="impala_conversion_functions.html#conversion_functions">Impala Type Conversion Functions</a> for
+      details about the <code class="ph codeph">CAST()</code> function.</p>
 
   </div>
 
diff --git a/docs/build/html/topics/impala_date.html b/docs/build/html/topics/impala_date.html
index eeee8b6..38c0e99 100644
--- a/docs/build/html/topics/impala_date.html
+++ b/docs/build/html/topics/impala_date.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DATE Data Type" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_datatypes.html" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="date" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -28,10 +28,9 @@
 
   <div class="body conbody">
 
-    <p class="p">
-      Use the <code class="ph codeph">DATE</code> data type to store date values. The <code class="ph codeph">DATE</code>
-      type is supported for HBase, Text, and Parquet.
-    </p>
+    <p class="p"> Use the <code class="ph codeph">DATE</code> data type to store date values. The
+        <code class="ph codeph">DATE</code> type is supported for HBase, Text, Avro, and
+      Parquet. </p>
 
 
     <p class="p">
@@ -39,9 +38,7 @@
     </p>
 
 
-    <p class="p">
-      0000-01-01 to 9999-12-31
-    </p>
+    <p class="p"> 0001-01-01 to 9999-12-31 </p>
 
 
     <p class="p">
@@ -49,30 +46,27 @@
     </p>
 
 
-    <p class="p">
-      The <code class="ph codeph">DATE</code> literals are in the form of <code class="ph codeph">DATE'YYYY-MM-DD'</code>.
-      For example, <code class="ph codeph">DATE '2013-01-01'</code>
+    <p class="p"> The <code class="ph codeph">DATE</code> literals are in the form of
+        <code class="ph codeph">DATE'YYYY-MM-DD'</code>. For examplep, <code class="ph codeph">DATE
+        '2013-01-01'</code>
     </p>
 
 
     <p class="p">
-      <strong class="ph b">Parquet considerations:</strong>
+      <strong class="ph b">Parquet and Avro considerations:</strong>
     </p>
 
 
-    <p class="p">
-      Parquet uses <code class="ph codeph">DATE</code> logical type for dates. The <code class="ph codeph">DATE</code>
-      logical type annotates an <code class="ph codeph">INT32</code> that stores the number of days from the
-      Unix epoch, January 1, 1970. This representation introduces a parquet interoperability
-      issue between Impala and older versions of Hive:
-    </p>
+    <p class="p"> Parquet and Avro use <code class="ph codeph">DATE</code> logical type for dates. The
+        <code class="ph codeph">DATE</code> logical type annotates an <code class="ph codeph">INT32</code>
+      that stores the number of days from the Unix epoch, January 1, 1970. This
+      representation introduces an interoperability issue between Impala and
+      older versions of Hive: </p>
 
 
-    <p class="p">
-      If Hive versions lower than 3.1 wrote dates earlier than 1582-10-15 to a parquet table,
-      those dates will be read back incorrectly by Impala and vice versa. In Hive 3.1 and
-      higher, this is no longer an issue.
-    </p>
+    <p class="p"> If Hive versions lower than 3.1 wrote dates earlier than 1582-10-15 to a
+      Parquet or Avro table, those dates would be read back incorrectly by
+      Impala and vice versa. In Hive 3.1 and higher, this is no longer an issue. </p>
 
 
     <p class="p">
@@ -89,15 +83,15 @@
     
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="date__table_ovw_zt1_p3b" class="table" frame="border" border="1" rules="all"><colgroup><col style="width:18.01801801801802%" /><col style="width:19.639639639639643%" /><col style="width:62.34234234234234%" /></colgroup><thead class="thead" style="text-align:left;">
           <tr class="row">
-            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d48173e142">
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d50716e142">
               Cast from
             </th>
 
-            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d48173e145">
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d50716e145">
               Cast to
             </th>
 
-            <th class="entry cell-norowborder" style="vertical-align:top;" id="d48173e148">
+            <th class="entry cell-norowborder" style="vertical-align:top;" id="d50716e148">
               Result
             </th>
 
@@ -106,15 +100,15 @@
         </thead>
 <tbody class="tbody">
           <tr class="row">
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d48173e142 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d50716e142 ">
               <code class="ph codeph">TIMESTAMP</code>
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d48173e145 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d50716e145 ">
               <code class="ph codeph">DATE</code>
             </td>
 
-            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d48173e148 ">
+            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d50716e148 ">
               The date component of the <code class="ph codeph">TIMESTAMP</code> is returned, and the time of
               the day component of the <code class="ph codeph">TIMESTAMP</code> is ignored.
             </td>
@@ -122,15 +116,15 @@
           </tr>
 
           <tr class="row">
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d48173e142 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d50716e142 ">
               <code class="ph codeph">STRING</code>
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d48173e145 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d50716e145 ">
               <code class="ph codeph">DATE</code>
             </td>
 
-            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d48173e148 ">
+            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d50716e148 ">
               The <code class="ph codeph">DATE</code> value of <code class="ph codeph">yyyy-MM-dd</code> is returned.
 
               <p class="p">
@@ -159,15 +153,15 @@
           </tr>
 
           <tr class="row">
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d48173e142 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d50716e142 ">
               <code class="ph codeph">DATE</code>
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d48173e145 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d50716e145 ">
               <code class="ph codeph">TIMESTAMP</code>
             </td>
 
-            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d48173e148 ">
+            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d50716e148 ">
               The year, month, and day of the <code class="ph codeph">DATE</code> is returned along with the
               time of day component set to <code class="ph codeph">00:00:00</code>.
             </td>
@@ -175,15 +169,15 @@
           </tr>
 
           <tr class="row">
-            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d48173e142 ">
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d50716e142 ">
               <code class="ph codeph">DATE</code>
             </td>
 
-            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d48173e145 ">
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d50716e145 ">
               <code class="ph codeph">STRING</code>
             </td>
 
-            <td class="entry cellrowborder" style="vertical-align:top;" headers="d48173e148 ">
+            <td class="entry cellrowborder" style="vertical-align:top;" headers="d50716e148 ">
               The <code class="ph codeph">STRING</code> value, <code class="ph codeph">'yyyy-MM-dd'</code>, is returned.
             </td>
 
diff --git a/docs/build/html/topics/impala_datetime_functions.html b/docs/build/html/topics/impala_datetime_functions.html
index e7967eb..0468376 100644
--- a/docs/build/html/topics/impala_datetime_functions.html
+++ b/docs/build/html/topics/impala_datetime_functions.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Date and Time 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="datetime_functions" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -472,6 +472,7 @@
             return the same value, and the value does not depend on how long the query takes.
           </p>
 
+
           <p class="p">
             <strong class="ph b">Return type:</strong> <code class="ph codeph">DATE</code>
           </p>
@@ -752,15 +753,15 @@ select date_sub(cast('2016-05-31' as timestamp), interval 1 months) as 'april_31
           
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="datetime_functions__table_ucy_trp_p3b" class="table" frame="border" border="1" rules="all"><colgroup><col style="width:25.380710659898476%" /><col style="width:32.48730964467005%" /><col style="width:42.13197969543147%" /></colgroup><thead class="thead" style="text-align:left;">
                 <tr class="row">
-                  <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d48673e1045">
+                  <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e1045">
                     Unit
                   </th>
 
-                  <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d48673e1048">
+                  <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e1048">
                     Supported for TIMESTAMP
                   </th>
 
-                  <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d48673e1051">
+                  <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e1051">
                     Supported for DATE
                   </th>
 
@@ -769,180 +770,180 @@ select date_sub(cast('2016-05-31' as timestamp), interval 1 months) as 'april_31
               </thead>
 <tbody class="tbody">
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'MICROSECONDS'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     No
                   </td>
 
                 </tr>
 
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'MILLISECONDS'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     No
                   </td>
 
                 </tr>
 
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'SECOND'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     No
                   </td>
 
                 </tr>
 
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'MINUTE'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     No
                   </td>
 
                 </tr>
 
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'HOUR'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     No
                   </td>
 
                 </tr>
 
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'DAY'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     Yes
                   </td>
 
                 </tr>
 
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'WEEK'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     Yes
                   </td>
 
                 </tr>
 
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'MONTH'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     Yes
                   </td>
 
                 </tr>
 
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'YEAR'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     Yes
                   </td>
 
                 </tr>
 
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'DECADE'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     Yes
                   </td>
 
                 </tr>
 
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'CENTURY'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     Yes
                   </td>
 
                 </tr>
 
                 <tr class="row">
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1045 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1045 ">
                     <code class="ph codeph">'MILLENNIUM'</code>
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1048 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1048 ">
                     Yes
                   </td>
 
-                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1051 ">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1051 ">
                     Yes
                   </td>
 
@@ -1244,15 +1245,15 @@ select date_sub(cast('2016-05-31' as timestamp), interval 1 months) as 'april_31
             
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="datetime_functions__table_itt_ktp_p3b" class="table" frame="border" border="1" rules="all"><colgroup><col style="width:25.380710659898476%" /><col style="width:32.48730964467005%" /><col style="width:42.13197969543147%" /></colgroup><thead class="thead" style="text-align:left;">
                   <tr class="row">
-                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d48673e1696">
+                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e1696">
                       Unit
                     </th>
 
-                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d48673e1699">
+                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e1699">
                       Supported for TIMESTAMP ts
                     </th>
 
-                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d48673e1702">
+                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e1702">
                       Supported for DATE ts
                     </th>
 
@@ -1261,135 +1262,135 @@ select date_sub(cast('2016-05-31' as timestamp), interval 1 months) as 'april_31
                 </thead>
 <tbody class="tbody">
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1696 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1696 ">
                       <code class="ph codeph">'EPOCH'</code>
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1699 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1699 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1702 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1702 ">
                       No
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1696 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1696 ">
                       <code class="ph codeph">'MILLISECOND'</code>
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1699 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1699 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1702 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1702 ">
                       No
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1696 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1696 ">
                       <code class="ph codeph">'SECOND'</code>
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1699 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1699 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1702 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1702 ">
                       No
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1696 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1696 ">
                       <code class="ph codeph">'MINUTE'</code>
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1699 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1699 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1702 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1702 ">
                       No
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1696 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1696 ">
                       <code class="ph codeph">'HOUR'</code>
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1699 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1699 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1702 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1702 ">
                       No
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1696 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1696 ">
                       <code class="ph codeph">'DAY'</code>
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1699 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1699 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1702 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1702 ">
                       Yes
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1696 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1696 ">
                       <code class="ph codeph">'MONTH'</code>
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1699 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1699 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1702 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1702 ">
                       Yes
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1696 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1696 ">
                       <code class="ph codeph">'QUARTER'</code>
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1699 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1699 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1702 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1702 ">
                       Yes
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1696 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1696 ">
                       <code class="ph codeph">'YEAR'</code>
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1699 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1699 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e1702 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e1702 ">
                       Yes
                     </td>
 
@@ -1494,7 +1495,7 @@ select date_sub(cast('2016-05-31' as timestamp), interval 1 months) as 'april_31
       
 
         <dt class="dt dlterm" id="datetime_functions__from_unixtime">
-          FROM_UNIXTIME(BIGINT unixtime[, STRING format])
+          FROM_UNIXTIME(BIGINT unixtime [, STRING pattern])
         </dt>
 
 
@@ -1505,6 +1506,209 @@ select date_sub(cast('2016-05-31' as timestamp), interval 1 months) as 'april_31
             <strong class="ph b">Return type:</strong> <code class="ph codeph">STRING</code>
           </p>
 
+          <p class="p">
+            The <var class="keyword varname">pattern</var> string supports the following subset of Java
+            SimpleDateFormat.
+          </p>
+
+          
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="datetime_functions__table_dzg_zpm_1jb" class="table" frame="border" border="1" rules="all"><colgroup><col /><col /></colgroup><thead class="thead" style="text-align:left;">
+                <tr class="row">
+                  <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e2004">
+                    Pattern
+                  </th>
+
+                  <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e2007">
+                    Description
+                  </th>
+
+                </tr>
+
+              </thead>
+<tbody class="tbody">
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2004 ">
+                    <code class="ph codeph">y</code>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2007 ">
+                    Year
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2004 ">
+                    <code class="ph codeph">M</code>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2007 ">
+                    Month
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2004 ">
+                    <code class="ph codeph">d</code>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2007 ">
+                    Day
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2004 ">
+                    <code class="ph codeph">H</code>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2007 ">
+                    Hour
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2004 ">
+                    <code class="ph codeph">m</code>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2007 ">
+                    Minute
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2004 ">
+                    <code class="ph codeph">s</code>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2007 ">
+                    Second
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2004 ">
+                    <code class="ph codeph">S</code>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2007 ">
+                    Fractional second
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2004 ">
+                    <code class="ph codeph">+/-hh:mm</code>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2007 ">
+                    Time zone offset
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2004 ">
+                    <code class="ph codeph">+/-hhmm</code>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2007 ">
+                    Time zone offset
+                  </td>
+
+                </tr>
+
+                <tr class="row">
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2004 ">
+                    <code class="ph codeph">+/-hh</code>
+                  </td>
+
+                  <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e2007 ">
+                    Time zone offset
+                  </td>
+
+                </tr>
+
+              </tbody>
+</table>
+</div>
+
+          <p class="p">
+            The following rules apply to the <var class="keyword varname">pattern</var> string:
+          </p>
+
+          <ul class="ul">
+            <li class="li">
+              The <var class="keyword varname">pattern</var> string is case-sensitive.
+            </li>
+
+
+            <li class="li">
+              All fields are variable length, and thus must use separators to specify the
+              boundaries of the fields, with the exception of the time zone values.
+            </li>
+
+
+            <li class="li">
+              Time zone offset formats must be at the end of the <var class="keyword varname">pattern</var>
+              string.
+            </li>
+
+
+            <li class="li">
+              Formatting character groups can appear in any order along with any separators
+              except for the time zone offset. For example:
+              <ul class="ul">
+                <li class="li">
+                  <code class="ph codeph">yyyy/MM/dd</code>
+                </li>
+
+
+                <li class="li">
+                  <code class="ph codeph">dd-MMM-yy</code>
+                </li>
+
+
+                <li class="li">
+                  <code class="ph codeph">(dd)(MM)(yyyy) HH:mm:ss</code>
+                </li>
+
+
+                <li class="li">
+                  <code class="ph codeph">yyyy-MM-dd HH:mm:ss+hh:mm</code>
+                </li>
+
+              </ul>
+
+            </li>
+
+          </ul>
+
+          <p class="p">
+            In Impala 1.3 and later, you can switch the order of elements, use alternative
+            separator characters, and use a different number of placeholders for each unit.
+            Adding more instances of <code class="ph codeph">y</code>, <code class="ph codeph">d</code>, <code class="ph codeph">H</code>,
+            and so on produces output strings zero-padded to the requested number of characters.
+            The exception is <code class="ph codeph">M</code> for months, where <code class="ph codeph">M</code> produces a
+            non-padded value such as <code class="ph codeph">3</code>, <code class="ph codeph">MM</code> produces a
+            zero-padded value such as <code class="ph codeph">03</code>, <code class="ph codeph">MMM</code> produces an
+            abbreviated month name such as <code class="ph codeph">Mar</code>, and sequences of 4 or more
+            <code class="ph codeph">M</code> are not allowed.
+          </p>
+
+          <p class="p">
+            A date string including all fields could be <code class="ph codeph">'yyyy-MM-dd
+            HH:mm:ss.SSSSSS'</code>, <code class="ph codeph">'dd/MM/yyyy HH:mm:ss.SSSSSS'</code>,
+            <code class="ph codeph">'MMM dd, yyyy HH.mm.ss (SSSSSS)'</code> or other combinations of
+            placeholders and separator characters.
+          </p>
 
           <p class="p">
         In Impala 2.2.0 and higher, built-in functions that accept or return integers
@@ -1520,37 +1724,10 @@ select date_sub(cast('2016-05-31' as timestamp), interval 1 months) as 'april_31
         SQL statements that call these functions.
       </p>
 
-
           <p class="p">
         <strong class="ph b">Usage notes:</strong>
       </p>
 
-
-          <p class="p">
-            The format string accepts the variations allowed for the <code class="ph codeph">TIMESTAMP</code>
-            data type: date plus time, date by itself, time by itself, and optional fractional
-            seconds for the time. See <a class="xref" href="impala_timestamp.html#timestamp">TIMESTAMP Data Type</a> for details.
-          </p>
-
-
-          <p class="p">
-            Currently, the format string is case-sensitive, especially to distinguish
-            <code class="ph codeph">m</code> for minutes and <code class="ph codeph">M</code> for months. In Impala 1.3 and
-            later, you can switch the order of elements, use alternative separator characters,
-            and use a different number of placeholders for each unit. Adding more instances of
-            <code class="ph codeph">y</code>, <code class="ph codeph">d</code>, <code class="ph codeph">H</code>, and so on produces
-            output strings zero-padded to the requested number of characters. The exception is
-            <code class="ph codeph">M</code> for months, where <code class="ph codeph">M</code> produces a non-padded value
-            such as <code class="ph codeph">3</code>, <code class="ph codeph">MM</code> produces a zero-padded value such as
-            <code class="ph codeph">03</code>, <code class="ph codeph">MMM</code> produces an abbreviated month name such as
-            <code class="ph codeph">Mar</code>, and sequences of 4 or more <code class="ph codeph">M</code> are not allowed.
-            A date string including all fields could be <code class="ph codeph">'yyyy-MM-dd
-            HH:mm:ss.SSSSSS'</code>, <code class="ph codeph">'dd/MM/yyyy HH:mm:ss.SSSSSS'</code>,
-            <code class="ph codeph">'MMM dd, yyyy HH.mm.ss (SSSSSS)'</code> or other combinations of
-            placeholders and separator characters.
-          </p>
-
-
           <p class="p">
         The way this function deals with time zones when converting to or from
         <code class="ph codeph">TIMESTAMP</code> values is affected by the
@@ -1560,19 +1737,6 @@ select date_sub(cast('2016-05-31' as timestamp), interval 1 months) as 'april_31
         Impala handles time zone considerations for the <code class="ph codeph">TIMESTAMP</code> data type.
       </p>
 
-
-          <div class="note note"><span class="notetitle">Note:</span> 
-            <p class="p">
-              The more flexible format strings allowed with the built-in functions do not change
-              the rules about using <code class="ph codeph">CAST()</code> to convert from a string to a
-              <code class="ph codeph">TIMESTAMP</code> value. Strings being converted through
-              <code class="ph codeph">CAST()</code> must still have the elements in the specified order and
-              use the specified delimiter characters, as described in
-              <a class="xref" href="impala_timestamp.html#timestamp">TIMESTAMP Data Type</a>.
-            </p>
-
-          </div>
-
         </dd>
 
 
@@ -2774,19 +2938,19 @@ select now() as 'Current time in California USA',
             
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="datetime_functions__table_evg_bhp_p3b" class="table" frame="border" border="1" rules="all"><colgroup><col style="width:25%" /><col style="width:25%" /><col style="width:25%" /><col style="width:25%" /></colgroup><thead class="thead" style="text-align:left;">
                   <tr class="row">
-                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d48673e3663">
+                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e3834">
                       Unit
                     </th>
 
-                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d48673e3666">
+                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e3837">
                       Supported for TIMESTAMP ts
                     </th>
 
-                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d48673e3669">
+                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e3840">
                       Supported for DATE ts
                     </th>
 
-                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d48673e3672">
+                    <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d51216e3843">
                       Description
                     </th>
 
@@ -2795,7 +2959,7 @@ select now() as 'Current time in California USA',
                 </thead>
 <tbody class="tbody">
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3663 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3834 ">
                       <p class="p">
                         <code class="ph codeph">'SYYYY'</code>
                       </p>
@@ -2844,44 +3008,44 @@ select now() as 'Current time in California USA',
 
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3666 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3837 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3669 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3840 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3672 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3843 ">
                       Year
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3663 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3834 ">
                       <p class="p">
                         <code class="ph codeph">'Q'</code>
                       </p>
 
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3666 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3837 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3669 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3840 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3672 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3843 ">
                       Quarter
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3663 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3834 ">
                       <p class="p">
                         <code class="ph codeph">'MONTH'</code>
                       </p>
@@ -2909,37 +3073,37 @@ select now() as 'Current time in California USA',
 
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3666 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3837 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3669 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3840 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3672 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3843 ">
                       Month
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3663 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3834 ">
                       <p class="p">
                         <code class="ph codeph">'WW'</code>
                       </p>
 
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3666 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3837 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3669 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3840 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3672 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3843 ">
                       The most recent date that is the same day of the week as the first day of
                       the year
                     </td>
@@ -2947,22 +3111,22 @@ select now() as 'Current time in California USA',
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3663 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3834 ">
                       <p class="p">
                         <code class="ph codeph">'W'</code>
                       </p>
 
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3666 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3837 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3669 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3840 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3672 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3843 ">
                       The most recent date that is the same day of the week as the first day of
                       the month
                     </td>
@@ -2970,7 +3134,7 @@ select now() as 'Current time in California USA',
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3663 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3834 ">
                       <p class="p">
                         <code class="ph codeph">'DDD'</code>
                       </p>
@@ -2991,22 +3155,22 @@ select now() as 'Current time in California USA',
 
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3666 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3837 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3669 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3840 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3672 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3843 ">
                       Day
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3663 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3834 ">
                       <p class="p">
                         <code class="ph codeph">'DAY'</code>
                       </p>
@@ -3027,22 +3191,22 @@ select now() as 'Current time in California USA',
 
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3666 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3837 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3669 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3840 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3672 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3843 ">
                       Starting day of the week (Monday)
                     </td>
 
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3663 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3834 ">
                       <p class="p">
                         <code class="ph codeph">'HH'</code>
                       </p>
@@ -3063,15 +3227,15 @@ select now() as 'Current time in California USA',
 
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3666 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3837 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3669 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3840 ">
                       No
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3672 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3843 ">
                       Hour. A <code class="ph codeph">TIMESTAMP</code> value truncated to the hour is always
                       represented in 24-hour notation, even for the <code class="ph codeph">HH12</code>
                       argument string.
@@ -3080,19 +3244,19 @@ select now() as 'Current time in California USA',
                   </tr>
 
                   <tr class="row">
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3663 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3834 ">
                       <code class="ph codeph">'MI'</code>
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3666 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3837 ">
                       Yes
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3669 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3840 ">
                       No
                     </td>
 
-                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d48673e3672 ">
+                    <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d51216e3843 ">
                       Minute
                     </td>
 
@@ -3168,7 +3332,7 @@ select now() as 'Current time in California USA',
 
         <dt class="dt dlterm" id="datetime_functions__unix_timestamp">
           UNIX_TIMESTAMP(), UNIX_TIMESTAMP(STRING datetime), UNIX_TIMESTAMP(STRING datetime,
-          STRING format), UNIX_TIMESTAMP(TIMESTAMP datetime)
+          STRING pattern), UNIX_TIMESTAMP(TIMESTAMP datetime)
         </dt>
 
 
@@ -3190,7 +3354,7 @@ select now() as 'Current time in California USA',
 
           <p class="p">
             See <code class="ph codeph">FROM_UNIXTIME()</code> for details about the patterns you can use in
-            the <code class="ph codeph">format</code> string to represent the position of year, month, day,
+            the <var class="keyword varname">pattern</var> string to represent the position of year, month, day,
             and so on in the <code class="ph codeph">date</code> string. In Impala 1.3 and higher, you have
             more flexibility to switch the positions of elements and use different separator
             characters.
@@ -3205,12 +3369,13 @@ select now() as 'Current time in California USA',
 
           <p class="p">
             In <span class="keyword">Impala 2.3</span> and higher, you can include a timezone offset
-            specified as minutes and hours, provided you also specify the details in the format
-            string argument. The offset is specified in the format string as a plus or minus
-            sign followed by <code class="ph codeph">hh:mm</code>, <code class="ph codeph">hhmm</code>, or
-            <code class="ph codeph">hh</code>. The <code class="ph codeph">hh</code> must be lowercase, to distinguish it
-            from the <code class="ph codeph">HH</code> represent hours in the actual time value. Currently,
-            only numeric timezone offsets are allowed, not symbolic names.
+            specified as minutes and hours, provided you also specify the details in the
+            <var class="keyword varname">pattern</var> string argument. The offset is specified in the
+            <var class="keyword varname">pattern</var> string as a plus or minus sign followed by
+            <code class="ph codeph">hh:mm</code>, <code class="ph codeph">hhmm</code>, or <code class="ph codeph">hh</code>. The
+            <code class="ph codeph">hh</code> must be lowercase, to distinguish it from the
+            <code class="ph codeph">HH</code> represent hours in the actual time value. Currently, only
+            numeric timezone offsets are allowed, not symbolic names.
           </p>
 
 
@@ -3261,10 +3426,11 @@ select now() as 'Current time in California USA',
 
           <p class="p">
             The following examples show different ways of turning the same date and time into an
-            integer value. A format string that Impala recognizes by default is interpreted as a
-            UTC date and time. The trailing <code class="ph codeph">Z</code> is a confirmation that the
-            timezone is UTC. If the date and time string is formatted differently, a second
-            argument specifies the position and units for each of the date and time values.
+            integer value. A <var class="keyword varname">pattern</var> string that Impala recognizes by default
+            is interpreted as a UTC date and time. The trailing <code class="ph codeph">Z</code> is a
+            confirmation that the timezone is UTC. If the date and time string is formatted
+            differently, a second argument specifies the position and units for each of the date
+            and time values.
           </p>
 
 
@@ -3272,7 +3438,7 @@ select now() as 'Current time in California USA',
             The final two examples show how to specify a timezone offset of Pacific Daylight
             Saving Time, which is 7 hours earlier than UTC. You can use the numeric offset
             <code class="ph codeph">-07:00</code> and the equivalent suffix of <code class="ph codeph">-hh:mm</code> in the
-            format string, or specify the mnemonic name for the time zone in a call to
+            pattern string, or specify the mnemonic name for the time zone in a call to
             <code class="ph codeph">TO_UTC_TIMESTAMP()</code>. This particular date and time expressed in PDT
             translates to a different number than the same date and time expressed in UTC.
           </p>
diff --git a/docs/build/html/topics/impala_ddl.html b/docs/build/html/topics/impala_ddl.html
index 248c9bd..ee79b0b 100644
--- a/docs/build/html/topics/impala_ddl.html
+++ b/docs/build/html/topics/impala_ddl.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DDL Statements" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="ddl" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -135,7 +135,7 @@
 
 
     <p class="p">
-      See <a class="xref" href="impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details about how Impala DDL statements interact with
+      See <a class="xref" href="impala_s3.html#s3">Using Impala with Amazon S3 Object Store</a> for details about how Impala DDL statements interact with
       tables and partitions stored in the Amazon S3 filesystem.
     </p>
 
diff --git a/docs/build/html/topics/impala_debug_action.html b/docs/build/html/topics/impala_debug_action.html
index c91fce3..54100d6 100644
--- a/docs/build/html/topics/impala_debug_action.html
+++ b/docs/build/html/topics/impala_debug_action.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DEBUG_ACTION 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="debug_action" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_decimal.html b/docs/build/html/topics/impala_decimal.html
index 840c1ba..a022914 100644
--- a/docs/build/html/topics/impala_decimal.html
+++ b/docs/build/html/topics/impala_decimal.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DECIMAL Data Type (Impala 3.0 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="decimal" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -133,37 +133,37 @@
     <div class="p">
       <table cellpadding="4" cellspacing="0" summary="" id="decimal__simpletable_tty_3y2_mdb" border="1" class="simpletable"><col style="width:50%" /><col style="width:50%" /><thead><tr class="sthead">
 
-          <th style="vertical-align:bottom;text-align:left;" id="d56459e176" class="stentry">Precision</th>
+          <th style="vertical-align:bottom;text-align:left;" id="d59343e176" class="stentry">Precision</th>
 
 
-          <th style="vertical-align:bottom;text-align:left;" id="d56459e179" class="stentry">In-memory Storage</th>
+          <th style="vertical-align:bottom;text-align:left;" id="d59343e179" class="stentry">In-memory Storage</th>
 
 
         </tr>
 </thead><tbody><tr class="strow">
 
-          <td style="vertical-align:top;" headers="d56459e176" class="stentry">1 - 9</td>
+          <td style="vertical-align:top;" headers="d59343e176" class="stentry">1 - 9</td>
 
 
-          <td style="vertical-align:top;" headers="d56459e179" class="stentry">4 bytes</td>
+          <td style="vertical-align:top;" headers="d59343e179" class="stentry">4 bytes</td>
 
 
         </tr>
 <tr class="strow">
 
-          <td style="vertical-align:top;" headers="d56459e176" class="stentry">10 - 18</td>
+          <td style="vertical-align:top;" headers="d59343e176" class="stentry">10 - 18</td>
 
 
-          <td style="vertical-align:top;" headers="d56459e179" class="stentry">8 bytes</td>
+          <td style="vertical-align:top;" headers="d59343e179" class="stentry">8 bytes</td>
 
 
         </tr>
 <tr class="strow">
 
-          <td style="vertical-align:top;" headers="d56459e176" class="stentry">19 - 38</td>
+          <td style="vertical-align:top;" headers="d59343e176" class="stentry">19 - 38</td>
 
 
-          <td style="vertical-align:top;" headers="d56459e179" class="stentry">16 bytes</td>
+          <td style="vertical-align:top;" headers="d59343e179" class="stentry">16 bytes</td>
 
 
         </tr>
@@ -1080,64 +1080,64 @@ INSERT INTO decimals_11_8 VALUES (CAST(1 AS TINYINT));</code></pre>
     <div class="p">
       <table cellpadding="4" cellspacing="0" summary="" id="decimal__simpletable_bwl_khm_rdb" border="1" class="simpletable"><col style="width:33.33333333333333%" /><col style="width:33.33333333333333%" /><col style="width:33.33333333333333%" /><thead><tr class="sthead">
 
-          <th style="vertical-align:bottom;text-align:left;" id="d56459e1325" class="stentry"> </th>
+          <th style="vertical-align:bottom;text-align:left;" id="d59343e1325" class="stentry"> </th>
 
 
-          <th style="vertical-align:bottom;text-align:left;" id="d56459e1327" class="stentry">DECIMAL in <span class="keyword">Impala 3.0</span> or
+          <th style="vertical-align:bottom;text-align:left;" id="d59343e1327" class="stentry">DECIMAL in <span class="keyword">Impala 3.0</span> or
             higher</th>
 
 
-          <th style="vertical-align:bottom;text-align:left;" id="d56459e1333" class="stentry">DECIMAL in <span class="keyword">Impala 2.12</span> or lower
+          <th style="vertical-align:bottom;text-align:left;" id="d59343e1333" class="stentry">DECIMAL in <span class="keyword">Impala 2.12</span> or lower
           </th>
 
 
         </tr>
 </thead><tbody><tr class="strow">
 
-          <td style="vertical-align:top;" headers="d56459e1325" class="stentry">Overall behavior</td>
+          <td style="vertical-align:top;" headers="d59343e1325" class="stentry">Overall behavior</td>
 
 
-          <td style="vertical-align:top;" headers="d56459e1327" class="stentry">Returns either the result or an error.</td>
+          <td style="vertical-align:top;" headers="d59343e1327" class="stentry">Returns either the result or an error.</td>
 
 
-          <td style="vertical-align:top;" headers="d56459e1333" class="stentry">Returns either the result or <code class="ph codeph">NULL</code> with a
+          <td style="vertical-align:top;" headers="d59343e1333" class="stentry">Returns either the result or <code class="ph codeph">NULL</code> with a
             warning.</td>
 
 
         </tr>
 <tr class="strow">
 
-          <td style="vertical-align:top;" headers="d56459e1325" class="stentry">Overflow behavior</td>
+          <td style="vertical-align:top;" headers="d59343e1325" class="stentry">Overflow behavior</td>
 
 
-          <td style="vertical-align:top;" headers="d56459e1327" class="stentry">Aborts with an error.</td>
+          <td style="vertical-align:top;" headers="d59343e1327" class="stentry">Aborts with an error.</td>
 
 
-          <td style="vertical-align:top;" headers="d56459e1333" class="stentry">Issues a warning and returns <code class="ph codeph">NULL</code>.</td>
+          <td style="vertical-align:top;" headers="d59343e1333" class="stentry">Issues a warning and returns <code class="ph codeph">NULL</code>.</td>
 
 
         </tr>
 <tr class="strow">
 
-          <td style="vertical-align:top;" headers="d56459e1325" class="stentry">Truncation / rounding behavior in arithmetic</td>
+          <td style="vertical-align:top;" headers="d59343e1325" class="stentry">Truncation / rounding behavior in arithmetic</td>
 
 
-          <td style="vertical-align:top;" headers="d56459e1327" class="stentry">Truncates and rounds digits from the back.</td>
+          <td style="vertical-align:top;" headers="d59343e1327" class="stentry">Truncates and rounds digits from the back.</td>
 
 
-          <td style="vertical-align:top;" headers="d56459e1333" class="stentry">Truncates digits from the front.</td>
+          <td style="vertical-align:top;" headers="d59343e1333" class="stentry">Truncates digits from the front.</td>
 
 
         </tr>
 <tr class="strow">
 
-          <td style="vertical-align:top;" headers="d56459e1325" class="stentry">String cast</td>
+          <td style="vertical-align:top;" headers="d59343e1325" class="stentry">String cast</td>
 
 
-          <td style="vertical-align:top;" headers="d56459e1327" class="stentry">Truncates from the back and rounds.</td>
+          <td style="vertical-align:top;" headers="d59343e1327" class="stentry">Truncates from the back and rounds.</td>
 
 
-          <td style="vertical-align:top;" headers="d56459e1333" class="stentry">Truncates from the back.</td>
+          <td style="vertical-align:top;" headers="d59343e1333" class="stentry">Truncates from the back.</td>
 
 
         </tr>
diff --git a/docs/build/html/topics/impala_decimal_v2.html b/docs/build/html/topics/impala_decimal_v2.html
index f2bd8e5..01a5713 100644
--- a/docs/build/html/topics/impala_decimal_v2.html
+++ b/docs/build/html/topics/impala_decimal_v2.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DECIMAL_V2 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.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="decimal_v2" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_dedicated_coordinator.html b/docs/build/html/topics/impala_dedicated_coordinator.html
index edaf89e..802848d 100644
--- a/docs/build/html/topics/impala_dedicated_coordinator.html
+++ b/docs/build/html/topics/impala_dedicated_coordinator.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="How to Configure Impala with Dedicated Coordinators" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_scalability.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="scalability" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_default_file_format.html b/docs/build/html/topics/impala_default_file_format.html
index d97e7ff..4838941 100644
--- a/docs/build/html/topics/impala_default_file_format.html
+++ b/docs/build/html/topics/impala_default_file_format.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DEFAULT_FILE_FORMAT 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.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="default_file_format" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_default_hints_insert_statement.html b/docs/build/html/topics/impala_default_hints_insert_statement.html
index 739709f..45ad730 100644
--- a/docs/build/html/topics/impala_default_hints_insert_statement.html
+++ b/docs/build/html/topics/impala_default_hints_insert_statement.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DEFAULT_HINTS_INSERT_STATEMENT 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.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="default_hints_insert_statement" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_default_join_distribution_mode.html b/docs/build/html/topics/impala_default_join_distribution_mode.html
index cf9815e..b3006ef 100644
--- a/docs/build/html/topics/impala_default_join_distribution_mode.html
+++ b/docs/build/html/topics/impala_default_join_distribution_mode.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DEFAULT_JOIN_DISTRIBUTION_MODE 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="default_join_distribution_mode" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_default_spillable_buffer_size.html b/docs/build/html/topics/impala_default_spillable_buffer_size.html
index e4163e5..fb67a56 100644
--- a/docs/build/html/topics/impala_default_spillable_buffer_size.html
+++ b/docs/build/html/topics/impala_default_spillable_buffer_size.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DEFAULT_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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="default_spillable_buffer_size" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_default_transactional_type.html b/docs/build/html/topics/impala_default_transactional_type.html
index bdefa03..d6e5433 100644
--- a/docs/build/html/topics/impala_default_transactional_type.html
+++ b/docs/build/html/topics/impala_default_transactional_type.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DEFAULT_TRANSACTIONAL_TYPE 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.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="default_transactional_type" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_delegation.html b/docs/build/html/topics/impala_delegation.html
index 8265381..401fd64 100644
--- a/docs/build/html/topics/impala_delegation.html
+++ b/docs/build/html/topics/impala_delegation.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Configuring Impala Delegation for Clients" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="delegation" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_delete.html b/docs/build/html/topics/impala_delete.html
index 6d87f38..0608b3c 100644
--- a/docs/build/html/topics/impala_delete.html
+++ b/docs/build/html/topics/impala_delete.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DELETE Statement (Impala 2.8 or higher only)" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="delete" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_describe.html b/docs/build/html/topics/impala_describe.html
index 865651a..e47a26f 100644
--- a/docs/build/html/topics/impala_describe.html
+++ b/docs/build/html/topics/impala_describe.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DESCRIBE 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="describe" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_development.html b/docs/build/html/topics/impala_development.html
index bd6c931..2c44de4 100644
--- a/docs/build/html/topics/impala_development.html
+++ b/docs/build/html/topics/impala_development.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Developing Impala Applications" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_concepts.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="intro_dev" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_disable_codegen.html b/docs/build/html/topics/impala_disable_codegen.html
index 905a61a..57c5eb7 100644
--- a/docs/build/html/topics/impala_disable_codegen.html
+++ b/docs/build/html/topics/impala_disable_codegen.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DISABLE_CODEGEN 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="disable_codegen" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_disable_codegen_rows_threshold.html b/docs/build/html/topics/impala_disable_codegen_rows_threshold.html
index 31f1500..9ab2c18 100644
--- a/docs/build/html/topics/impala_disable_codegen_rows_threshold.html
+++ b/docs/build/html/topics/impala_disable_codegen_rows_threshold.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DISABLE_CODEGEN_ROWS_THRESHOLD Query Option (Impala 2.10 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="disable_codegen_rows_threshold" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_disable_hbase_num_rows_estimate.html b/docs/build/html/topics/impala_disable_hbase_num_rows_estimate.html
new file mode 100644
index 0000000..3ec7d86
--- /dev/null
+++ b/docs/build/html/topics/impala_disable_hbase_num_rows_estimate.html
@@ -0,0 +1,93 @@
+<?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 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
+<meta name="DC.Type" content="concept" />
+<meta name="DC.Title" content="DISABLE_HBASE_NUM_ROWS_ESTIMATE 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.4.x" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="disable_hbase_num_rows_estimate" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>DISABLE_HBASE_NUM_ROWS_ESTIMATE Query Option</title>
+</head>
+<body id="disable_hbase_num_rows_estimate">
+
+
+  <h1 class="title topictitle1" id="ariaid-title1">DISABLE_HBASE_NUM_ROWS_ESTIMATE Query Option</h1>
+
+
+  
+
+  
+
+  <div class="body conbody">
+
+    <p class="p">
+      Use the <code class="ph codeph">DISABLE_HBASE_NUM_ROWS_ESTIMATE</code> query option to disable key
+      sampling of HBase tables in row count and row size estimation.
+    </p>
+
+
+    <p class="p">
+      While generating a plan for an HBase query, the planner samples the underlying HBase
+      tables to estimate their row count and row size, and the sampling can negatively impact
+      the planning time. When the HBase table stats does not change much in short time, disable
+      the sampling by setting the <code class="ph codeph">DISABLE_HBASE_NUM_ROWS_ESTIMATE</code> query option
+      to <code class="ph codeph">TRUE</code>. And Impala planner will fall back to using Hive Metastore (HMS)
+      table stats instead.
+    </p>
+
+
+    <p class="p">
+      When <code class="ph codeph">DISABLE_HBASE_NUM_ROWS_ESTIMATE</code> query option is set to
+      <code class="ph codeph">TRUE</code>, you need to update the HMS table stats by running <code class="ph codeph">COMPUTE
+      STATS</code>. Alternatively, you can manually set table statistics by running
+      <code class="ph codeph">ALTER TABLE</code>. See <a class="xref" href="impala_perf_stats.html#perf_stats">Table and Column Statistics</a>
+      for details.
+    </p>
+
+
+    <div class="p">
+      The following values are supported:
+      <ul class="ul">
+        <li class="li">
+          <code class="ph codeph">TRUE</code> or <code class="ph codeph">1</code>: Disables the normal key sampling of HBase
+          tables and uses HMS table stats for estimation.
+        </li>
+
+
+        <li class="li">
+          <code class="ph codeph">FALSE</code> or <code class="ph codeph">0</code>: Enables the normal sampling of HBase
+          tables.
+        </li>
+
+      </ul>
+
+    </div>
+
+
+    <p class="p">
+      <strong class="ph b">Type:</strong> <code class="ph codeph">BOOLEAN</code>
+    </p>
+
+
+    <p class="p">
+      <strong class="ph b">Default:</strong> <code class="ph codeph">FALSE</code>
+    </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
diff --git a/docs/build/html/topics/impala_disable_row_runtime_filtering.html b/docs/build/html/topics/impala_disable_row_runtime_filtering.html
index 1afecaa..e8a6474 100644
--- a/docs/build/html/topics/impala_disable_row_runtime_filtering.html
+++ b/docs/build/html/topics/impala_disable_row_runtime_filtering.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DISABLE_ROW_RUNTIME_FILTERING 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="disable_row_runtime_filtering" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_disable_streaming_preaggregations.html b/docs/build/html/topics/impala_disable_streaming_preaggregations.html
index 82e7690..4964abc 100644
--- a/docs/build/html/topics/impala_disable_streaming_preaggregations.html
+++ b/docs/build/html/topics/impala_disable_streaming_preaggregations.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DISABLE_STREAMING_PREAGGREGATIONS 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="disable_streaming_preaggregations" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_disable_unsafe_spills.html b/docs/build/html/topics/impala_disable_unsafe_spills.html
index 4cf8ee5..e26e2e6 100644
--- a/docs/build/html/topics/impala_disable_unsafe_spills.html
+++ b/docs/build/html/topics/impala_disable_unsafe_spills.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DISABLE_UNSAFE_SPILLS Query Option (Impala 2.0 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="disable_unsafe_spills" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_disk_space.html b/docs/build/html/topics/impala_disk_space.html
index dc2b72a..91eb163 100644
--- a/docs/build/html/topics/impala_disk_space.html
+++ b/docs/build/html/topics/impala_disk_space.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Managing Disk Space for Impala Data" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_admin.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="disk_space" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -23,28 +23,33 @@
 
   <h1 class="title topictitle1" id="ariaid-title1">Managing Disk Space for Impala Data</h1>
 
+
   
+
   
 
   <div class="body conbody">
 
     <p class="p">
-      Although Impala typically works with many large files in an HDFS storage system with plenty of capacity,
-      there are times when you might perform some file cleanup to reclaim space, or advise developers on techniques
-      to minimize space consumption and file duplication.
+      Although Impala typically works with many large files in an HDFS storage system with
+      plenty of capacity, there are times when you might perform some file cleanup to reclaim
+      space, or advise developers on techniques to minimize space consumption and file
+      duplication.
     </p>
 
 
     <ul class="ul">
       <li class="li">
         <p class="p">
-          Use compact binary file formats where practical. Numeric and time-based data in particular can be stored
-          in more compact form in binary data files. Depending on the file format, various compression and encoding
-          features can reduce file size even further. You can specify the <code class="ph codeph">STORED AS</code> clause as part
-          of the <code class="ph codeph">CREATE TABLE</code> statement, or <code class="ph codeph">ALTER TABLE</code> with the <code class="ph codeph">SET
-          FILEFORMAT</code> clause for an existing table or partition within a partitioned table. See
-          <a class="xref" href="impala_file_formats.html#file_formats">How Impala Works with Hadoop File Formats</a> for details about file formats, especially
-          <a class="xref" href="impala_parquet.html#parquet">Using the Parquet File Format with Impala Tables</a>. See <a class="xref" href="impala_create_table.html#create_table">CREATE TABLE Statement</a> and
+          Use compact binary file formats where practical. Numeric and time-based data in
+          particular can be stored in more compact form in binary data files. Depending on the
+          file format, various compression and encoding features can reduce file size even
+          further. You can specify the <code class="ph codeph">STORED AS</code> clause as part of the
+          <code class="ph codeph">CREATE TABLE</code> statement, or <code class="ph codeph">ALTER TABLE</code> with the
+          <code class="ph codeph">SET FILEFORMAT</code> clause for an existing table or partition within a
+          partitioned table. See <a class="xref" href="impala_file_formats.html#file_formats">How Impala Works with Hadoop File Formats</a>
+          for details about file formats, especially <a class="xref" href="impala_parquet.html#parquet">Using the Parquet File Format with Impala Tables</a>.
+          See <a class="xref" href="impala_create_table.html#create_table">CREATE TABLE Statement</a> and
           <a class="xref" href="impala_alter_table.html#alter_table">ALTER TABLE Statement</a> for syntax details.
         </p>
 
@@ -53,48 +58,53 @@
 
       <li class="li">
         <p class="p">
-          You manage underlying data files differently depending on whether the corresponding Impala table is
-          defined as an <a class="xref" href="impala_tables.html#internal_tables">internal</a> or
+          You manage underlying data files differently depending on whether the corresponding
+          Impala table is defined as an
+          <a class="xref" href="impala_tables.html#internal_tables">internal</a> or
           <a class="xref" href="impala_tables.html#external_tables">external</a> table:
         </p>
 
         <ul class="ul">
           <li class="li">
-            Use the <code class="ph codeph">DESCRIBE FORMATTED</code> statement to check if a particular table is internal
-            (managed by Impala) or external, and to see the physical location of the data files in HDFS. See
-            <a class="xref" href="impala_describe.html#describe">DESCRIBE Statement</a> for details.
+            Use the <code class="ph codeph">DESCRIBE FORMATTED</code> statement to check if a particular table
+            is internal (managed by Impala) or external, and to see the physical location of the
+            data files in HDFS. See <a class="xref" href="impala_describe.html#describe">DESCRIBE Statement</a>
+            for details.
           </li>
 
 
           <li class="li">
-            For Impala-managed (<span class="q">"internal"</span>) tables, use <code class="ph codeph">DROP TABLE</code> statements to remove
-            data files. See <a class="xref" href="impala_drop_table.html#drop_table">DROP TABLE Statement</a> for details.
+            For Impala-managed (<span class="q">"internal"</span>) tables, use <code class="ph codeph">DROP TABLE</code>
+            statements to remove data files. See
+            <a class="xref" href="impala_drop_table.html#drop_table">DROP TABLE Statement</a> for details.
           </li>
 
 
           <li class="li">
-            For tables not managed by Impala (<span class="q">"external"</span> tables), use appropriate HDFS-related commands such
-            as <code class="ph codeph">hadoop fs</code>, <code class="ph codeph">hdfs dfs</code>, or <code class="ph codeph">distcp</code>, to create, move,
-            copy, or delete files within HDFS directories that are accessible by the <code class="ph codeph">impala</code> user.
-            Issue a <code class="ph codeph">REFRESH <var class="keyword varname">table_name</var></code> statement after adding or removing any
-            files from the data directory of an external table. See <a class="xref" href="impala_refresh.html#refresh">REFRESH Statement</a> for
-            details.
+            For tables not managed by Impala (<span class="q">"external"</span> tables), use appropriate
+            HDFS-related commands such as <code class="ph codeph">hadoop fs</code>, <code class="ph codeph">hdfs dfs</code>,
+            or <code class="ph codeph">distcp</code>, to create, move, copy, or delete files within HDFS
+            directories that are accessible by the <code class="ph codeph">impala</code> user. Issue a
+            <code class="ph codeph">REFRESH <var class="keyword varname">table_name</var></code> statement after adding or
+            removing any files from the data directory of an external table. See
+            <a class="xref" href="impala_refresh.html#refresh">REFRESH Statement</a> for details.
           </li>
 
 
           <li class="li">
-            Use external tables to reference HDFS data files in their original location. With this technique, you
-            avoid copying the files, and you can map more than one Impala table to the same set of data files. When
-            you drop the Impala table, the data files are left undisturbed. See
-            <a class="xref" href="impala_tables.html#external_tables">External Tables</a> for details.
+            Use external tables to reference HDFS data files in their original location. With
+            this technique, you avoid copying the files, and you can map more than one Impala
+            table to the same set of data files. When you drop the Impala table, the data files
+            are left undisturbed. See <a class="xref" href="impala_tables.html#external_tables">External Tables</a> for
+            details.
           </li>
 
 
           <li class="li">
-            Use the <code class="ph codeph">LOAD DATA</code> statement to move HDFS files into the data directory for an Impala
-            table from inside Impala, without the need to specify the HDFS path of the destination directory. This
-            technique works for both internal and external tables. See
-            <a class="xref" href="impala_load_data.html#load_data">LOAD DATA Statement</a> for details.
+            Use the <code class="ph codeph">LOAD DATA</code> statement to move HDFS files into the data
+            directory for an Impala table from inside Impala, without the need to specify the
+            HDFS path of the destination directory. This technique works for both internal and
+            external tables. See <a class="xref" href="impala_load_data.html#load_data">LOAD DATA Statement</a> for details.
           </li>
 
         </ul>
@@ -104,11 +114,11 @@
 
       <li class="li">
         <p class="p">
-          Make sure that the HDFS trashcan is configured correctly. When you remove files from HDFS, the space
-          might not be reclaimed for use by other files until sometime later, when the trashcan is emptied. See
-          <a class="xref" href="impala_drop_table.html#drop_table">DROP TABLE Statement</a> for details. See
-          <a class="xref" href="impala_prereqs.html#prereqs_account">User Account Requirements</a> for permissions needed for the HDFS trashcan to operate
-          correctly.
+          Make sure that the HDFS trashcan is configured correctly. When you remove files from
+          HDFS, the space might not be reclaimed for use by other files until sometime later,
+          when the trashcan is emptied. See <a class="xref" href="impala_drop_table.html#drop_table">DROP TABLE Statement</a> for
+          details. See <a class="xref" href="impala_prereqs.html#prereqs_account">User Account Requirements</a> for permissions needed
+          for the HDFS trashcan to operate correctly.
         </p>
 
       </li>
@@ -125,14 +135,17 @@
 
       <li class="li">
         <p class="p">
-          Clean up temporary files after failed <code class="ph codeph">INSERT</code> statements. If an <code class="ph codeph">INSERT</code>
-          statement encounters an error, and you see a directory named <span class="ph filepath">.impala_insert_staging</span>
-          or <span class="ph filepath">_impala_insert_staging</span> left behind in the data directory for the table, it might
-          contain temporary data files taking up space in HDFS. You might be able to salvage these data files, for
-          example if they are complete but could not be moved into place due to a permission error. Or, you might
-          delete those files through commands such as <code class="ph codeph">hadoop fs</code> or <code class="ph codeph">hdfs dfs</code>, to
-          reclaim space before re-trying the <code class="ph codeph">INSERT</code>. Issue <code class="ph codeph">DESCRIBE FORMATTED
-          <var class="keyword varname">table_name</var></code> to see the HDFS path where you can check for temporary files.
+          Clean up temporary files after failed <code class="ph codeph">INSERT</code> statements. If an
+          <code class="ph codeph">INSERT</code> statement encounters an error, and you see a directory named
+          <span class="ph filepath">.impala_insert_staging</span> or
+          <span class="ph filepath">_impala_insert_staging</span> left behind in the data directory for the
+          table, it might contain temporary data files taking up space in HDFS. You might be
+          able to salvage these data files, for example if they are complete but could not be
+          moved into place due to a permission error. Or, you might delete those files through
+          commands such as <code class="ph codeph">hadoop fs</code> or <code class="ph codeph">hdfs dfs</code>, to reclaim
+          space before re-trying the <code class="ph codeph">INSERT</code>. Issue <code class="ph codeph">DESCRIBE FORMATTED
+          <var class="keyword varname">table_name</var></code> to see the HDFS path where you can check for
+          temporary files.
         </p>
 
       </li>
@@ -140,42 +153,158 @@
 
       <li class="li">
         <p class="p">
-        By default, intermediate files used during large sort, join, aggregation, or analytic
-        function operations are stored in the directory <span class="ph filepath">/tmp/impala-scratch</span>
-        . These files are removed when the operation finishes. (Multiple concurrent queries can
-        perform operations that use the <span class="q">"spill to disk"</span> technique, without any name
-        conflicts for these temporary files.) You can specify a different location by starting
-        the <span class="keyword cmdname">impalad</span> daemon with the
-        <code class="ph codeph">‑‑scratch_dirs="<var class="keyword varname">path_to_directory</var>"</code>
-        configuration option. You can specify a single directory, or a comma-separated list of
-        directories. The scratch directories must be on the local filesystem, not in HDFS. You
-        might specify different directory paths for different hosts, depending on the capacity
-        and speed of the available storage devices. In <span class="keyword">Impala 2.3</span> or
-        higher, Impala successfully starts (with a warning Impala successfully starts (with a
-        warning written to the log) if it cannot create or read and write files in one of the
-        scratch directories. If there is less than 1 GB free on the filesystem where that
-        directory resides, Impala still runs, but writes a warning message to its log. If Impala
-        encounters an error reading or writing files in a scratch directory during a query,
-        Impala logs the error and the query fails.
-      </p>
+          If you use the Amazon Simple Storage Service (S3) as a place to offload data to reduce
+          the volume of local storage, Impala 2.2.0 and higher can query the data directly from
+          S3. See <a class="xref" href="impala_s3.html#s3">Using Impala with Amazon S3 Object Store</a> for details.
+        </p>
 
       </li>
 
+    </ul>
 
-      <li class="li">
-        <p class="p">
-          If you use the Amazon Simple Storage Service (S3) as a place to offload
-          data to reduce the volume of local storage, Impala 2.2.0 and higher
-          can query the data directly from S3.
-          See <a class="xref" href="impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details.
-        </p>
 
-      </li>
+    <div class="section" id="disk_space__section_vrg_fjb_3jb"><h2 class="title sectiontitle">Configuring Scratch Space for Spilling to Disk</h2>
+
+      Impala uses intermediate files during large
+      sort, join, aggregation, or analytic function operations The files are
+      removed when the operation finishes. You can specify locations of the
+      intermediate files by starting the <span class="keyword cmdname">impalad</span> daemon with
+      the
+          <code class="ph codeph">‑‑scratch_dirs="<var class="keyword varname">path_to_directory</var>"</code>
+      configuration option. By default, intermediate files are stored in the
+      directory <span class="ph filepath">/tmp/impala-scratch</span>.<div class="p" id="disk_space__order_by_scratch_dir">
+        <ul class="ul">
+          <li class="li">
+            You can specify a single directory or a comma-separated list of directories.
+          </li>
+
+
+          <li class="li">
+            You can specify an optional a capacity quota per scratch directory using the colon
+            (:) as the delimiter.
+            <p class="p">
+              The capacity quota of <code class="ph codeph">-1</code> or <code class="ph codeph">0</code> is the same as no
+              quota for the directory.
+            </p>
+
+          </li>
+
+
+          <li class="li">
+            The scratch directories must be on the local filesystem, not in HDFS.
+          </li>
+
+
+          <li class="li">
+            You might specify different directory paths for different hosts, depending on the
+            capacity and speed of the available storage devices.
+          </li>
+
+        </ul>
+
+      </div>
+
+
+      <p class="p">
+        If there is less than 1 GB free on the filesystem where that directory resides, Impala
+        still runs, but writes a warning message to its log.
+      </p>
+
+
+      <p class="p">
+        Impala successfully starts (with a warning written to the log) if it cannot create or
+        read and write files in one of the scratch directories.
+      </p>
+
+
+      <div class="p">
+        The following are examples for specifying scratch directories.
+        
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="disk_space__table_a4d_myg_3jb" class="table" frame="border" border="1" rules="all"><colgroup><col /><col /></colgroup><thead class="thead" style="text-align:left;">
+              <tr class="row">
+                <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d66648e320">
+                  Config option
+                </th>
+
+                <th class="entry cellrowborder" style="text-align:left;vertical-align:top;" id="d66648e323">
+                  Description
+                </th>
+
+              </tr>
+
+            </thead>
+<tbody class="tbody">
+              <tr class="row">
+                <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d66648e320 ">
+                  <code class="ph codeph">--scratch_dirs=/dir1,/dir2</code>
+                </td>
+
+                <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d66648e323 ">
+                  Use /dir1 and /dir2 as scratch directories with no capacity quota.
+                </td>
+
+              </tr>
+
+              <tr class="row">
+                <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d66648e320 ">
+                  <code class="ph codeph">--scratch_dirs=/dir1,/dir2:25G</code>
+                </td>
+
+                <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d66648e323 ">
+                  Use /dir1 and /dir2 as scratch directories with no capacity quota on /dir1 and
+                  the 25GB quota on /dir2.
+                </td>
+
+              </tr>
+
+              <tr class="row">
+                <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d66648e320 ">
+                  <code class="ph codeph">--scratch_dirs=/dir1:5MB,/dir2</code>
+                </td>
+
+                <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d66648e323 ">
+                  Use /dir1 and /dir2 as scratch directories with the capacity quota of 5MB on
+                  /dir1 and no quota on /dir2.
+                </td>
+
+              </tr>
+
+              <tr class="row">
+                <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d66648e320 ">
+                  <code class="ph codeph">--scratch_dirs=/dir1:-1,/dir2:0</code>
+                </td>
+
+                <td class="entry cellrowborder" style="text-align:left;vertical-align:top;" headers="d66648e323 ">
+                  Use /dir1 and /dir2 as scratch directories with no capacity quota.
+                </td>
+
+              </tr>
+
+            </tbody>
+</table>
+</div>
+
+      </div>
+
+
+      <p class="p">
+        Allocation from a scratch directory will fail if the specified limit for the directory
+        is exceeded.
+      </p>
+
+
+      <p class="p">
+        If Impala encounters an error reading or writing files in a scratch directory during a
+        query, Impala logs the error, and the query fails.
+      </p>
+
+
+    </div>
 
-    </ul>
 
   </div>
 
+
 <div class="related-links">
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_admin.html">Impala Administration</a></div>
diff --git a/docs/build/html/topics/impala_distinct.html b/docs/build/html/topics/impala_distinct.html
index 1068ca6..b904d9b 100644
--- a/docs/build/html/topics/impala_distinct.html
+++ b/docs/build/html/topics/impala_distinct.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DISTINCT Operator" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_select.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="distinct" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_dml.html b/docs/build/html/topics/impala_dml.html
index 8d5d328..33c60c6 100644
--- a/docs/build/html/topics/impala_dml.html
+++ b/docs/build/html/topics/impala_dml.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DML Statements" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="dml" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -98,7 +98,7 @@
 
     <p class="p">
       Impala can perform DML operations for tables or partitions stored in the Amazon S3 filesystem
-      with <span class="keyword">Impala 2.6</span> and higher. See <a class="xref" href="impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details.
+      with <span class="keyword">Impala 2.6</span> and higher. See <a class="xref" href="impala_s3.html#s3">Using Impala with Amazon S3 Object Store</a> for details.
     </p>
 
 
diff --git a/docs/build/html/topics/impala_double.html b/docs/build/html/topics/impala_double.html
index 7195401..a1afdec 100644
--- a/docs/build/html/topics/impala_double.html
+++ b/docs/build/html/topics/impala_double.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DOUBLE Data Type" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="double" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_drop_database.html b/docs/build/html/topics/impala_drop_database.html
index 0a6c545..b2564c5 100644
--- a/docs/build/html/topics/impala_drop_database.html
+++ b/docs/build/html/topics/impala_drop_database.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DROP DATABASE 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="drop_database" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -155,7 +155,7 @@
         PARTITION</code> can create or remove folders as needed in the Amazon S3 system. Prior
         to <span class="keyword">Impala 2.6</span>, you had to create folders yourself and point
         Impala database, tables, or partitions at them, and manually remove folders when no
-        longer needed. See <a class="xref" href="../shared/../topics/impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details about reading
+        longer needed. See <a class="xref" href="../shared/../topics/impala_s3.html#s3">Using Impala with Amazon S3 Object Store</a> for details about reading
         and writing S3 data with Impala.
       </p>
 
diff --git a/docs/build/html/topics/impala_drop_function.html b/docs/build/html/topics/impala_drop_function.html
index 1443893..bdf5fa1 100644
--- a/docs/build/html/topics/impala_drop_function.html
+++ b/docs/build/html/topics/impala_drop_function.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DROP FUNCTION 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="drop_function" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_drop_role.html b/docs/build/html/topics/impala_drop_role.html
index e53e8d2..ba56b05 100644
--- a/docs/build/html/topics/impala_drop_role.html
+++ b/docs/build/html/topics/impala_drop_role.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DROP ROLE Statement (Impala 2.0 or higher only)" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="drop_role" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_drop_stats.html b/docs/build/html/topics/impala_drop_stats.html
index 634675c..01ede4a 100644
--- a/docs/build/html/topics/impala_drop_stats.html
+++ b/docs/build/html/topics/impala_drop_stats.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DROP STATS 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="drop_stats" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_drop_table.html b/docs/build/html/topics/impala_drop_table.html
index bed0dcd..252b2cf 100644
--- a/docs/build/html/topics/impala_drop_table.html
+++ b/docs/build/html/topics/impala_drop_table.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DROP TABLE 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="drop_table" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -155,36 +155,30 @@ drop table temporary.trivial;</code></pre>
       In <span class="keyword">Impala 2.6</span> and higher, as part of improved support for writing
       to S3, Impala also removes the associated folder when dropping an internal table
       that resides on S3.
-      See <a class="xref" href="impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details about working with S3 tables.
+      See <a class="xref" href="impala_s3.html#s3">Using Impala with Amazon S3 Object Store</a> for details about working with S3 tables.
     </p>
 
 
-    <div class="p">
-        For best compatibility with the S3 write support in <span class="keyword">Impala 2.6</span>
-        and higher:
-        <ul class="ul">
-          <li class="li">
-            Use native Hadoop techniques to create data files in S3 for querying through Impala.
-          </li>
+    <div class="p"> For best
+        compatibility with the S3 write support in <span class="keyword">Impala 2.6</span> and higher: <ul class="ul">
+          <li class="li"> Use native Hadoop techniques to create data files in S3 for
+            querying through Impala. </li>
 
-
-          <li class="li">
-            Use the <code class="ph codeph">PURGE</code> clause of <code class="ph codeph">DROP TABLE</code> when dropping
-            internal (managed) tables.
-          </li>
+          <li class="li"> Use the <code class="ph codeph">PURGE</code> clause of <code class="ph codeph">DROP
+              TABLE</code> when dropping internal (managed) tables. </li>
 
         </ul>
-
-        By default, when you drop an internal (managed) table, the data files are moved to the
-        HDFS trashcan. This operation is expensive for tables that reside on the Amazon S3
-        filesystem. Therefore, for S3 tables, prefer to use <code class="ph codeph">DROP TABLE
-        <var class="keyword varname">table_name</var> PURGE</code> rather than the default <code class="ph codeph">DROP
-        TABLE</code> statement. The <code class="ph codeph">PURGE</code> clause makes Impala delete the data
-        files immediately, skipping the HDFS trashcan. For the <code class="ph codeph">PURGE</code> clause to
-        work effectively, you must originally create the data files on S3 using one of the tools
-        from the Hadoop ecosystem, such as <code class="ph codeph">hadoop fs -cp</code>, or
-        <code class="ph codeph">INSERT</code> in Impala or Hive.
-      </div>
+ By default, when you drop an internal (managed) table, the data
+        files are moved to the HDFS trashcan. This operation is expensive for
+        tables that reside on the Amazon S3 object store. Therefore, for S3
+        tables, prefer to use <code class="ph codeph">DROP TABLE <var class="keyword varname">table_name</var>
+          PURGE</code> rather than the default <code class="ph codeph">DROP TABLE</code>
+        statement. The <code class="ph codeph">PURGE</code> clause makes Impala delete the
+        data files immediately, skipping the HDFS trashcan. For the
+          <code class="ph codeph">PURGE</code> clause to work effectively, you must originally
+        create the data files on S3 using one of the tools from the Hadoop
+        ecosystem, such as <code class="ph codeph">hadoop fs -cp</code>, or
+          <code class="ph codeph">INSERT</code> in Impala or Hive. </div>
 
 
     <p class="p">
@@ -194,7 +188,7 @@ drop table temporary.trivial;</code></pre>
         PARTITION</code> can create or remove folders as needed in the Amazon S3 system. Prior
         to <span class="keyword">Impala 2.6</span>, you had to create folders yourself and point
         Impala database, tables, or partitions at them, and manually remove folders when no
-        longer needed. See <a class="xref" href="../shared/../topics/impala_s3.html#s3">Using Impala with the Amazon S3 Filesystem</a> for details about reading
+        longer needed. See <a class="xref" href="../shared/../topics/impala_s3.html#s3">Using Impala with Amazon S3 Object Store</a> for details about reading
         and writing S3 data with Impala.
       </p>
 
diff --git a/docs/build/html/topics/impala_drop_view.html b/docs/build/html/topics/impala_drop_view.html
index a70a17f..b7530d8 100644
--- a/docs/build/html/topics/impala_drop_view.html
+++ b/docs/build/html/topics/impala_drop_view.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="DROP VIEW 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="drop_view" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_enable_expr_rewrites.html b/docs/build/html/topics/impala_enable_expr_rewrites.html
index 1ee6d9a..3326498 100644
--- a/docs/build/html/topics/impala_enable_expr_rewrites.html
+++ b/docs/build/html/topics/impala_enable_expr_rewrites.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="ENABLE_EXPR_REWRITES 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.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="enable_expr_rewrites" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_exec_single_node_rows_threshold.html b/docs/build/html/topics/impala_exec_single_node_rows_threshold.html
index 0290752..c6a5fe4 100644
--- a/docs/build/html/topics/impala_exec_single_node_rows_threshold.html
+++ b/docs/build/html/topics/impala_exec_single_node_rows_threshold.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="EXEC_SINGLE_NODE_ROWS_THRESHOLD Query Option (Impala 2.1 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="exec_single_node_rows_threshold" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_exec_time_limit_s.html b/docs/build/html/topics/impala_exec_time_limit_s.html
index 423f530..c7a7fb8 100644
--- a/docs/build/html/topics/impala_exec_time_limit_s.html
+++ b/docs/build/html/topics/impala_exec_time_limit_s.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="EXEC_TIME_LIMIT_S Query Option (Impala 2.12 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="exec_time_limit_s" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_explain.html b/docs/build/html/topics/impala_explain.html
index 6452c94..6c59621 100644
--- a/docs/build/html/topics/impala_explain.html
+++ b/docs/build/html/topics/impala_explain.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="EXPLAIN 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="explain" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_explain_level.html b/docs/build/html/topics/impala_explain_level.html
index 5ea9af3..6dcbcbb 100644
--- a/docs/build/html/topics/impala_explain_level.html
+++ b/docs/build/html/topics/impala_explain_level.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="EXPLAIN_LEVEL 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="explain_level" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_explain_plan.html b/docs/build/html/topics/impala_explain_plan.html
index 75a5c56..3013bca 100644
--- a/docs/build/html/topics/impala_explain_plan.html
+++ b/docs/build/html/topics/impala_explain_plan.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Understanding Impala Query Performance - EXPLAIN Plans and Query Profiles" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_performance.html" />
@@ -14,11 +14,11 @@
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="explain_plan" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -29,31 +29,34 @@
 
   <h1 class="title topictitle1" id="ariaid-title1">Understanding Impala Query Performance - EXPLAIN Plans and Query Profiles</h1>
 
+
   
+
   
 
   <div class="body conbody">
 
     <p class="p">
-      To understand the high-level performance considerations for Impala queries, read the output of the
-      <code class="ph codeph">EXPLAIN</code> statement for the query. You can get the <code class="ph codeph">EXPLAIN</code> plan without
-      actually running the query itself.
+      To understand the high-level performance considerations for Impala queries, read the
+      output of the <code class="ph codeph">EXPLAIN</code> statement for the query. You can get the
+      <code class="ph codeph">EXPLAIN</code> plan without actually running the query itself.
     </p>
 
 
     <p class="p">
-      For an overview of the physical performance characteristics for a query, issue the <code class="ph codeph">SUMMARY</code>
-      statement in <span class="keyword cmdname">impala-shell</span> immediately after executing a query. This condensed information
-      shows which phases of execution took the most time, and how the estimates for memory usage and number of rows
-      at each phase compare to the actual values.
+      For an overview of the physical performance characteristics for a query, issue the
+      <code class="ph codeph">SUMMARY</code> statement in <span class="keyword cmdname">impala-shell</span> immediately after
+      executing a query. This condensed information shows which phases of execution took the
+      most time, and how the estimates for memory usage and number of rows at each phase compare
+      to the actual values.
     </p>
 
 
     <p class="p">
-      To understand the detailed performance characteristics for a query, issue the <code class="ph codeph">PROFILE</code>
-      statement in <span class="keyword cmdname">impala-shell</span> immediately after executing a query. This low-level information
-      includes physical details about memory, CPU, I/O, and network usage, and thus is only available after the
-      query is actually run.
+      To understand the detailed performance characteristics for a query, issue the
+      <code class="ph codeph">PROFILE</code> statement in <span class="keyword cmdname">impala-shell</span> immediately after
+      executing a query. This low-level information includes physical details about memory, CPU,
+      I/O, and network usage, and thus is only available after the query is actually run.
     </p>
 
 
@@ -61,13 +64,13 @@
 
 
     <p class="p">
-      Also, see <a class="xref" href="impala_hbase.html#hbase_performance">Performance Considerations for the Impala-HBase Integration</a>
-      and <a class="xref" href="impala_s3.html#s3_performance">Understanding and Tuning Impala Query Performance for S3 Data</a>
-      for examples of interpreting
-      <code class="ph codeph">EXPLAIN</code> plans for queries against HBase tables
-      <span class="ph">and data stored in the Amazon Simple Storage System (S3)</span>.
+      Also, see <a class="xref" href="impala_hbase.html#hbase_performance">Performance Considerations for the Impala-HBase Integration</a> and
+      <a class="xref" href="impala_s3.html#s3_performance">Understanding and Tuning Impala Query Performance for S3 Data</a> for examples of interpreting
+      <code class="ph codeph">EXPLAIN</code> plans for queries against HBase tables <span class="ph">and data
+      stored in the Amazon Simple Storage System (S3)</span>.
     </p>
 
+
   </div>
 
 
@@ -83,11 +86,12 @@
     <div class="body conbody">
 
       <p class="p">
-        The <code class="ph codeph"><a class="xref" href="impala_explain.html#explain">EXPLAIN</a></code> statement gives you an outline
-        of the logical steps that a query will perform, such as how the work will be distributed among the nodes
-        and how intermediate results will be combined to produce the final result set. You can see these details
-        before actually running the query. You can use this information to check that the query will not operate in
-        some very unexpected or inefficient way.
+        The <code class="ph codeph"><a class="xref" href="impala_explain.html#explain">EXPLAIN</a></code> statement
+        gives you an outline of the logical steps that a query will perform, such as how the
+        work will be distributed among the nodes and how intermediate results will be combined
+        to produce the final result set. You can see these details before actually running the
+        query. You can use this information to check that the query will not operate in some
+        very unexpected or inefficient way.
       </p>
 
 
@@ -149,24 +153,28 @@
 
 
       <p class="p">
-        The <code class="ph codeph">EXPLAIN</code> plan is also printed at the beginning of the query profile report described in
-        <a class="xref" href="#perf_profile">Using the Query Profile for Performance Tuning</a>, for convenience in examining both the logical and physical aspects of the
-        query side-by-side.
+        The <code class="ph codeph">EXPLAIN</code> plan is also printed at the beginning of the query profile
+        report described in <a class="xref" href="#perf_profile">Using the Query Profile for Performance Tuning</a>, for convenience in examining both the
+        logical and physical aspects of the query side-by-side.
       </p>
 
 
       <p class="p">
-        The amount of detail displayed in the <code class="ph codeph">EXPLAIN</code> output is controlled by the
-        <a class="xref" href="impala_explain_level.html#explain_level">EXPLAIN_LEVEL</a> query option. You typically
-        increase this setting from <code class="ph codeph">standard</code> to <code class="ph codeph">extended</code> (or from <code class="ph codeph">1</code>
-        to <code class="ph codeph">2</code>) when doublechecking the presence of table and column statistics during performance
-        tuning, or when estimating query resource usage in conjunction with the resource management features.
+        The amount of detail displayed in the <code class="ph codeph">EXPLAIN</code> output is controlled by
+        the <a class="xref" href="impala_explain_level.html#explain_level">EXPLAIN_LEVEL</a> query
+        option. You typically increase this setting from <code class="ph codeph">standard</code> to
+        <code class="ph codeph">extended</code> (or from <code class="ph codeph">1</code> to <code class="ph codeph">2</code>) when
+        doublechecking the presence of table and column statistics during performance tuning, or
+        when estimating query resource usage in conjunction with the resource management
+        features.
       </p>
 
 
-      
+
+
     </div>
 
+
   </div>
 
 
@@ -178,77 +186,71 @@
     <div class="body conbody">
 
       <p class="p">
-        The <code class="ph codeph"><a class="xref" href="impala_shell_commands.html#shell_commands">SUMMARY</a></code> command within
-        the <span class="keyword cmdname">impala-shell</span> interpreter gives you an easy-to-digest overview of the timings for the
-        different phases of execution for a query. Like the <code class="ph codeph">EXPLAIN</code> plan, it is easy to see
-        potential performance bottlenecks. Like the <code class="ph codeph">PROFILE</code> output, it is available after the
-        query is run and so displays actual timing numbers.
+        The
+        <code class="ph codeph"><a class="xref" href="impala_shell_commands.html#shell_commands">SUMMARY</a></code>
+        command within the <span class="keyword cmdname">impala-shell</span> interpreter gives you an
+        easy-to-digest overview of the timings for the different phases of execution for a
+        query. Like the <code class="ph codeph">EXPLAIN</code> plan, it is easy to see potential performance
+        bottlenecks. Like the <code class="ph codeph">PROFILE</code> output, it is available after the query
+        is run and so displays actual timing numbers.
       </p>
 
 
       <p class="p">
-        The <code class="ph codeph">SUMMARY</code> report is also printed at the beginning of the query profile report described
-        in <a class="xref" href="#perf_profile">Using the Query Profile for Performance Tuning</a>, for convenience in examining high-level and low-level aspects of the query
-        side-by-side.
+        The <code class="ph codeph">SUMMARY</code> report is also printed at the beginning of the query
+        profile report described in <a class="xref" href="#perf_profile">Using the Query Profile for Performance Tuning</a>, for convenience in examining
+        high-level and low-level aspects of the query side-by-side.
       </p>
 
 
       <p class="p">
-        For example, here is a query involving an aggregate function, on a single-node VM. The different stages of
-        the query and their timings are shown (rolled up for all nodes), along with estimated and actual values
-        used in planning the query. In this case, the <code class="ph codeph">AVG()</code> function is computed for a subset of
-        data on each node (stage 01) and then the aggregated results from all nodes are combined at the end (stage
-        03). You can see which stages took the most time, and whether any estimates were substantially different
-        than the actual data distribution. (When examining the time values, be sure to consider the suffixes such
-        as <code class="ph codeph">us</code> for microseconds and <code class="ph codeph">ms</code> for milliseconds, rather than just looking
-        for the largest numbers.)
+        When the <code class="ph codeph">MT_DOP</code> query option is set to a value larger than
+        <code class="ph codeph">0</code>, the <code class="ph codeph">#Inst</code> column in the output shows the number of
+        fragment instances. Impala decomposes each query into smaller units of work that are
+        distributed across the cluster, and these units are referred as fragments.
       </p>
 
 
-<pre class="pre codeblock"><code>[localhost:21000] &gt; select avg(ss_sales_price) from store_sales where ss_coupon_amt = 0;
-+---------------------+
-| avg(ss_sales_price) |
-+---------------------+
-| 37.80770926328327   |
-+---------------------+
-[localhost:21000] &gt; summary;
-+--------------+--------+----------+----------+-------+------------+----------+---------------+-----------------+
-| Operator     | #Hosts | Avg Time | Max Time | #Rows | Est. #Rows | Peak Mem | Est. Peak Mem | Detail          |
-+--------------+--------+----------+----------+-------+------------+----------+---------------+-----------------+
-| 03:AGGREGATE | 1      | 1.03ms   | 1.03ms   | 1     | 1          | 48.00 KB | -1 B          | MERGE FINALIZE  |
-| 02:EXCHANGE  | 1      | 0ns      | 0ns      | 1     | 1          | 0 B      | -1 B          | UNPARTITIONED   |
-| 01:AGGREGATE | 1      | 30.79ms  | 30.79ms  | 1     | 1          | 80.00 KB | 10.00 MB      |                 |
-| 00:SCAN HDFS | 1      | 5.45s    | 5.45s    | 2.21M | -1         | 64.05 MB | 432.00 MB     | tpc.store_sales |
-+--------------+--------+----------+----------+-------+------------+----------+---------------+-----------------+
-</code></pre>
-
       <p class="p">
-        Notice how the longest initial phase of the query is measured in seconds (s), while later phases working on
-        smaller intermediate results are measured in milliseconds (ms) or even nanoseconds (ns).
+        When the <code class="ph codeph">MT_DOP</code> query option is set to 0, the <code class="ph codeph">#Inst</code>
+        column in the output shows the same value as the <code class="ph codeph">#Hosts</code> column, since
+        there is exactly one fragment for each host.
       </p>
 
 
       <p class="p">
-        Here is an example from a more complicated query, as it would appear in the <code class="ph codeph">PROFILE</code>
-        output:
+        For example, here is a query involving an aggregate function, on a single-node cluster.
+        The different stages of the query and their timings are shown (rolled up for all nodes),
+        along with estimated and actual values used in planning the query. In this case, the
+        <code class="ph codeph">AVG()</code> function is computed for a subset of data on each node (stage 01)
+        and then the aggregated results from all nodes are combined at the end (stage 03). You
+        can see which stages took the most time, and whether any estimates were substantially
+        different than the actual data distribution.
       </p>
 
 
-<pre class="pre codeblock"><code>Operator              #Hosts   Avg Time   Max Time    #Rows  Est. #Rows  Peak Mem  Est. Peak Mem  Detail
-------------------------------------------------------------------------------------------------------------------------
-09:MERGING-EXCHANGE        1   79.738us   79.738us        5           5         0        -1.00 B  UNPARTITIONED
-05:TOP-N                   3   84.693us   88.810us        5           5  12.00 KB       120.00 B
-04:AGGREGATE               3    5.263ms    6.432ms        5           5  44.00 KB       10.00 MB  MERGE FINALIZE
-08:AGGREGATE               3   16.659ms   27.444ms   52.52K     600.12K   3.20 MB       15.11 MB  MERGE
-07:EXCHANGE                3    2.644ms      5.1ms   52.52K     600.12K         0              0  HASH(o_orderpriority)
-03:AGGREGATE               3  342.913ms  966.291ms   52.52K     600.12K  10.80 MB       15.11 MB
-02:HASH JOIN               3    2s165ms    2s171ms  144.87K     600.12K  13.63 MB      941.01 KB  INNER JOIN, BROADCAST
-|--06:EXCHANGE             3    8.296ms    8.692ms   57.22K      15.00K         0              0  BROADCAST
-|  01:SCAN HDFS            2    1s412ms    1s978ms   57.22K      15.00K  24.21 MB      176.00 MB  tpch.orders o
-00:SCAN HDFS               3    8s032ms    8s558ms    3.79M     600.12K  32.29 MB      264.00 MB  tpch.lineitem l
+<pre class="pre codeblock"><code>&gt; SELECT AVG(ss_sales_price) FROM store_sales WHERE ss_coupon_amt = 0;
+&gt; SUMMARY;
++--------------+--------+--------+----------+----------+-------+------------+----------+---------------+-----------------+
+| Operator     | #Hosts | #Inst  | Avg Time | Max Time | #Rows | Est. #Rows | Peak Mem | Est. Peak Mem | Detail          |
++--------------+--------+--------+----------+----------+-------+------------+----------+---------------+-----------------+
+| 03:AGGREGATE | 1      | 1      | 1.03ms   | 1.03ms   | 1     | 1          | 48.00 KB | -1 B          | MERGE FINALIZE  |
+| 02:EXCHANGE  | 1      | 1      | 0ns      | 0ns      | 1     | 1          | 0 B      | -1 B          | UNPARTITIONED   |
+| 01:AGGREGATE | 1      | 1      |30.79ms   | 30.79ms  | 1     | 1          | 80.00 KB | 10.00 MB      |                 |
+| 00:SCAN HDFS | 1      | 1      | 5.45s    | 5.45s    | 2.21M | -1         | 64.05 MB | 432.00 MB     | tpc.store_sales |
++--------------+--------+--------+----------+----------+-------+------------+----------+---------------+-----------------+
 </code></pre>
+
+      <p class="p">
+        Notice how the longest initial phase of the query is measured in seconds (s), while
+        later phases working on smaller intermediate results are measured in milliseconds (ms)
+        or even nanoseconds (ns).
+      </p>
+
+
     </div>
 
+
   </div>
 
 
@@ -259,78 +261,102 @@
 
     <div class="body conbody">
 
-      <p class="p"> The <code class="ph codeph">PROFILE</code> command, available in the
-          <span class="keyword cmdname">impala-shell</span> interpreter, produces a detailed
-        low-level report showing how the most recent query was executed. Unlike
-        the <code class="ph codeph">EXPLAIN</code> plan described in <a class="xref" href="#perf_explain">Using the EXPLAIN Plan for Performance Tuning</a>, this information is only available after the
-        query has finished. It shows physical details such as the number of
-        bytes read, maximum memory usage, and so on for each node. You can use
-        this information to determine if the query is I/O-bound or CPU-bound,
-        whether some network condition is imposing a bottleneck, whether a
-        slowdown is affecting some nodes but not others, and to check that
-        recommended configuration settings such as short-circuit local reads are
-        in effect. </p>
+      <p class="p">
+        The <code class="ph codeph">PROFILE</code> command, available in the <span class="keyword cmdname">impala-shell</span>
+        interpreter, produces a detailed low-level report showing how the most recent query was
+        executed. Unlike the <code class="ph codeph">EXPLAIN</code> plan described in
+        <a class="xref" href="#perf_explain">Using the EXPLAIN Plan for Performance Tuning</a>, this information is only available after the
+        query has finished. It shows physical details such as the number of bytes read, maximum
+        memory usage, and so on for each node. You can use this information to determine if the
+        query is I/O-bound or CPU-bound, whether some network condition is imposing a
+        bottleneck, whether a slowdown is affecting some nodes but not others, and to check that
+        recommended configuration settings such as short-circuit local reads are in effect.
+      </p>
+
+
+      <p class="p">
+        By default, time values in the profile output reflect the wall-clock time taken by an
+        operation. For values denoting system time or user time, the measurement unit is
+        reflected in the metric name, such as <code class="ph codeph">ScannerThreadsSysTime</code> or
+        <code class="ph codeph">ScannerThreadsUserTime</code>. For example, a multi-threaded I/O operation
+        might show a small figure for wall-clock time, while the corresponding system time is
+        larger, representing the sum of the CPU time taken by each thread. Or a wall-clock time
+        figure might be larger because it counts time spent waiting, while the corresponding
+        system and user time figures only measure the time while the operation is actively using
+        CPU cycles.
+      </p>
 
 
       <p class="p">
-        By default, time values in the profile output reflect the wall-clock time taken by an operation.
-        For values denoting system time or user time, the measurement unit is reflected in the metric
-        name, such as <code class="ph codeph">ScannerThreadsSysTime</code> or <code class="ph codeph">ScannerThreadsUserTime</code>.
-        For example, a multi-threaded I/O operation might show a small figure for wall-clock time,
-        while the corresponding system time is larger, representing the sum of the CPU time taken by each thread.
-        Or a wall-clock time figure might be larger because it counts time spent waiting, while
-        the corresponding system and user time figures only measure the time while the operation
-        is actively using CPU cycles.
+        The <a class="xref" href="impala_explain_plan.html#perf_explain"><code class="ph codeph">EXPLAIN</code>
+        plan</a> is also printed at the beginning of the query profile report, for
+        convenience in examining both the logical and physical aspects of the query
+        side-by-side. The
+        <a class="xref" href="impala_explain_level.html#explain_level">EXPLAIN_LEVEL</a> query option
+        also controls the verbosity of the <code class="ph codeph">EXPLAIN</code> output printed by the
+        <code class="ph codeph">PROFILE</code> command.
       </p>
 
 
       <p class="p">
-        The <a class="xref" href="impala_explain_plan.html#perf_explain"><code class="ph codeph">EXPLAIN</code> plan</a> is also printed
-        at the beginning of the query profile report, for convenience in examining both the logical and physical
-        aspects of the query side-by-side. The
-        <a class="xref" href="impala_explain_level.html#explain_level">EXPLAIN_LEVEL</a> query option also controls the
-        verbosity of the <code class="ph codeph">EXPLAIN</code> output printed by the <code class="ph codeph">PROFILE</code> command.
+        In <span class="keyword">Impala 3.2</span>, a new <code class="ph codeph">Per Node Profiles</code> section
+        was added to the profile output. The new section includes the following metrics that can
+        be controlled by the
+        <code class="ph codeph"><a class="xref" href="impala_resource_trace_ratio.html#resource_trace_ratio">RESOURCE_TRACE_RATIO</a></code>
+        query option.
       </p>
 
-      <p class="p">In <span class="keyword">Impala 3.2</span>, a new <code class="ph codeph">Per Node
-          Profiles</code> section was added to the profile output. The new
-        section includes the following metrics that can be controlled by the
-            <code class="ph codeph"><a class="xref" href="impala_resource_trace_ratio.html#resource_trace_ratio">RESOURCE_TRACE_RATIO</a></code> query option.</p>
 
       <ul class="ul">
-        <li class="li"><code class="ph codeph">CpuIoWaitPercentage</code>
+        <li class="li">
+          <code class="ph codeph">CpuIoWaitPercentage</code>
         </li>
 
-        <li class="li"><code class="ph codeph">CpuSysPercentage</code></li>
 
-        <li class="li"><code class="ph codeph">CpuUserPercentage</code></li>
+        <li class="li">
+          <code class="ph codeph">CpuSysPercentage</code>
+        </li>
 
-        <li class="li"><code class="ph codeph">HostDiskReadThroughput</code>: All data read by the host
-          as part of the execution of this query (spilling), by the HDFS data
-          node, and by other processes running on the same system.</li>
 
-        <li class="li"><code class="ph codeph">HostDiskWriteThroughput</code>: All data written by the
-          host as part of the execution of this query (spilling), by the HDFS
-          data node, and by other processes running on the same system.</li>
+        <li class="li">
+          <code class="ph codeph">CpuUserPercentage</code>
+        </li>
 
-        <li class="li"><code class="ph codeph">HostNetworkRx</code>: All data received by the host as
-          part of the execution of this query, other queries, and other
-          processes running on the same system. </li>
 
-        <li class="li"><code class="ph codeph">HostNetworkTx</code>: All data transmitted by the host as
-          part of the execution of this query, other queries, and other
-          processes running on the same system. </li>
+        <li class="li">
+          <code class="ph codeph">HostDiskReadThroughput</code>: All data read by the host as part of the
+          execution of this query (spilling), by the HDFS data node, and by other processes
+          running on the same system.
+        </li>
 
-      </ul>
 
-      
+        <li class="li">
+          <code class="ph codeph">HostDiskWriteThroughput</code>: All data written by the host as part of the
+          execution of this query (spilling), by the HDFS data node, and by other processes
+          running on the same system.
+        </li>
 
-      
+
+        <li class="li">
+          <code class="ph codeph">HostNetworkRx</code>: All data received by the host as part of the execution
+          of this query, other queries, and other processes running on the same system.
+        </li>
+
+
+        <li class="li">
+          <code class="ph codeph">HostNetworkTx</code>: All data transmitted by the host as part of the
+          execution of this query, other queries, and other processes running on the same
+          system.
+        </li>
+
+      </ul>
 
 
     </div>
 
+
   </div>
 
+
 </body>
 </html>
\ No newline at end of file
diff --git a/docs/build/html/topics/impala_faq.html b/docs/build/html/topics/impala_faq.html
index 555b68c..d36553e 100644
--- a/docs/build/html/topics/impala_faq.html
+++ b/docs/build/html/topics/impala_faq.html
@@ -4,14 +4,14 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Frequently Asked Questions" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="faq" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_fetch_rows_timeout_ms.html b/docs/build/html/topics/impala_fetch_rows_timeout_ms.html
new file mode 100644
index 0000000..5a0b607
--- /dev/null
+++ b/docs/build/html/topics/impala_fetch_rows_timeout_ms.html
@@ -0,0 +1,71 @@
+<?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 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
+<meta name="DC.Type" content="concept" />
+<meta name="DC.Title" content="FETCH_ROWS_TIMEOUT_MS 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.4.x" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="FETCH_ROWS_TIMEOUT_MS" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>FETCH_ROWS_TIMEOUT_MS Query Option</title>
+</head>
+<body id="FETCH_ROWS_TIMEOUT_MS">
+
+  <h1 class="title topictitle1" id="ariaid-title1">FETCH_ROWS_TIMEOUT_MS Query Option</h1>
+
+  
+  
+  <div class="body conbody">
+    <p class="p">Use the <code class="ph codeph">FETCH_ROWS_TIMEOUT_MS</code> query option to control
+      how long Impala waits for query results when clients fetch rows.</p>
+
+    <p class="p"> When this query option is set to <code class="ph codeph">0</code>, fetch requests wait
+      indefinitely.</p>
+
+    <div class="p">The timeout applies both when query result spooling is enabled and disabled:<ul class="ul">
+        <li class="li">When result spooling is disabled (<code class="ph codeph">SPOOL_QUERY_RESULTS =
+            FALSE</code>), the timeout controls how long a client waits for a
+          single row batch to be produced by the coordinator. </li>
+
+        <li class="li">When result spooling is enabled ( (<code class="ph codeph">SPOOL_QUERY_RESULTS =
+            TRUE</code>), a client can fetch multiple row batches at a time,
+          so this timeout controls the total time a client waits for row batches
+          to be produced.</li>
+
+      </ul>
+</div>
+
+    <p class="p">The timeout also applies to fetch requests issued against queries in the
+      'RUNNING' state. A 'RUNNING' query has no rows available, so any fetch
+      request will wait until the query transitions to the 'FINISHED' state and
+      for it to fetch all requested rows. A query in the 'FINISHED' state means
+      that the rows are available to be fetched.</p>
+
+    <p class="p"><strong class="ph b">Type:</strong>
+      <code class="ph codeph">INT</code></p>
+
+    <p class="p"><strong class="ph b">Default:</strong>
+      <code class="ph codeph">10000</code> (10 seconds)</p>
+
+    <p class="p"><strong class="ph b">Added in:</strong>
+      <span class="keyword">Impala 3.4</span></p>
+
+    <p class="p"><strong class="ph b">Related information:</strong>
+      <a class="xref" href="impala_max_result_spooling_mem.html#MAX_RESULT_SPOOLING_MEM">MAX_RESULT_SPOOLING_MEM Query Option</a>,
+        <a class="xref" href="impala_max_spilled_result_spooling_mem.html#MAX_SPILLED_RESULT_SPOOLING_MEM">MAX_SPILLED_RESULT_SPOOLING_MEM Query Option</a>, <a class="xref" href="impala_spool_query_results.html#SPOOL_QUERY_RESULTS">SPOOL_QUERY_RESULTS Query Option</a></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
diff --git a/docs/build/html/topics/impala_file_formats.html b/docs/build/html/topics/impala_file_formats.html
index a8f1885..c900804 100644
--- a/docs/build/html/topics/impala_file_formats.html
+++ b/docs/build/html/topics/impala_file_formats.html
@@ -4,20 +4,21 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="How Impala Works with Hadoop File Formats" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_txtfile.html" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_parquet.html" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_orc.html" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_avro.html" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_hudi.html" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_rcfile.html" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_seqfile.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="file_formats" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -72,23 +73,23 @@
     
 <div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" class="table" frame="border" border="1" rules="all"><colgroup><col style="width:10%" /><col style="width:10%" /><col style="width:20%" /><col style="width:30%" /><col style="width:30%" /></colgroup><thead class="thead" style="text-align:left;">
           <tr class="row">
-            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d68905e92">
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d72274e92">
               File Type
             </th>
 
-            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d68905e95">
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d72274e95">
               Format
             </th>
 
-            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d68905e98">
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d72274e98">
               Compression Codecs
             </th>
 
-            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d68905e101">
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d72274e101">
               Impala Can CREATE?
             </th>
 
-            <th class="entry cell-norowborder" style="vertical-align:top;" id="d68905e104">
+            <th class="entry cell-norowborder" style="vertical-align:top;" id="d72274e104">
               Impala Can INSERT?
             </th>
 
@@ -97,21 +98,21 @@
         </thead>
 <tbody class="tbody">
           <tr id="file_formats__parquet_support" class="row">
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e92 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e92 ">
               <a class="xref" href="impala_parquet.html#parquet">Parquet</a>
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e95 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e95 ">
               Structured
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e98 "> Snappy, gzip, zstd, lz4; currently Snappy by default </td>
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e98 ">Snappy, gzip, zstd, lz4; currently Snappy by default </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e101 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e101 ">
               Yes.
             </td>
 
-            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d68905e104 ">
+            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d72274e104 ">
               Yes: <code class="ph codeph">CREATE TABLE</code>, <code class="ph codeph">INSERT</code>, <code class="ph codeph">LOAD
               DATA</code>, and query.
             </td>
@@ -119,30 +120,25 @@
           </tr>
 
           <tr id="file_formats__orc_support" class="row">
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e92 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e92 ">
               <a class="xref" href="impala_orc.html#orc">ORC</a>
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e95 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e95 ">
               Structured
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e98 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e98 ">
               gzip, Snappy, LZO, LZ4; currently gzip by default
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e101 ">
-              Yes, in Impala 2.12.0 and higher.
-
-              <p class="p">
-                The ORC support is an experimental feature since Impala-2.12. To disable it, set
-                <code class="ph codeph">--enable_orc_scanner</code> to <code class="ph codeph">false</code> when starting
-                the cluster.
-              </p>
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e101 "> Yes, in Impala 2.12.0 and higher. <p class="p">By default, ORC reads are enabled in Impala
+              3.4.0 and higher. To disable, set <code class="ph codeph">--enable_orc_scanner</code> to 
+              <code class="ph codeph">false</code> when starting the cluster. </p>
 
             </td>
 
-            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d68905e104 ">
+            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d72274e104 ">
               No. Import data by using <code class="ph codeph">LOAD DATA</code> on data files already in the
               right format, or use <code class="ph codeph">INSERT</code> in Hive followed by <code class="ph codeph">REFRESH
               <var class="keyword varname">table_name</var></code> in Impala.
@@ -151,51 +147,51 @@
           </tr>
 
           <tr id="file_formats__txtfile_support" class="row">
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e92 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e92 ">
               <a class="xref" href="impala_txtfile.html#txtfile">Text</a>
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e95 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e95 ">
               Unstructured
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e98 ">
-              LZO, gzip, bzip2, Snappy
-            </td>
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e98 ">bzip2, deflate, gzip, LZO, Snappy, zstd</td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e101 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e101 ">
               Yes. For <code class="ph codeph">CREATE TABLE</code> with no <code class="ph codeph">STORED AS</code> clause,
               the default file format is uncompressed text, with values separated by ASCII
               <code class="ph codeph">0x01</code> characters (typically represented as Ctrl-A).
             </td>
 
-            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d68905e104 ">
-              Yes: <code class="ph codeph">CREATE TABLE</code>, <code class="ph codeph">INSERT</code>, <code class="ph codeph">LOAD
-              DATA</code>, and query. If LZO compression is used, you must create the table
-              and load data in Hive. If other kinds of compression are used, you must load data
-              through <code class="ph codeph">LOAD DATA</code>, Hive, or manually in HDFS.
-            </td>
+            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d72274e104 "> Yes if uncompressed.<p class="p">No if compressed.</p>
+<p class="p">If LZO
+                compression is used, you must create the table and load data in
+                Hive.</p>
+<p class="p">If other kinds of compression are used, you must
+                load data through <code class="ph codeph">LOAD DATA</code>, Hive, or manually
+                in HDFS. </p>
+</td>
 
           </tr>
 
           <tr id="file_formats__avro_support" class="row">
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e92 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e92 ">
               <a class="xref" href="impala_avro.html#avro">Avro</a>
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e95 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e95 ">
               Structured
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e98 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e98 ">
               Snappy, gzip, deflate
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e101 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e101 ">
               Yes, in Impala 1.4.0 and higher. In lower versions, create the table using Hive.
             </td>
 
-            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d68905e104 ">
+            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d72274e104 ">
               No. Import data by using <code class="ph codeph">LOAD DATA</code> on data files already in the
               right format, or use <code class="ph codeph">INSERT</code> in Hive followed by <code class="ph codeph">REFRESH
               <var class="keyword varname">table_name</var></code> in Impala.
@@ -204,24 +200,40 @@
 
           </tr>
 
+          <tr id="file_formats__hudi_support" class="row">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e92 ">
+              <a class="xref" href="impala_hudi.html#hudi">Hudi</a>
+            </td>
+
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e95 ">Structured</td>
+
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e98 ">Snappy, gzip, zstd, lz4; currently Snappy by default </td>
+
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e101 ">Yes, support for Read Optimized Queries is experimental.</td>
+
+            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d72274e104 ">No. Create an external table in Impala. Set the table location to the Hudi table
+              directory. Alternatively, create the Hudi table in Hive. </td>
+
+          </tr>
+
           <tr id="file_formats__rcfile_support" class="row">
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e92 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e92 ">
               <a class="xref" href="impala_rcfile.html#rcfile">RCFile</a>
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e95 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e95 ">
               Structured
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e98 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e98 ">
               Snappy, gzip, deflate, bzip2
             </td>
 
-            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d68905e101 ">
+            <td class="entry nocellnorowborder" style="vertical-align:top;" headers="d72274e101 ">
               Yes.
             </td>
 
-            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d68905e104 ">
+            <td class="entry cell-norowborder" style="vertical-align:top;" headers="d72274e104 ">
               No. Import data by using <code class="ph codeph">LOAD DATA</code> on data files already in the
               right format, or use <code class="ph codeph">INSERT</code> in Hive followed by <code class="ph codeph">REFRESH
               <var class="keyword varname">table_name</var></code> in Impala.
@@ -231,23 +243,23 @@
           </tr>
 
           <tr id="file_formats__sequencefile_support" class="row">
-            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d68905e92 ">
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d72274e92 ">
               <a class="xref" href="impala_seqfile.html#seqfile">SequenceFile</a>
             </td>
 
-            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d68905e95 ">
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d72274e95 ">
               Structured
             </td>
 
-            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d68905e98 ">
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d72274e98 ">
               Snappy, gzip, deflate, bzip2
             </td>
 
-            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d68905e101 ">
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d72274e101 ">
               Yes.
             </td>
 
-            <td class="entry cellrowborder" style="vertical-align:top;" headers="d68905e104 ">
+            <td class="entry cellrowborder" style="vertical-align:top;" headers="d72274e104 ">
               No. Import data by using <code class="ph codeph">LOAD DATA</code> on data files already in the
               right format, or use <code class="ph codeph">INSERT</code> in Hive followed by <code class="ph codeph">REFRESH
               <var class="keyword varname">table_name</var></code> in Impala.
@@ -313,9 +325,7 @@
 
 
         <dd class="dd">
-          <p class="p">
-            Not supported for text files.
-          </p>
+          <p class="p"> Supported for AVRO, RC, Sequence, and text files. </p>
 
         </dd>
 
@@ -360,7 +370,7 @@
       
         <dt class="dt dlterm">Zstd</dt>
 
-        <dd class="dd">For Parquet files only.</dd>
+        <dd class="dd">For Parquet and text files only.</dd>
 
       
 
@@ -386,6 +396,8 @@
 </li>
 <li class="link ulchildlink"><strong><a href="../topics/impala_avro.html">Using the Avro File Format with Impala Tables</a></strong><br />
 </li>
+<li class="link ulchildlink"><strong><a href="../topics/impala_hudi.html">Using the Hudi File Format</a></strong><br />
+</li>
 <li class="link ulchildlink"><strong><a href="../topics/impala_rcfile.html">Using the RCFile File Format with Impala Tables</a></strong><br />
 </li>
 <li class="link ulchildlink"><strong><a href="../topics/impala_seqfile.html">Using the SequenceFile File Format with Impala Tables</a></strong><br />
diff --git a/docs/build/html/topics/impala_fixed_issues.html b/docs/build/html/topics/impala_fixed_issues.html
index 71c6573..6391c98 100644
--- a/docs/build/html/topics/impala_fixed_issues.html
+++ b/docs/build/html/topics/impala_fixed_issues.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Fixed Issues in Apache Impala" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_release_notes.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="fixed_issues" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_float.html b/docs/build/html/topics/impala_float.html
index 64f30fc..e74114e 100644
--- a/docs/build/html/topics/impala_float.html
+++ b/docs/build/html/topics/impala_float.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="FLOAT Data Type" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="float" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_functions.html b/docs/build/html/topics/impala_functions.html
index 0ec0c3f..28d7f1b 100644
--- a/docs/build/html/topics/impala_functions.html
+++ b/docs/build/html/topics/impala_functions.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Impala Built-In Functions" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_langref.html" />
@@ -20,8 +20,8 @@
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_analytic_functions.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="builtins" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -715,6 +715,38 @@
 
           <tr class="row">
             <td class="entry nocellnorowborder" style="vertical-align:top;">
+              <a class="xref" href="impala_string_functions.html#string_functions__jaro_distance">JARO_DISTANCE,
+              JARO_DIST</a>
+            </td>
+
+          </tr>
+
+          <tr class="row">
+            <td class="entry nocellnorowborder" style="vertical-align:top;">
+              <a class="xref" href="impala_string_functions.html#string_functions__jaro_similarity">JARO_SIMILARITY,
+              JARO_SIM</a>
+            </td>
+
+          </tr>
+
+          <tr class="row">
+            <td class="entry nocellnorowborder" style="vertical-align:top;">
+              <a class="xref" href="impala_string_functions.html#string_functions__jaro_winkler_distance">JARO_WINKER_DISTANCE,
+              JW_DST</a>
+            </td>
+
+          </tr>
+
+          <tr class="row">
+            <td class="entry nocellnorowborder" style="vertical-align:top;">
+              <a class="xref" href="impala_string_functions.html#string_functions__jaro_winkler_similarity">JARO_WINKER_SIMILARITY,
+              JW_SIM</a>
+            </td>
+
+          </tr>
+
+          <tr class="row">
+            <td class="entry nocellnorowborder" style="vertical-align:top;">
               <a class="xref" href="impala_analytic_functions.html#lag">LAG</a>
             </td>
 
diff --git a/docs/build/html/topics/impala_functions_overview.html b/docs/build/html/topics/impala_functions_overview.html
index 5da495a..0561c42 100644
--- a/docs/build/html/topics/impala_functions_overview.html
+++ b/docs/build/html/topics/impala_functions_overview.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Overview of Impala Functions" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_schema_objects.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="functions" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_grant.html b/docs/build/html/topics/impala_grant.html
index 42858b8..e8ce8de 100644
--- a/docs/build/html/topics/impala_grant.html
+++ b/docs/build/html/topics/impala_grant.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="GRANT Statement (Impala 2.0 or higher only)" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="grant" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -125,6 +125,9 @@ GRANT <var class="keyword varname">privilege</var> ON <var class="keyword varnam
         SQL statements in <span class="keyword">Impala 3.0</span> and higher. The following notations
         are used:
         <ul class="ul">
+          <li class="li">The <strong class="ph b">SERVER</strong> resource type in Ranger implies all databases,
+            all tables, all columns, all UDFs, and all URIs.</li>
+
           <li class="li">
             <strong class="ph b">ANY</strong> denotes the <code class="ph codeph">SELECT</code>, <code class="ph codeph">INSERT</code>,
             <code class="ph codeph">CREATE</code>, <code class="ph codeph">ALTER</code>, <code class="ph codeph">DROP</code>,
@@ -155,7 +158,7 @@ GRANT <var class="keyword varname">privilege</var> ON <var class="keyword varnam
         </ul>
 
         
-<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="grant__d6e172" class="table" frame="border" border="1" rules="all"><colgroup><col /><col /><col /></colgroup><tbody class="tbody">
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="grant__d6e178" class="table" frame="border" border="1" rules="all"><colgroup><col /><col /><col /></colgroup><tbody class="tbody">
               <tr class="row">
                 <td class="entry cellrowborder" style="vertical-align:top;">
                   <strong class="ph b">SQL Statement</strong>
diff --git a/docs/build/html/topics/impala_group_by.html b/docs/build/html/topics/impala_group_by.html
index 21de595..1f32be2 100644
--- a/docs/build/html/topics/impala_group_by.html
+++ b/docs/build/html/topics/impala_group_by.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="GROUP BY Clause" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_select.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="group_by" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_group_concat.html b/docs/build/html/topics/impala_group_concat.html
index 3fad723..0b489a8 100644
--- a/docs/build/html/topics/impala_group_concat.html
+++ b/docs/build/html/topics/impala_group_concat.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="GROUP_CONCAT 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="group_concat" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_hadoop.html b/docs/build/html/topics/impala_hadoop.html
index 3c3aa91..9126ceb 100644
--- a/docs/build/html/topics/impala_hadoop.html
+++ b/docs/build/html/topics/impala_hadoop.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="How Impala Fits Into the Hadoop Ecosystem" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_concepts.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="intro_hadoop" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_having.html b/docs/build/html/topics/impala_having.html
index 093c2e4..7aed911 100644
--- a/docs/build/html/topics/impala_having.html
+++ b/docs/build/html/topics/impala_having.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="HAVING Clause" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_select.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="having" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_hbase.html b/docs/build/html/topics/impala_hbase.html
index 559100d..ee2e04f 100644
--- a/docs/build/html/topics/impala_hbase.html
+++ b/docs/build/html/topics/impala_hbase.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Using Impala to Query HBase Tables" />
 <meta name="prodname" content="Impala" />
@@ -18,16 +18,16 @@
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="impala_hbase" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -128,12 +128,12 @@
         </li>
 
 
-        <li class="li">
-          You issue queries against the Impala tables. For efficient queries, use <code class="ph codeph">WHERE</code> clauses to
-          find a single key value or a range of key values wherever practical, by testing the Impala column
-          corresponding to the HBase row key. Avoid queries that do full-table scans, which are efficient for
-          regular Impala tables but inefficient in HBase.
-        </li>
+        <li class="li"> You issue queries against the Impala tables. For efficient queries,
+          use the <code class="ph codeph">WHERE</code> clause to find a single key value or a
+          range of key values wherever practical, by testing the Impala column
+          corresponding to the HBase row key. Avoid queries that do full-table
+          scans, which are efficient for regular Impala tables but inefficient
+          in HBase. </li>
 
       </ul>
 
@@ -207,15 +207,16 @@
       </p>
 
 
-      <p class="p">
-        For best performance of Impala queries against HBase tables, most queries will perform comparisons in the
-        <code class="ph codeph">WHERE</code> against the column that corresponds to the HBase row key. When creating the table
-        through the Hive shell, use the <code class="ph codeph">STRING</code> data type for the column that corresponds to the
-        HBase row key. Impala can translate conditional tests (through operators such as <code class="ph codeph">=</code>,
-        <code class="ph codeph">&lt;</code>, <code class="ph codeph">BETWEEN</code>, and <code class="ph codeph">IN</code>) against this column into fast
-        lookups in HBase, but this optimization (<span class="q">"predicate pushdown"</span>) only works when that column is
-        defined as <code class="ph codeph">STRING</code>.
-      </p>
+      <p class="p"> For best performance of Impala queries against HBase tables, most
+        queries will perform comparisons in the <code class="ph codeph">WHERE</code> clause
+        against the column that corresponds to the HBase row key. When creating
+        the table through the Hive shell, use the <code class="ph codeph">STRING</code> data
+        type for the column that corresponds to the HBase row key. Impala can
+        translate predicates (through operators such as <code class="ph codeph">=</code>,
+          <code class="ph codeph">&lt;</code>, and <code class="ph codeph">BETWEEN</code>) against this
+        column into fast lookups in HBase, but this optimization (<span class="q">"predicate
+          pushdown"</span>) only works when that column is defined as
+          <code class="ph codeph">STRING</code>. </p>
 
 
       <p class="p">
diff --git a/docs/build/html/topics/impala_hbase_cache_blocks.html b/docs/build/html/topics/impala_hbase_cache_blocks.html
index 8f18598..47d52aa 100644
--- a/docs/build/html/topics/impala_hbase_cache_blocks.html
+++ b/docs/build/html/topics/impala_hbase_cache_blocks.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="HBASE_CACHE_BLOCKS 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="hbase_cache_blocks" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_hbase_caching.html b/docs/build/html/topics/impala_hbase_caching.html
index f358dd7..940d531 100644
--- a/docs/build/html/topics/impala_hbase_caching.html
+++ b/docs/build/html/topics/impala_hbase_caching.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="HBASE_CACHING 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="hbase_caching" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_hints.html b/docs/build/html/topics/impala_hints.html
index 4356094..4408b9f 100644
--- a/docs/build/html/topics/impala_hints.html
+++ b/docs/build/html/topics/impala_hints.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Optimizer Hints" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="hints" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_hudi.html b/docs/build/html/topics/impala_hudi.html
new file mode 100644
index 0000000..076324e
--- /dev/null
+++ b/docs/build/html/topics/impala_hudi.html
@@ -0,0 +1,93 @@
+<?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 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
+<meta name="DC.Type" content="concept" />
+<meta name="DC.Title" content="Using the Hudi File Format" />
+<meta name="DC.Relation" scheme="URI" content="../topics/impala_file_formats.html" />
+<meta name="prodname" content="Impala" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="DC.Format" content="XHTML" />
+<meta name="DC.Identifier" content="hudi" />
+<link rel="stylesheet" type="text/css" href="../commonltr.css" />
+<title>Using the Hudi File Format</title>
+</head>
+<body id="hudi">
+
+  
+  <h1 class="title topictitle1" id="ariaid-title1">Using the Hudi File Format</h1>
+
+  
+  
+  
+  <div class="body conbody">
+    
+    <p class="p">
+       Impala supports Read Optimized
+      Queries on Hudi tables as an experimental feature. Read Optimized Queries treat the latest
+      table snapshot as the commit or compaction action, expose only base/columnar files in latest
+      file slices, and guarantee the same columnar query performance as a non-Hudi columnar
+      table.</p>
+
+    <p class="p"></p>
+
+    
+    
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" class="table" frame="border" border="1" rules="all"><caption><span class="tablecap"><span class="table--title-label">Table 1. </span>Hudi Format Support in Impala</span></caption><colgroup><col style="width:10%" /><col style="width:10%" /><col style="width:20%" /><col style="width:30%" /><col style="width:30%" /></colgroup><thead class="thead" style="text-align:left;">
+          <tr class="row">
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d98160e72">
+              File Type
+            </th>
+
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d98160e75">
+              Format
+            </th>
+
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d98160e78">
+              Compression Codecs
+            </th>
+
+            <th class="entry nocellnorowborder" style="vertical-align:top;" id="d98160e81">
+              Impala Can CREATE?
+            </th>
+
+            <th class="entry cell-norowborder" style="vertical-align:top;" id="d98160e84">
+              Impala Can INSERT?
+            </th>
+
+          </tr>
+
+        </thead>
+<tbody class="tbody">
+          <tr class="row">
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d98160e72 ">
+              <a class="xref" href="impala_hudi.html#hudi">Hudi</a>
+            </td>
+
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d98160e75 ">Structured</td>
+
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d98160e78 ">Snappy, gzip, zstd, lz4; currently Snappy by default </td>
+
+            <td class="entry row-nocellborder" style="vertical-align:top;" headers="d98160e81 ">Yes, support for Read Optimized Queries is experimental.</td>
+
+            <td class="entry cellrowborder" style="vertical-align:top;" headers="d98160e84 ">No. Create an external table in Impala. Set the table location to the Hudi table
+              directory. Alternatively, create the Hudi table in Hive. </td>
+
+          </tr>
+
+        </tbody>
+</table>
+</div>
+
+  </div>
+
+<div class="related-links">
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_file_formats.html">How Impala Works with Hadoop File Formats</a></div>
+</div>
+</div></body>
+</html>
\ No newline at end of file
diff --git a/docs/build/html/topics/impala_identifiers.html b/docs/build/html/topics/impala_identifiers.html
index 0d341c1..2438dea 100644
--- a/docs/build/html/topics/impala_identifiers.html
+++ b/docs/build/html/topics/impala_identifiers.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Overview of Impala Identifiers" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_schema_objects.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="identifiers" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_idle_session_timeout.html b/docs/build/html/topics/impala_idle_session_timeout.html
index 98b1bd2..506c972 100644
--- a/docs/build/html/topics/impala_idle_session_timeout.html
+++ b/docs/build/html/topics/impala_idle_session_timeout.html
@@ -4,13 +4,13 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="IDLE_SESSION_TIMEOUT Query Option (Impala 2.12 or higher only)" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_query_options.html" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="idle_session_timeout" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_impala_shell.html b/docs/build/html/topics/impala_impala_shell.html
index d4ac6f1..54cd19b 100644
--- a/docs/build/html/topics/impala_impala_shell.html
+++ b/docs/build/html/topics/impala_impala_shell.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Using the Impala Shell (impala-shell Command)" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_client.html" />
@@ -15,8 +15,8 @@
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_shell_commands.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="impala_shell" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_incompatible_changes.html b/docs/build/html/topics/impala_incompatible_changes.html
index 0e407a8..a4332be 100644
--- a/docs/build/html/topics/impala_incompatible_changes.html
+++ b/docs/build/html/topics/impala_incompatible_changes.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Incompatible Changes and Limitations in Apache Impala" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_release_notes.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="incompatible_changes" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -46,8 +46,34 @@
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_release_notes.html">Impala Release Notes</a></div>
 </div>
-</div><div class="topic concept nested1" aria-labelledby="ariaid-title2" id="incompatible_changes_330x">
-    <h2 class="title topictitle2" id="ariaid-title2">Incompatible Changes Introduced in Impala 3.3.x</h2>
+</div><div class="topic concept nested1" aria-labelledby="ariaid-title2" id="incompatible_changes_340x">
+    <h2 class="title topictitle2" id="ariaid-title2">Incompatible Changes Introduced in Impala 3.4.x</h2>
+
+    <div class="body conbody">
+      <div class="p"> For the full list of issues closed in this release, including any that
+        introduce behavior changes or incompatibilities, see the <a class="xref" href="https://impala.apache.org/docs/changelog-3.4.html" target="_blank">changelog for <span class="keyword">Impala 3.4</span></a>. <ul class="ul">
+          <li class="li">To optimize query performance, Impala planner uses the value of
+            the <code class="ph codeph">fs.s3a.block.size</code> startup flag when calculating
+            the split size on non-block based stores, e.g. S3, ADLS, etc.
+            Starting in this release, Impala planner uses the
+              <code class="ph codeph">PARQUET_OBJECT_STORE_SPLIT_SIZE</code> query option to
+            get the Parquet file format specific split size.<p class="p">For Parquet
+              files, the <code class="ph codeph">fs.s3a.block.size</code> startup flag is no
+              longer used.</p>
+<p class="p">The default value of the
+                <code class="ph codeph">PARQUET_OBJECT_STORE_SPLIT_SIZE</code> query option is
+              256 MB.</p>
+</li>
+
+        </ul>
+</div>
+
+    </div>
+
+  </div>
+
+  <div class="topic concept nested1" aria-labelledby="ariaid-title3" id="incompatible_changes_330x">
+    <h2 class="title topictitle2" id="ariaid-title3">Incompatible Changes Introduced in Impala 3.3.x</h2>
 
     <div class="body conbody">
       <div class="p"> For the full list of issues closed in this release, including any that
@@ -67,8 +93,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title3" id="incompatible_changes_320x">
-    <h2 class="title topictitle2" id="ariaid-title3">Incompatible Changes Introduced in Impala 3.2.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title4" id="incompatible_changes_320x">
+    <h2 class="title topictitle2" id="ariaid-title4">Incompatible Changes Introduced in Impala 3.2.x</h2>
 
     <div class="body conbody">
       <p class="p"> For the full list of issues closed in this release, including any that
@@ -88,8 +114,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title4" id="incompatible_changes_310x">
-    <h2 class="title topictitle2" id="ariaid-title4">Incompatible Changes Introduced in Impala 3.1.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title5" id="incompatible_changes_310x">
+    <h2 class="title topictitle2" id="ariaid-title5">Incompatible Changes Introduced in Impala 3.1.x</h2>
 
     <div class="body conbody">
       <p class="p"> For the full list of issues closed in this release, including any that
@@ -99,8 +125,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title5" id="incompatible_changes_300x">
-    <h2 class="title topictitle2" id="ariaid-title5">Incompatible Changes Introduced in Impala 3.0.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title6" id="incompatible_changes_300x">
+    <h2 class="title topictitle2" id="ariaid-title6">Incompatible Changes Introduced in Impala 3.0.x</h2>
 
     <div class="body conbody">
       <p class="p"> For the full list of issues closed in this release, including any that
@@ -110,8 +136,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title6" id="incompatible_changes_212x">
-    <h2 class="title topictitle2" id="ariaid-title6">Incompatible Changes Introduced in Impala 2.12.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title7" id="incompatible_changes_212x">
+    <h2 class="title topictitle2" id="ariaid-title7">Incompatible Changes Introduced in Impala 2.12.x</h2>
 
     <div class="body conbody">
       <p class="p"> For the full list of issues closed in this release, including any that
@@ -121,8 +147,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title7" id="incompatible_changes_211x">
-    <h2 class="title topictitle2" id="ariaid-title7">Incompatible Changes Introduced in Impala 2.11.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title8" id="incompatible_changes_211x">
+    <h2 class="title topictitle2" id="ariaid-title8">Incompatible Changes Introduced in Impala 2.11.x</h2>
 
     <div class="body conbody">
       <p class="p"> For the full list of issues closed in this release, including any that
@@ -132,8 +158,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title8" id="incompatible_changes_210x">
-    <h2 class="title topictitle2" id="ariaid-title8">Incompatible Changes Introduced in Impala 2.10.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title9" id="incompatible_changes_210x">
+    <h2 class="title topictitle2" id="ariaid-title9">Incompatible Changes Introduced in Impala 2.10.x</h2>
 
     <div class="body conbody">
       <p class="p"> For the full list of issues closed in this release, including any that
@@ -143,8 +169,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title9" id="incompatible_changes_29x">
-    <h2 class="title topictitle2" id="ariaid-title9">Incompatible Changes Introduced in Impala 2.9.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title10" id="incompatible_changes_29x">
+    <h2 class="title topictitle2" id="ariaid-title10">Incompatible Changes Introduced in Impala 2.9.x</h2>
 
     <div class="body conbody">
       <p class="p"> For the full list of issues closed in this release, including any that
@@ -155,8 +181,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title10" id="incompatible_changes_28x">
-    <h2 class="title topictitle2" id="ariaid-title10">Incompatible Changes Introduced in Impala 2.8.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title11" id="incompatible_changes_28x">
+    <h2 class="title topictitle2" id="ariaid-title11">Incompatible Changes Introduced in Impala 2.8.x</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -263,8 +289,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title11" id="incompatible_changes_27x">
-    <h2 class="title topictitle2" id="ariaid-title11">Incompatible Changes Introduced in Impala 2.7.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title12" id="incompatible_changes_27x">
+    <h2 class="title topictitle2" id="ariaid-title12">Incompatible Changes Introduced in Impala 2.7.x</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -293,8 +319,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title12" id="incompatible_changes_26x">
-    <h2 class="title topictitle2" id="ariaid-title12">Incompatible Changes Introduced in Impala 2.6.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title13" id="incompatible_changes_26x">
+    <h2 class="title topictitle2" id="ariaid-title13">Incompatible Changes Introduced in Impala 2.6.x</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -464,8 +490,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title13" id="incompatible_changes_25x">
-    <h2 class="title topictitle2" id="ariaid-title13">Incompatible Changes Introduced in Impala 2.5.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title14" id="incompatible_changes_25x">
+    <h2 class="title topictitle2" id="ariaid-title14">Incompatible Changes Introduced in Impala 2.5.x</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -555,8 +581,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title14" id="incompatible_changes_24x">
-    <h2 class="title topictitle2" id="ariaid-title14">Incompatible Changes Introduced in Impala 2.4.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title15" id="incompatible_changes_24x">
+    <h2 class="title topictitle2" id="ariaid-title15">Incompatible Changes Introduced in Impala 2.4.x</h2>
 
     <div class="body conbody">
       <p class="p"> Other than support for DSSD storage, the Impala feature set for
@@ -569,8 +595,8 @@
 
   
   
-  <div class="topic concept nested1" aria-labelledby="ariaid-title15" id="incompatible_changes_23x">
-    <h2 class="title topictitle2" id="ariaid-title15">Incompatible Changes Introduced in Impala 2.3.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title16" id="incompatible_changes_23x">
+    <h2 class="title topictitle2" id="ariaid-title16">Incompatible Changes Introduced in Impala 2.3.x</h2>
 
     <div class="body conbody">
       <div class="note note"><span class="notetitle">Note:</span> 
@@ -648,8 +674,8 @@
   </div>
 
   
-  <div class="topic concept nested1" aria-labelledby="ariaid-title16" id="incompatible_changes_22x">
-    <h2 class="title topictitle2" id="ariaid-title16">Incompatible Changes Introduced in Impala 2.2.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title17" id="incompatible_changes_22x">
+    <h2 class="title topictitle2" id="ariaid-title17">Incompatible Changes Introduced in Impala 2.2.x</h2>
 
     <div class="body conbody">
       <div class="section" id="incompatible_changes_22x__files_220"><h3 class="title sectiontitle"> Changes to File Handling </h3>
@@ -689,8 +715,8 @@
   </div>
 
   
-  <div class="topic concept nested1" aria-labelledby="ariaid-title17" id="incompatible_changes_21x">
-    <h2 class="title topictitle2" id="ariaid-title17">Incompatible Changes Introduced in Impala 2.1.x</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title18" id="incompatible_changes_21x">
+    <h2 class="title topictitle2" id="ariaid-title18">Incompatible Changes Introduced in Impala 2.1.x</h2>
 
     <div class="body conbody">
       <div class="section" id="incompatible_changes_21x__prereqs_210"><h3 class="title sectiontitle"> Changes to Prerequisites </h3>
@@ -728,8 +754,8 @@
   </div>
 
   
-  <div class="topic concept nested1" aria-labelledby="ariaid-title18" id="incompatible_changes_205">
-    <h2 class="title topictitle2" id="ariaid-title18">Incompatible Changes Introduced in Impala 2.0.5</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title19" id="incompatible_changes_205">
+    <h2 class="title topictitle2" id="ariaid-title19">Incompatible Changes Introduced in Impala 2.0.5</h2>
 
     <div class="body conbody">
       <p class="p"> No incompatible changes. </p>
@@ -738,8 +764,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title19" id="incompatible_changes_204">
-    <h2 class="title topictitle2" id="ariaid-title19">Incompatible Changes Introduced in Impala 2.0.4</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title20" id="incompatible_changes_204">
+    <h2 class="title topictitle2" id="ariaid-title20">Incompatible Changes Introduced in Impala 2.0.4</h2>
 
     <div class="body conbody">
       <p class="p"> No incompatible changes. </p>
@@ -748,15 +774,15 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title20" id="incompatible_changes_203">
-    <h2 class="title topictitle2" id="ariaid-title20">Incompatible Changes Introduced in Impala 2.0.3</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title21" id="incompatible_changes_203">
+    <h2 class="title topictitle2" id="ariaid-title21">Incompatible Changes Introduced in Impala 2.0.3</h2>
 
     <div class="body conbody"> </div>
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title21" id="incompatible_changes_202">
-    <h2 class="title topictitle2" id="ariaid-title21">Incompatible Changes Introduced in Impala 2.0.2</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title22" id="incompatible_changes_202">
+    <h2 class="title topictitle2" id="ariaid-title22">Incompatible Changes Introduced in Impala 2.0.2</h2>
 
     <div class="body conbody">
       <p class="p"> No incompatible changes. </p>
@@ -765,8 +791,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title22" id="incompatible_changes_201">
-    <h2 class="title topictitle2" id="ariaid-title22">Incompatible Changes Introduced in Impala 2.0.1</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title23" id="incompatible_changes_201">
+    <h2 class="title topictitle2" id="ariaid-title23">Incompatible Changes Introduced in Impala 2.0.1</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -809,8 +835,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title23" id="incompatible_changes_200">
-    <h2 class="title topictitle2" id="ariaid-title23">Incompatible Changes Introduced in Impala 2.0.0</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title24" id="incompatible_changes_200">
+    <h2 class="title topictitle2" id="ariaid-title24">Incompatible Changes Introduced in Impala 2.0.0</h2>
 
     <div class="body conbody">
       <div class="section" id="incompatible_changes_200__prereqs_200"><h3 class="title sectiontitle"> Changes to Prerequisites </h3>
@@ -993,8 +1019,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title24" id="incompatible_changes_144">
-    <h2 class="title topictitle2" id="ariaid-title24">Incompatible Changes Introduced in Impala 1.4.4</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title25" id="incompatible_changes_144">
+    <h2 class="title topictitle2" id="ariaid-title25">Incompatible Changes Introduced in Impala 1.4.4</h2>
 
     <div class="body conbody">
       <p class="p"> No incompatible changes. </p>
@@ -1003,8 +1029,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title25" id="incompatible_changes_143">
-    <h2 class="title topictitle2" id="ariaid-title25">Incompatible Changes Introduced in Impala 1.4.3</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title26" id="incompatible_changes_143">
+    <h2 class="title topictitle2" id="ariaid-title26">Incompatible Changes Introduced in Impala 1.4.3</h2>
 
     <div class="body conbody">
       <p class="p"> No incompatible changes. The TLS/SSL security fix does not require any
@@ -1014,8 +1040,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title26" id="incompatible_changes_142">
-    <h2 class="title topictitle2" id="ariaid-title26">Incompatible Changes Introduced in Impala 1.4.2</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title27" id="incompatible_changes_142">
+    <h2 class="title topictitle2" id="ariaid-title27">Incompatible Changes Introduced in Impala 1.4.2</h2>
 
     <div class="body conbody">
       <p class="p"> None. Impala 1.4.2 is purely a bug-fix release. It does not include
@@ -1025,8 +1051,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title27" id="incompatible_changes_141">
-    <h2 class="title topictitle2" id="ariaid-title27">Incompatible Changes Introduced in Impala 1.4.1</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title28" id="incompatible_changes_141">
+    <h2 class="title topictitle2" id="ariaid-title28">Incompatible Changes Introduced in Impala 1.4.1</h2>
 
     <div class="body conbody">
       <p class="p"> None. Impala 1.4.1 is purely a bug-fix release. It does not include
@@ -1036,8 +1062,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title28" id="incompatible_changes_140">
-    <h2 class="title topictitle2" id="ariaid-title28">Incompatible Changes Introduced in Impala 1.4.0</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title29" id="incompatible_changes_140">
+    <h2 class="title topictitle2" id="ariaid-title29">Incompatible Changes Introduced in Impala 1.4.0</h2>
 
     
     <div class="body conbody">
@@ -1142,8 +1168,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title29" id="incompatible_changes_133">
-    <h2 class="title topictitle2" id="ariaid-title29">Incompatible Changes Introduced in Impala 1.3.3</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title30" id="incompatible_changes_133">
+    <h2 class="title topictitle2" id="ariaid-title30">Incompatible Changes Introduced in Impala 1.3.3</h2>
 
     <div class="body conbody">
       <p class="p"> No incompatible changes. The TLS/SSL security fix does not require any
@@ -1153,8 +1179,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title30" id="incompatible_changes_132">
-    <h2 class="title topictitle2" id="ariaid-title30">Incompatible Changes Introduced in Impala 1.3.2</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title31" id="incompatible_changes_132">
+    <h2 class="title topictitle2" id="ariaid-title31">Incompatible Changes Introduced in Impala 1.3.2</h2>
 
     <div class="body conbody">
       <p class="p"> With the fix for IMPALA-1019, you can use HDFS caching for files that
@@ -1164,8 +1190,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title31" id="incompatible_changes_131">
-    <h2 class="title topictitle2" id="ariaid-title31">Incompatible Changes Introduced in Impala 1.3.1</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title32" id="incompatible_changes_131">
+    <h2 class="title topictitle2" id="ariaid-title32">Incompatible Changes Introduced in Impala 1.3.1</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -1199,8 +1225,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title32" id="incompatible_changes_130">
-    <h2 class="title topictitle2" id="ariaid-title32">Incompatible Changes Introduced in Impala 1.3.0</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title33" id="incompatible_changes_130">
+    <h2 class="title topictitle2" id="ariaid-title33">Incompatible Changes Introduced in Impala 1.3.0</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -1298,8 +1324,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title33" id="incompatible_changes_124">
-    <h2 class="title topictitle2" id="ariaid-title33">Incompatible Changes Introduced in Impala 1.2.4</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title34" id="incompatible_changes_124">
+    <h2 class="title topictitle2" id="ariaid-title34">Incompatible Changes Introduced in Impala 1.2.4</h2>
 
     <div class="body conbody">
       <p class="p"> There are no incompatible changes introduced in Impala 1.2.4. </p>
@@ -1320,8 +1346,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title34" id="incompatible_changes_123">
-    <h2 class="title topictitle2" id="ariaid-title34">Incompatible Changes Introduced in Impala 1.2.3</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title35" id="incompatible_changes_123">
+    <h2 class="title topictitle2" id="ariaid-title35">Incompatible Changes Introduced in Impala 1.2.3</h2>
 
     <div class="body conbody">
       <p class="p"> Because the feature set of Impala 1.2.3 is identical to Impala 1.2.2,
@@ -1332,8 +1358,8 @@
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title35" id="incompatible_changes_122">
-    <h2 class="title topictitle2" id="ariaid-title35">Incompatible Changes Introduced in Impala 1.2.2</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title36" id="incompatible_changes_122">
+    <h2 class="title topictitle2" id="ariaid-title36">Incompatible Changes Introduced in Impala 1.2.2</h2>
 
     <div class="body conbody">
       <p class="p"> The following changes to SQL syntax and semantics in Impala 1.2.2
@@ -1399,8 +1425,8 @@ select * from `cross`;</code></pre>
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title36" id="incompatible_changes_121">
-    <h2 class="title topictitle2" id="ariaid-title36">Incompatible Changes Introduced in Impala 1.2.1</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title37" id="incompatible_changes_121">
+    <h2 class="title topictitle2" id="ariaid-title37">Incompatible Changes Introduced in Impala 1.2.1</h2>
 
     <div class="body conbody">
       <p class="p"> The following changes to SQL syntax and semantics in Impala 1.2.1
@@ -1476,8 +1502,8 @@ select * from `cross`;</code></pre>
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title37" id="incompatible_changes_120">
-    <h2 class="title topictitle2" id="ariaid-title37">Incompatible Changes Introduced in Impala 1.2.0 (Beta)</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title38" id="incompatible_changes_120">
+    <h2 class="title topictitle2" id="ariaid-title38">Incompatible Changes Introduced in Impala 1.2.0 (Beta)</h2>
 
     <div class="body conbody">
       <p class="p"> There are no incompatible changes to SQL syntax in Impala 1.2.0
@@ -1535,8 +1561,8 @@ select * from `cross`;</code></pre>
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title38" id="incompatible_changes_111">
-    <h2 class="title topictitle2" id="ariaid-title38">Incompatible Changes Introduced in Impala 1.1.1</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title39" id="incompatible_changes_111">
+    <h2 class="title topictitle2" id="ariaid-title39">Incompatible Changes Introduced in Impala 1.1.1</h2>
 
     <div class="body conbody">
       <p class="p"> There are no incompatible changes in Impala 1.1.1. </p>
@@ -1572,8 +1598,8 @@ ALTER TABLE <var class="keyword varname">table_name</var> SET FILEFORMAT
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title39" id="incompatible_changes_11">
-    <h2 class="title topictitle2" id="ariaid-title39">Incompatible Change Introduced in Impala 1.1</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title40" id="incompatible_changes_11">
+    <h2 class="title topictitle2" id="ariaid-title40">Incompatible Change Introduced in Impala 1.1</h2>
 
     <div class="body conbody">
       <ul class="ul">
@@ -1602,8 +1628,8 @@ ALTER TABLE <var class="keyword varname">table_name</var> SET FILEFORMAT
 
   </div>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title40" id="incompatible_changes_10">
-    <h2 class="title topictitle2" id="ariaid-title40">Incompatible Changes Introduced in Impala 1.0</h2>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title41" id="incompatible_changes_10">
+    <h2 class="title topictitle2" id="ariaid-title41">Incompatible Changes Introduced in Impala 1.0</h2>
 
     <div class="body conbody">
       <ul class="ul">
diff --git a/docs/build/html/topics/impala_insert.html b/docs/build/html/topics/impala_insert.html
index f8b4b56..1cc6fe9 100644
--- a/docs/build/html/topics/impala_insert.html
+++ b/docs/build/html/topics/impala_insert.html
@@ -4,17 +4,17 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="INSERT 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="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="insert" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -613,35 +613,6 @@ Inserted 2 rows in 0.16s
       </p>
 
 
-
-
-      <p class="p">
-        To use a <code class="ph codeph">VALUES</code> clause like a table in other statements, wrap it in parentheses and use
-        <code class="ph codeph">AS</code> clauses to specify aliases for the entire object and any columns you need to refer to:
-      </p>
-
-
-<pre class="pre codeblock"><code>[localhost:21000] &gt; select * from (values(4,5,6),(7,8,9)) as t;
-+---+---+---+
-| 4 | 5 | 6 |
-+---+---+---+
-| 4 | 5 | 6 |
-| 7 | 8 | 9 |
-+---+---+---+
-[localhost:21000] &gt; select * from (values(1 as c1, true as c2, 'abc' as c3),(100,false,'xyz')) as t;
-+-----+-------+-----+
-| c1  | c2    | c3  |
-+-----+-------+-----+
-| 1   | true  | abc |
-| 100 | false | xyz |
-+-----+-------+-----+</code></pre>
-
-      <p class="p">
-        For example, you might use a tiny table constructed like this from constant literals or function return
-        values as part of a longer statement involving joins or <code class="ph codeph">UNION ALL</code>.
-      </p>
-
-
       <p class="p">
         <strong class="ph b">HDFS considerations:</strong>
       </p>
@@ -762,38 +733,38 @@ Inserted 2 rows in 0.16s
         <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 Amazon
-        Simple Storage Service (S3). The syntax of the DML statements is the same as for any
-        other tables, because the S3 location for tables and partitions is specified by an
-        <code class="ph codeph">s3a://</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 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 <code class="ph codeph">LOAD
-        DATA</code> statement and the final stage of the <code class="ph codeph">INSERT</code> and
-        <code class="ph codeph">CREATE TABLE AS SELECT</code> statements involve moving files from one
-        directory to another. (In the case of <code class="ph codeph">INSERT</code> and <code class="ph codeph">CREATE TABLE
-        AS SELECT</code>, the files are moved from a temporary staging directory to the final
-        destination directory.) Because S3 does not support a <span class="q">"rename"</span> operation for
-        existing objects, in these cases Impala actually copies the data files from one location
-        to another and then removes the original files. In <span class="keyword">Impala 2.6</span>,
-        the <code class="ph codeph">S3_SKIP_INSERT_STAGING</code> query option provides a way to speed up
-        <code class="ph codeph">INSERT</code> statements for S3 tables and partitions, with the tradeoff that
-        a problem during statement execution could leave data in an inconsistent state. 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"> 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 S3. The syntax of the DML statements is the same as for any other
+        tables, because the S3 location for tables and partitions is specified
+        by an <code class="ph codeph">s3a://</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 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 <code class="ph codeph">LOAD
+          DATA</code> statement and the final stage of the
+          <code class="ph codeph">INSERT</code> and <code class="ph codeph">CREATE TABLE AS SELECT</code>
+        statements involve moving files from one directory to another. (In the
+        case of <code class="ph codeph">INSERT</code> and <code class="ph codeph">CREATE TABLE AS
+          SELECT</code>, the files are moved from a temporary staging
+        directory to the final destination directory.) Because S3 does not
+        support a <span class="q">"rename"</span> operation for existing objects, in these cases
+        Impala actually copies the data files from one location to another and
+        then removes the original files. In <span class="keyword">Impala 2.6</span>,
+        the <code class="ph codeph">S3_SKIP_INSERT_STAGING</code> query option provides a way
+        to speed up <code class="ph codeph">INSERT</code> statements for S3 tables and
+        partitions, with the tradeoff that a problem during statement execution
+        could leave data in an inconsistent state. 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</a> for details. </p>
+
+      <p class="p">See <a class="xref" href="impala_s3.html#s3">Using Impala with Amazon S3 Object Store</a> for details about reading and writing S3 data with Impala.</p>
 
 
       <p class="p">
diff --git a/docs/build/html/topics/impala_install.html b/docs/build/html/topics/impala_install.html
index 12efc73..c8ccbb7 100644
--- a/docs/build/html/topics/impala_install.html
+++ b/docs/build/html/topics/impala_install.html
@@ -4,14 +4,14 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Installing Impala" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="install" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_int.html b/docs/build/html/topics/impala_int.html
index 439dc75..4e7ed83 100644
--- a/docs/build/html/topics/impala_int.html
+++ b/docs/build/html/topics/impala_int.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="INT Data Type" />
 <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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="int" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_intro.html b/docs/build/html/topics/impala_intro.html
index bddb10a..9da2a3b 100644
--- a/docs/build/html/topics/impala_intro.html
+++ b/docs/build/html/topics/impala_intro.html
@@ -4,12 +4,12 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Introducing Apache Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="intro" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_invalidate_metadata.html b/docs/build/html/topics/impala_invalidate_metadata.html
index 7b4c592..fd282af 100644
--- a/docs/build/html/topics/impala_invalidate_metadata.html
+++ b/docs/build/html/topics/impala_invalidate_metadata.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="INVALIDATE METADATA 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.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="invalidate_metadata" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_isilon.html b/docs/build/html/topics/impala_isilon.html
index 8eedb46..21befbf 100644
--- a/docs/build/html/topics/impala_isilon.html
+++ b/docs/build/html/topics/impala_isilon.html
@@ -4,14 +4,14 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Using Impala with Isilon Storage" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="impala_isilon" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_jdbc.html b/docs/build/html/topics/impala_jdbc.html
index 8a41580..eac6a3a 100644
--- a/docs/build/html/topics/impala_jdbc.html
+++ b/docs/build/html/topics/impala_jdbc.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Configuring Impala to Work with JDBC" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_client.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="impala_jdbc" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -20,210 +20,137 @@
 </head>
 <body id="impala_jdbc">
 
-
   <h1 class="title topictitle1" id="impala_jdbc__jdbc">Configuring Impala to Work with JDBC</h1>
 
-
   
-
   <div class="body conbody">
+    <p class="p"> Impala supports the standard JDBC interface, allowing access from
+      commercial Business Intelligence tools and custom software written in Java
+      or other programming languages. The JDBC driver allows you to access
+      Impala from a Java program that you write, or a Business Intelligence or
+      similar tool that uses JDBC to communicate with various database products. </p>
 
-    <p class="p">
-      
-      Impala supports the standard JDBC interface, allowing access from commercial Business
-      Intelligence tools and custom software written in Java or other programming languages. The
-      JDBC driver allows you to access Impala from a Java program that you write, or a Business
-      Intelligence or similar tool that uses JDBC to communicate with various database products.
-    </p>
-
-
-    <p class="p">
-      Setting up a JDBC connection to Impala involves the following steps:
-    </p>
-
+    <p class="p"> Setting up a JDBC connection to Impala involves the following steps: </p>
 
     <ul class="ul">
-      <li class="li">
-        Verifying the communication port where the Impala daemons in your cluster are listening
-        for incoming JDBC requests.
-      </li>
-
+      <li class="li"> Verifying the communication port where the Impala daemons in your
+        cluster are listening for incoming JDBC requests. </li>
 
-      <li class="li">
-        Installing the JDBC driver on every system that runs the JDBC-enabled application.
-      </li>
+      <li class="li"> Installing the JDBC driver on every system that runs the JDBC-enabled
+        application. </li>
 
-
-      <li class="li">
-        Specifying a connection string for the JDBC application to access one of the servers
-        running the <span class="keyword cmdname">impalad</span> daemon, with the appropriate security settings.
-      </li>
+      <li class="li"> Specifying a connection string for the JDBC application to access one
+        of the servers running the <span class="keyword cmdname">impalad</span> daemon, with the
+        appropriate security settings. </li>
 
     </ul>
 
-
     <p class="p toc inpage"></p>
 
-
   </div>
 
-
   <div class="related-links">
 <div class="familylinks">
 <div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/impala_client.html">Impala Client Access</a></div>
 </div>
 </div><div class="topic concept nested1" aria-labelledby="ariaid-title2" id="jdbc_port">
-
     <h2 class="title topictitle2" id="ariaid-title2">Configuring the JDBC Port</h2>
 
-
     <div class="body conbody">
-
-      <div class="p">
-        The following are the default ports that Impala server accepts JDBC connections through:
-        <table cellpadding="4" cellspacing="0" summary="" id="jdbc_port__simpletable_tr2_gnt_43b" border="1" class="simpletable"><col style="width:22.675736961451246%" /><col style="width:23.356009070294785%" /><col style="width:53.96825396825397%" /><thead></thead><tbody><tr class="strow">
-
+      <div class="p"> The following are the default ports that Impala server accepts JDBC
+        connections through: <table cellpadding="4" cellspacing="0" summary="" id="jdbc_port__simpletable_tr2_gnt_43b" border="1" class="simpletable"><col style="width:22.675736961451246%" /><col style="width:23.356009070294785%" /><col style="width:53.96825396825397%" /><thead></thead><tbody><tr class="strow">
             <td style="vertical-align:top;" class="stentry"><strong class="ph b">Protocol</strong>
-
             </td>
 
-
             <td style="vertical-align:top;" class="stentry"><strong class="ph b">Default Port</strong>
-
             </td>
 
-
             <td style="vertical-align:top;" class="stentry"><strong class="ph b">Flag to Specify an Alternate Port</strong>
-
             </td>
 
-
           </tr>
 <tr class="strow">
-
             <td style="vertical-align:top;" class="stentry">HTTP</td>
 
-
             <td style="vertical-align:top;" class="stentry">28000</td>
 
-
             <td style="vertical-align:top;" class="stentry"><code class="ph codeph">‑‑hs2_http_port</code>
-
             </td>
 
-
           </tr>
 <tr class="strow">
-
             <td style="vertical-align:top;" class="stentry">Binary TCP</td>
 
-
             <td style="vertical-align:top;" class="stentry">21050</td>
 
-
             <td style="vertical-align:top;" class="stentry"><code class="ph codeph">‑‑hs2_port</code>
-
             </td>
 
-
           </tr>
 </tbody></table>
 
       </div>
 
+      <p class="p"> Make sure the port for the protocol you are using is available for
+        communication with clients, for example, that it is not blocked by
+        firewall software. </p>
 
-      <p class="p">
-        Make sure the port for the protocol you are using is available for communication with
-        clients, for example, that it is not blocked by firewall software.
-      </p>
-
-
-      <p class="p">
-        If your JDBC client software connects to a different port, specify that alternative port
-        number with the flag in the above table when starting the <code class="ph codeph">impalad</code>.
-      </p>
-
+      <p class="p"> If your JDBC client software connects to a different port, specify
+        that alternative port number with the flag in the above table when
+        starting the <code class="ph codeph">impalad</code>. </p>
 
     </div>
 
-
   </div>
 
-
   <div class="topic concept nested1" aria-labelledby="ariaid-title3" id="jdbc_driver_choice">
-
     <h2 class="title topictitle2" id="ariaid-title3">Choosing the JDBC Driver</h2>
 
-
     
-
     <div class="body conbody">
+      <p class="p"> In Impala 2.0 and later, you can use the Hive 0.13 or higher JDBC
+        driver. If you are already using JDBC applications with an earlier
+        Impala release, you should update your JDBC driver, because the Hive
+        0.12 driver that was formerly the only choice is not compatible with
+        Impala 2.0 and later. </p>
 
-      <p class="p">
-        In Impala 2.0 and later, you can use the Hive 0.13 JDBC driver. If you are already using
-        JDBC applications with an earlier Impala release, you should update your JDBC driver,
-        because the Hive 0.12 driver that was formerly the only choice is not compatible with
-        Impala 2.0 and later.
-      </p>
-
-
-      <p class="p">
-        The Hive JDBC driver provides a substantial speed increase for JDBC applications with
-        Impala 2.0 and higher, for queries that return large result sets.
-      </p>
-
+      <p class="p"> The Hive JDBC driver provides a substantial speed increase for JDBC
+        applications with Impala 2.0 and higher, for queries that return large
+        result sets. </p>
 
     </div>
 
-
   </div>
 
-
   <div class="topic concept nested1" aria-labelledby="ariaid-title4" id="jdbc_setup">
-
     <h2 class="title topictitle2" id="ariaid-title4">Enabling Impala JDBC Support on Client Systems</h2>
 
-
     
-
     <div class="body conbody">
-
       <div class="section" id="jdbc_setup__install_hive_driver"><h3 class="title sectiontitle">Using the Hive JDBC Driver</h3>
-
         
-
-        <p class="p">
-          You install the Hive JDBC driver (<code class="ph codeph">hive-jdbc</code> package) through the
-          Linux package manager, on hosts within the cluster. The driver consists of several
-          Java JAR files. The same driver can be used by Impala and Hive.
-        </p>
-
-
-        <p class="p">
-          To get the JAR files, install the Hive JDBC driver on each host in the cluster that
-          will run JDBC applications.
-
-        </p>
-
-
-        <div class="note note"><span class="notetitle">Note:</span> 
-          The latest JDBC driver, corresponding to Hive 0.13, provides substantial performance
-          improvements for Impala queries that return large result sets. Impala 2.0 and later
-          are compatible with the Hive 0.13 driver. If you already have an older JDBC driver
-          installed, and are running Impala 2.0 or higher, consider upgrading to the latest Hive
-          JDBC driver for best performance with JDBC applications.
-        </div>
-
-
-        <p class="p">
-          If you are using JDBC-enabled applications on hosts outside the cluster, you cannot
-          use the the same install procedure on the hosts. Install the JDBC driver on at least
-          one cluster host using the preceding procedure. Then download the JAR files to each
-          client machine that will use JDBC with Impala:
-        </p>
-
-
-<pre class="pre codeblock"><code>commons-logging-X.X.X.jar
+        <p class="p"> You install the Hive JDBC driver (<code class="ph codeph">hive-jdbc</code>
+          package) through the Linux package manager, on hosts within the
+          cluster. The driver consists of several JAR files. The same driver can
+          be used by Impala and Hive. </p>
+
+        <p class="p"> To get the JAR files, install the Hive JDBC driver on each host in
+          the cluster that will run JDBC applications.  </p>
+
+        <div class="note note"><span class="notetitle">Note:</span>  The latest JDBC driver, corresponding to Hive 0.13, provides
+          substantial performance improvements for Impala queries that return
+          large result sets. Impala 2.0 and later are compatible with the Hive
+          0.13 driver. If you already have an older JDBC driver installed, and
+          are running Impala 2.0 or higher, consider upgrading to the latest
+          Hive JDBC driver for best performance with JDBC applications. </div>
+
+        <p class="p"> If you are using JDBC-enabled applications on hosts outside the
+          cluster, you cannot use the the same install procedure on the hosts.
+          Install the JDBC driver on at least one cluster host using the
+          preceding procedure. Then download the JAR files to each client
+          machine that will use JDBC with Impala: </p>
+
+        <pre class="pre codeblock"><code>commons-logging-X.X.X.jar
   hadoop-common.jar
   hive-common-X.XX.X.jar
   hive-jdbc-X.XX.X.jar
@@ -237,69 +164,53 @@
   slf4j-api-X.X.X.jar
   slf4j-logXjXX-X.X.X.jar
   </code></pre>
-
         <p class="p">
-          <strong class="ph b">To enable JDBC support for Impala on the system where you run the JDBC
-          application:</strong>
+          <strong class="ph b">To enable JDBC support for Impala on the system where you run the
+            JDBC application:</strong>
         </p>
 
-
         <ol class="ol">
-          <li class="li">
-            Download the JAR files listed above to each client machine.
-            <div class="note note"><span class="notetitle">Note:</span> 
-              For Maven users, see <a class="xref" href="https://github.com/onefoursix/Cloudera-Impala-JDBC-Example" target="_blank">this sample github
-              page</a> for an example of the dependencies you could add to a
-              <code class="ph codeph">pom</code> file instead of downloading the individual JARs.
-            </div>
+          <li class="li"> Download the JAR files listed above to each client machine.
+              <div class="note note"><span class="notetitle">Note:</span>  For Maven users, see <a class="xref" href="https://github.com/onefoursix/Cloudera-Impala-JDBC-Example" target="_blank">this sample github page</a> for an example of the
+              dependencies you could add to a <code class="ph codeph">pom</code> file instead
+              of downloading the individual JARs. </div>
 
           </li>
 
+          <li class="li"> Store the JAR files in a location of your choosing, ideally a
+            directory already referenced in your <code class="ph codeph">CLASSPATH</code>
+            setting. For example: <ul class="ul">
+              <li class="li"> On Linux, you might use a location such as
+                  <code class="ph codeph">/opt/jars/</code>. </li>
 
-          <li class="li">
-            Store the JAR files in a location of your choosing, ideally a directory already
-            referenced in your <code class="ph codeph">CLASSPATH</code> setting. For example:
-            <ul class="ul">
-              <li class="li">
-                On Linux, you might use a location such as <code class="ph codeph">/opt/jars/</code>.
-              </li>
-
-
-              <li class="li">
-                On Windows, you might use a subdirectory underneath <span class="ph filepath">C:\Program
-                Files</span>.
-              </li>
+              <li class="li"> On Windows, you might use a subdirectory underneath
+                  <span class="ph filepath">C:\Program Files</span>. </li>
 
             </ul>
 
           </li>
 
-
-          <li class="li">
-            To successfully load the Impala JDBC driver, client programs must be able to locate
-            the associated JAR files. This often means setting the <code class="ph codeph">CLASSPATH</code>
-            for the client process to include the JARs. Consult the documentation for your JDBC
-            client for more details on how to install new JDBC drivers, but some examples of how
-            to set <code class="ph codeph">CLASSPATH</code> variables include:
-            <ul class="ul">
-              <li class="li">
-                On Linux, if you extracted the JARs to <code class="ph codeph">/opt/jars/</code>, you might
-                issue the following command to prepend the JAR files path to an existing
-                classpath:
-<pre class="pre codeblock"><code>export CLASSPATH=/opt/jars/*.jar:$CLASSPATH</code></pre>
+          <li class="li"> To successfully load the Impala JDBC driver, client programs must
+            be able to locate the associated JAR files. This often means setting
+            the <code class="ph codeph">CLASSPATH</code> for the client process to include the
+            JARs. Consult the documentation for your JDBC client for more
+            details on how to install new JDBC drivers, but some examples of how
+            to set <code class="ph codeph">CLASSPATH</code> variables include: <ul class="ul">
+              <li class="li"> On Linux, if you extracted the JARs to
+                  <code class="ph codeph">/opt/jars/</code>, you might issue the following
+                command to prepend the JAR files path to an existing classpath:
+                <pre class="pre codeblock"><code>export CLASSPATH=/opt/jars/*.jar:$CLASSPATH</code></pre>
               </li>
 
-
-              <li class="li">
-                On Windows, use the <strong class="ph b">System Properties</strong> control panel item to modify the
-                <strong class="ph b">Environment Variables</strong> for your system. Modify the environment variables
-                to include the path to which you extracted the files.
-                <div class="note note"><span class="notetitle">Note:</span> 
-                  If the existing <code class="ph codeph">CLASSPATH</code> on your client machine refers to
-                  some older version of the Hive JARs, ensure that the new JARs are the first
-                  ones listed. Either put the new JAR files earlier in the listings, or delete
-                  the other references to Hive JAR files.
-                </div>
+              <li class="li"> On Windows, use the <strong class="ph b">System Properties</strong> control panel
+                item to modify the <strong class="ph b">Environment Variables</strong> for your system.
+                Modify the environment variables to include the path to which
+                you extracted the files. <div class="note note"><span class="notetitle">Note:</span>  If the existing
+                    <code class="ph codeph">CLASSPATH</code> on your client machine refers to
+                  some older version of the Hive JARs, ensure that the new JARs
+                  are the first ones listed. Either put the new JAR files
+                  earlier in the listings, or delete the other references to
+                  Hive JAR files. </div>
 
               </li>
 
@@ -309,27 +220,17 @@
 
         </ol>
 
-
       </div>
 
-
     </div>
 
-
   </div>
 
-
   <div class="topic concept nested1" aria-labelledby="ariaid-title5" id="jdbc_connect">
-
     <h2 class="title topictitle2" id="ariaid-title5">Establishing JDBC Connections</h2>
 
-
     <div class="body conbody">
-
-      <p class="p">
-        The JDBC driver class depends on which driver you select.
-      </p>
-
+      <p class="p"> The JDBC driver class depends on which driver you select. </p>
 
       <div class="note note"><span class="notetitle">Note:</span> 
         If your JDBC or ODBC application connects to Impala through a load balancer such as
@@ -340,53 +241,37 @@
         closed.
       </div>
 
-
       <div class="section" id="jdbc_connect__class_hive_driver"><h3 class="title sectiontitle">Using the Hive JDBC Driver</h3>
-
         
-
-        <p class="p">
-          For example, with the Hive JDBC driver, the class name is
-          <code class="ph codeph">org.apache.hive.jdbc.HiveDriver</code>. Once you have configured Impala to
-          work with JDBC, you can establish connections between the two. To do so for a cluster
-          that does not use Kerberos authentication, use a connection string of the form
-          <code class="ph codeph">jdbc:hive2://<var class="keyword varname">host</var>:<var class="keyword varname">port</var>/;auth=noSasl</code>.
-
-          For example, you might use:
-        </p>
-
-
-<pre class="pre codeblock"><code>jdbc:hive2://myhost.example.com:21050/;auth=noSasl</code></pre>
-
-        <p class="p">
-          To connect to an instance of Impala that requires Kerberos authentication, use a
-          connection string of the form
-          <code class="ph codeph">jdbc:hive2://<var class="keyword varname">host</var>:<var class="keyword varname">port</var>/;principal=<var class="keyword varname">principal_name</var></code>.
-          The principal must be the same user principal you used when starting Impala. For
-          example, you might use:
-        </p>
-
-
-<pre class="pre codeblock"><code>jdbc:hive2://myhost.example.com:21050/;principal=impala/myhost.example.com@H2.EXAMPLE.COM</code></pre>
-
-        <p class="p">
-          To connect to an instance of Impala that requires LDAP authentication, use a
-          connection string of the form
-          <code class="ph codeph">jdbc:hive2://<var class="keyword varname">host</var>:<var class="keyword varname">port</var>/<var class="keyword varname">db_name</var>;user=<var class="keyword varname">ldap_userid</var>;password=<var class="keyword varname">ldap_password</var></code>.
-          For example, you might use:
-        </p>
-
-
-<pre class="pre codeblock"><code>jdbc:hive2://myhost.example.com:21050/test_db;user=fred;password=xyz123</code></pre>
-
-        <div class="p">
-          To connect to an instance of Impala over HTTP, specify the HTTP port, 28000 by
-          default, and <code class="ph codeph">transportMode=http</code> in the connection string. For
-          example:
-<pre class="pre codeblock"><code>jdbc:hive2://myhost.example.com:28000/;transportMode=http</code></pre>
+        <p class="p"> For example, with the Hive JDBC driver, the class name is
+            <code class="ph codeph">org.apache.hive.jdbc.HiveDriver</code>. Once you have
+          configured Impala to work with JDBC, you can establish connections
+          between the two. To do so for a cluster that does not use Kerberos
+          authentication, use a connection string of the form
+              <code class="ph codeph">jdbc:hive2://<var class="keyword varname">host</var>:<var class="keyword varname">port</var>/;auth=noSasl</code>.
+          
+          For example, you might use: </p>
+
+        <pre class="pre codeblock"><code>jdbc:hive2://myhost.example.com:21050/;auth=noSasl</code></pre>
+        <p class="p"> To connect to an instance of Impala that requires Kerberos
+          authentication, use a connection string of the form
+              <code class="ph codeph">jdbc:hive2://<var class="keyword varname">host</var>:<var class="keyword varname">port</var>/;principal=<var class="keyword varname">principal_name</var></code>.
+          The principal must be the same user principal you used when starting
+          Impala. For example, you might use: </p>
+
+        <pre class="pre codeblock"><code>jdbc:hive2://myhost.example.com:21050/;principal=impala/myhost.example.com@H2.EXAMPLE.COM</code></pre>
+        <p class="p"> To connect to an instance of Impala that requires LDAP
+          authentication, use a connection string of the form
+              <code class="ph codeph">jdbc:hive2://<var class="keyword varname">host</var>:<var class="keyword varname">port</var>/<var class="keyword varname">db_name</var>;user=<var class="keyword varname">ldap_userid</var>;password=<var class="keyword varname">ldap_password</var></code>.
+          For example, you might use: </p>
+
+        <pre class="pre codeblock"><code>jdbc:hive2://myhost.example.com:21050/test_db;user=fred;password=xyz123</code></pre>
+        <div class="p"> To connect to an instance of Impala over HTTP, specify the HTTP
+          port, 28000 by default, and <code class="ph codeph">transportMode=http</code> in the
+          connection string. For example:
+          <pre class="pre codeblock"><code>jdbc:hive2://myhost.example.com:28000/;transportMode=http</code></pre>
         </div>
 
-
         <div class="note note"><span class="notetitle">Note:</span> 
           <p class="p">
         Prior to <span class="keyword">Impala 2.5</span>, the Hive JDBC driver did not support
@@ -397,29 +282,21 @@
 
         </div>
 
-
       </div>
 
-
     </div>
 
-
   </div>
 
-
   <div class="topic concept nested1" aria-labelledby="ariaid-title6" id="jdbc_odbc_notes">
-
-    <h2 class="title topictitle2" id="ariaid-title6">Notes about JDBC and ODBC Interaction with Impala SQL Features</h2>
-
+    <h2 class="title topictitle2" id="ariaid-title6">Notes about JDBC and ODBC Interaction with Impala SQL
+      Features</h2>
 
     <div class="body conbody">
-
-      <p class="p">
-        Most Impala SQL features work equivalently through the <span class="keyword cmdname">impala-shell</span>
-        interpreter of the JDBC or ODBC APIs. The following are some exceptions to keep in mind
-        when switching between the interactive shell and applications using the APIs:
-      </p>
-
+      <p class="p"> Most Impala SQL features work equivalently through the
+          <span class="keyword cmdname">impala-shell</span> interpreter of the JDBC or ODBC APIs.
+        The following are some exceptions to keep in mind when switching between
+        the interactive shell and applications using the APIs: </p>
 
       <ul class="ul">
         <li class="li">
@@ -429,38 +306,34 @@
 
           <ul class="ul">
             <li class="li">
-              <p class="p">
-                Queries involving the complex types (<code class="ph codeph">ARRAY</code>,
-                <code class="ph codeph">STRUCT</code>, and <code class="ph codeph">MAP</code>) require notation that might
-                not be available in all levels of JDBC and ODBC drivers. If you have trouble
-                querying such a table due to the driver level or inability to edit the queries
-                used by the application, you can create a view that exposes a <span class="q">"flattened"</span>
-                version of the complex columns and point the application at the view. See
-                <a class="xref" href="impala_complex_types.html#complex_types">Complex Types (Impala 2.3 or higher only)</a> for details.
+              <p class="p"> Queries involving the complex types (<code class="ph codeph">ARRAY</code>,
+                  <code class="ph codeph">STRUCT</code>, and <code class="ph codeph">MAP</code>) require
+                notation that might not be available in all levels of JDBC and
+                ODBC drivers. If you have trouble querying such a table due to
+                the driver level or inability to edit the queries used by the
+                application, you can create a view that exposes a
+                  <span class="q">"flattened"</span> version of the complex columns and point the
+                application at the view. See <a class="xref" href="impala_complex_types.html#complex_types">Complex Types (Impala 2.3 or higher only)</a> for details.
               </p>
 
             </li>
 
-
             <li class="li">
-              <p class="p">
-                The complex types available in <span class="keyword">Impala 2.3</span> and higher are
-                supported by the JDBC <code class="ph codeph">getColumns()</code> API. Both
-                <code class="ph codeph">MAP</code> and <code class="ph codeph">ARRAY</code> are reported as the JDBC SQL
-                Type <code class="ph codeph">ARRAY</code>, because this is the closest matching Java SQL type.
-                This behavior is consistent with Hive. <code class="ph codeph">STRUCT</code> types are
-                reported as the JDBC SQL Type <code class="ph codeph">STRUCT</code>.
-              </p>
-
-
-              <div class="p">
-                To be consistent with Hive's behavior, the TYPE_NAME field is populated with the
-                primitive type name for scalar types, and with the full <code class="ph codeph">toSql()</code>
-                for complex types. The resulting type names are somewhat inconsistent, because
-                nested types are printed differently than top-level types. For example, the
-                following list shows how <code class="ph codeph">toSQL()</code> for Impala types are
-                translated to <code class="ph codeph">TYPE_NAME</code> values:
-<pre class="pre codeblock"><code>DECIMAL(10,10)         becomes  DECIMAL
+              <p class="p"> The complex types available in <span class="keyword">Impala 2.3</span> and higher are supported by the JDBC
+                  <code class="ph codeph">getColumns()</code> API. Both <code class="ph codeph">MAP</code>
+                and <code class="ph codeph">ARRAY</code> are reported as the JDBC SQL Type
+                  <code class="ph codeph">ARRAY</code>, because this is the closest matching
+                Java SQL type. This behavior is consistent with Hive.
+                  <code class="ph codeph">STRUCT</code> types are reported as the JDBC SQL
+                Type <code class="ph codeph">STRUCT</code>. </p>
+
+              <div class="p"> To be consistent with Hive's behavior, the TYPE_NAME field is
+                populated with the primitive type name for scalar types, and
+                with the full <code class="ph codeph">toSql()</code> for complex types. The
+                resulting type names are somewhat inconsistent, because nested
+                types are printed differently than top-level types. For example,
+                the following list shows how <code class="ph codeph">toSQL()</code> for Impala
+                types are translated to <code class="ph codeph">TYPE_NAME</code> values: <pre class="pre codeblock"><code>DECIMAL(10,10)         becomes  DECIMAL
 CHAR(10)               becomes  CHAR
 VARCHAR(10)            becomes  VARCHAR
 ARRAY&lt;DECIMAL(10,10)&gt;  becomes  ARRAY&lt;DECIMAL(10,10)&gt;
@@ -478,34 +351,24 @@ ARRAY&lt;VARCHAR(10)&gt;     becomes  ARRAY&lt;VARCHAR(10)&gt;
 
       </ul>
 
-
     </div>
 
-
   </div>
 
-
   <div class="topic concept nested1" aria-labelledby="ariaid-title7" id="jdbc_kudu">
-
     <h2 class="title topictitle2" id="ariaid-title7">Kudu Considerations for DML Statements</h2>
 
-
     <div class="body conbody">
-
-      <p class="p">
-        Currently, Impala <code class="ph codeph">INSERT</code>, <code class="ph codeph">UPDATE</code>, or other DML
-        statements issued through the JDBC interface against a Kudu table do not return JDBC
-        error codes for conditions such as duplicate primary key columns. Therefore, for
-        applications that issue a high volume of DML statements, prefer to use the Kudu Java API
-        directly rather than a JDBC application.
-      </p>
-
+      <p class="p"> Currently, Impala <code class="ph codeph">INSERT</code>, <code class="ph codeph">UPDATE</code>, or
+        other DML statements issued through the JDBC interface against a Kudu
+        table do not return JDBC error codes for conditions such as duplicate
+        primary key columns. Therefore, for applications that issue a high
+        volume of DML statements, prefer to use the Kudu Java API directly
+        rather than a JDBC application. </p>
 
     </div>
 
-
   </div>
 
-
 </body>
 </html>
\ No newline at end of file
diff --git a/docs/build/html/topics/impala_joins.html b/docs/build/html/topics/impala_joins.html
index 239f315..19fd757 100644
--- a/docs/build/html/topics/impala_joins.html
+++ b/docs/build/html/topics/impala_joins.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Joins in Impala SELECT Statements" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_select.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="joins" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_kerberos.html b/docs/build/html/topics/impala_kerberos.html
index 152f5de..d78cdb0 100644
--- a/docs/build/html/topics/impala_kerberos.html
+++ b/docs/build/html/topics/impala_kerberos.html
@@ -4,8 +4,8 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Enabling Kerberos Authentication for Impala" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_authentication.html" />
@@ -18,15 +18,15 @@
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="kerberos" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_known_issues.html b/docs/build/html/topics/impala_known_issues.html
index 01908a0..70482b1 100644
--- a/docs/build/html/topics/impala_known_issues.html
+++ b/docs/build/html/topics/impala_known_issues.html
@@ -4,15 +4,15 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Known Issues and Workarounds in Impala" />
 <meta name="DC.Relation" scheme="URI" content="../topics/impala_release_notes.html" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="known_issues" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
@@ -289,16 +289,6 @@
     </div>
 
 
-
-
-    
-
-    
-
-
-
-    
-
   </div>
 
 
@@ -583,16 +573,17 @@ explain SELECT 1 FROM alltypestiny a1
 
 
       <div class="body conbody">
-
-        <p class="p">
-          If the following error appears multiple times in a short duration while running a
-          query, it would mean that the connection between the <code class="ph codeph">impalad</code> and the
-          HDFS NameNode is in a bad state and hence the <code class="ph codeph">impalad</code> would have to
-          be restarted:
-        </p>
+        <p class="p"> In Impala 3.2 and higher, if the following error appears multiple
+          times in a short duration while running a query, it would mean that
+          the connection between the <code class="ph codeph">impalad</code> and the HDFS
+          NameNode is in a bad state and hence the <code class="ph codeph">impalad</code>
+          would have to be restarted: </p>
 
 
 <pre class="pre codeblock"><code>"hdfsOpenFile() for &lt;filename&gt; at backend &lt;hostname:port&gt; failed to finish before the &lt;hdfs_operation_timeout_sec&gt; second timeout " </code></pre>
+        <p class="p">In Impala 3.1 and lower, the same issue would cause Impala to wait for
+          a long time or hang without showing the above error message.</p>
+
 
         <p class="p">
           <strong class="ph b">Apache Issue:</strong>
@@ -666,8 +657,6 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
     </div>
 
 
-    
-
     <div class="topic concept nested2" aria-labelledby="ariaid-title22" id="flume_writeformat_text">
 
       <h3 class="title topictitle3" id="ariaid-title22">Configuration needed for Flume to be compatible with Impala</h3>
@@ -787,44 +776,46 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
 
     </div>
 
+    <div class="topic concept nested2" aria-labelledby="ariaid-title26" id="IMPALA-8953">
+      <h3 class="title topictitle3" id="ariaid-title26">Tables and databases sharing same name can cause query
+        failures</h3>
 
-  </div>
-
+      <div class="body conbody">
+        <p class="p">A table and a database that share the same name can cause a query
+          failure if the table is not readable by Impala, for example, the table
+          was created in Hive in the Open CSV Serde format. The following
+          exception will return:</p>
 
-  <div class="topic concept nested1" aria-labelledby="ariaid-title26" id="known_issues_limitations">
+        <pre class="pre codeblock"><code>CAUSED BY: TableLoadingException: Unrecognized table type for table</code></pre>
+        <p class="p">
+          <strong class="ph b">Apache Issue:</strong>
+          <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-8953" target="_blank">IMPALA-8953</a>
+        </p>
 
-    <h2 class="title topictitle2" id="ariaid-title26">Impala Known Issues: Limitations</h2>
+        <p class="p">
+          <strong class="ph b">Workaround:</strong> Do not create databases and tables with the same
+          names.</p>
 
+      </div>
 
-    <div class="body conbody">
+    </div>
 
-      <p class="p">
-        These issues are current limitations of Impala that require evaluation as you plan how
-        to integrate Impala into your data management workflow.
-      </p>
 
+  </div>
 
-    </div>
 
-    <div class="topic concept nested2" aria-labelledby="ariaid-title27" id="IMPALA-8829">
-      <h3 class="title topictitle3" id="ariaid-title27">Unable to Correctly Parse the Terabyte Unit</h3>
+  <div class="topic concept nested1" aria-labelledby="ariaid-title27" id="known_issues_limitations">
 
-      <div class="body conbody">
-        <p class="p">Impala does not support parsing strings that contain "TB" when used
-          as a unit for terabytes. The flags related to memory limits may be
-          affected, such as the flags for scratch space and data cache.</p>
+    <h2 class="title topictitle2" id="ariaid-title27">Impala Known Issues: Limitations</h2>
 
-        <p class="p"><strong class="ph b">Workaround:</strong> Use other supported units to specify values, e.g.
-          GB or MB.</p>
 
-        <p class="p"><strong class="ph b">Affected Versions:</strong> All versions</p>
+    <div class="body conbody">
 
-        <p class="p">
-          <strong class="ph b">Apache Issue:</strong>
-          <a class="xref" href="https://issues.apache.org/jira/browse/IMPALA-8829" target="_blank">IMPALA-8829</a>
-        </p>
+      <p class="p">
+        These issues are current limitations of Impala that require evaluation as you plan how
+        to integrate Impala into your data management workflow.
+      </p>
 
-      </div>
 
     </div>
 
@@ -978,10 +969,6 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE');
     </div>
 
 
-
-
-    
-
     <div class="topic concept nested2" aria-labelledby="ariaid-title33" id="IMPALA-532">
 
       <h3 class="title topictitle3" id="ariaid-title33">Impala should tolerate bad locale settings</h3>
diff --git a/docs/build/html/topics/impala_kudu.html b/docs/build/html/topics/impala_kudu.html
index 1587dfb..f8ba1c2 100644
--- a/docs/build/html/topics/impala_kudu.html
+++ b/docs/build/html/topics/impala_kudu.html
@@ -4,14 +4,14 @@
 <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 2019" />
-<meta name="DC.rights.owner" content="(C) Copyright 2019" />
+<meta name="copyright" content="(C) Copyright 2020" />
+<meta name="DC.rights.owner" content="(C) Copyright 2020" />
 <meta name="DC.Type" content="concept" />
 <meta name="DC.Title" content="Using Impala to Query Kudu Tables" />
 <meta name="prodname" content="Impala" />
 <meta name="prodname" content="Impala" />
-<meta name="version" content="Impala 3.3.x" />
-<meta name="version" content="Impala 3.3.x" />
+<meta name="version" content="Impala 3.4.x" />
+<meta name="version" content="Impala 3.4.x" />
 <meta name="DC.Format" content="XHTML" />
 <meta name="DC.Identifier" content="impala_kudu" />
 <link rel="stylesheet" type="text/css" href="../commonltr.css" />
diff --git a/docs/build/html/topics/impala_kudu_read_mode.html b/docs/build/html/topics/impala_kudu_read_mode.html
index 0353314..5269940 100644
--- a/docs/build/html/topics/impala_kudu_read_mode.html
... 12589 lines suppressed ...