commit	b6b31e4cc415d0ba22d30b17f5dd039ba23700a6	[log] [tgz]
author	stiga-huang <huangquanlong@gmail.com>	Thu Oct 24 11:37:25 2019 +0800
committer	Joe McDonnell <joemcdonnell@cloudera.com>	Thu Oct 24 22:10:03 2019 +0000
tree	0e6bcfb2ff31da31c26ee6ef98769f9c3f2e6ff1
parent	b02f51458396e5d9fcb1444ae9d33642cbf9580f [diff]

IMPALA-9071: Handle translated external HDFS table in CTAS

After upgrading Hive-3 to a version containing HIVE-22158, it's not
allowed for managed tables to be non transactional. Creating non ACID
tables will result in creating an external table with table property
'external.table.purge' set to true.

In Hive-3, the default location of external HDFS tables will be located
in 'metastore.warehouse.external.dir' if it's set. This property is
added by HIVE-19837 in Hive 2.7, but hasn't been added to Hive in cdh6
yet.

In CTAS statement, we create a temporary HMS Table for the analysis on
the Insert part. The table path is created assuming it's a managed
table, and the Insert part will use this path for insertion. However, in
Hive-3, the created table is translated to an external table. It's not
the same as we passed to the HMS API. The created table is located in
'metastore.warehouse.external.dir', while the table path we assumed is
in 'metastore.warehouse.dir'. This introduces bugs when these two
properties are different. CTAS statement will create table in one place
and insert data in another place.

This patch adds a new method in MetastoreShim to wrap the difference for
getting the default table path for non transactional tables between
Hive-2 and Hive-3.

Changes in the infra:
 - To support customizing hive configuration, add an env var,
   CUSTOM_CLASSPATH in bin/set-classpath.sh to be put in front of
   existing CLASSPATH. The customized hive-site.xml should be put inside
   CUSTOM_CLASSPATH.
 - Change hive-site.xml.py to generate a hive-site.xml with non default
   'metastore.warehouse.external.dir'
 - Add an option, --env_vars, in bin/start-impala-cluster.py to pass
   down CUSTOM_CLASSPATH.

Tests:
 - Add a custom cluster test to start Hive with
   metastore.warehouse.external.dir being set to non default value. Run
   it locally using CDP components with HIVE-22158. xfail the test until
   we bump CDP_BUILD_NUMBER to 1507246.
 - Run CORE tests using CDH components

Change-Id: I460a57dc877ef68ad7dd0864a33b1599b1e9a8d9
Reviewed-on: http://gerrit.cloudera.org:8080/14527
Reviewed-by: Csaba Ringhofer <csringhofer@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
Reviewed-by: Joe McDonnell <joemcdonnell@cloudera.com>

9 files changed

tree: 0e6bcfb2ff31da31c26ee6ef98769f9c3f2e6ff1

README.md

Welcome to Impala

Lightning-fast, distributed SQL queries for petabytes of data stored in Apache Hadoop clusters.

Impala is a modern, massively-distributed, massively-parallel, C++ query engine that lets you analyze, transform and combine data from a variety of data sources:

Best of breed performance and scalability.
Support for data stored in HDFS, Apache HBase and Amazon S3.
Wide analytic SQL support, including window functions and subqueries.
On-the-fly code generation using LLVM to generate CPU-efficient code tailored specifically to each individual query.
Support for the most commonly-used Hadoop file formats, including the Apache Parquet project.
Apache-licensed, 100% open source.

More about Impala

To learn more about Impala as a business user, or to try Impala live or in a VM, please visit the Impala homepage.

If you are interested in contributing to Impala as a developer, or learning more about Impala's internals and architecture, visit the Impala wiki.

Supported Platforms

Impala only supports Linux at the moment.

Export Control Notice

This distribution uses cryptographic software and may be subject to export controls. Please refer to EXPORT_CONTROL.md for more information.

Build Instructions

See bin/bootstrap_build.sh.

Detailed Build Notes

Impala can be built with pre-built components or components downloaded from S3. The components needed to build Impala are Apache Hadoop, Hive, HBase, and Sentry. If you need to manually override the locations or versions of these components, you can do so through the environment variables and scripts listed below.

Scripts and directories

Location	Purpose
bin/impala-config.sh	This script must be sourced to setup all environment variables properly to allow other scripts to work
bin/impala-config-local.sh	A script can be created in this location to set local overrides for any environment variables
bin/impala-config-branch.sh	A version of the above that can be checked into a branch for convenience.
bin/bootstrap_build.sh	A helper script to bootstrap some of the build requirements.
bin/bootstrap_development.sh	A helper script to bootstrap a developer environment. Please read it before using.
be/build/	Impala build output goes here.
be/generated-sources/	Thrift and other generated source will be found here.

Build Related Variables

Environment variable	Default value	Description
IMPALA_HOME		Top level Impala directory
IMPALA_TOOLCHAIN	“${IMPALA_HOME}/toolchain”	Native toolchain directory (for compilers, libraries, etc.)
SKIP_TOOLCHAIN_BOOTSTRAP	“false”	Skips downloading the toolchain any python dependencies if “true”
CDH_BUILD_NUMBER		Identifier to indicate the CDH build number
CDH_COMPONENTS_HOME	“${IMPALA_HOME}/toolchain/cdh_components-${CDH_BUILD_NUMBER}”	Location of the CDH components within the toolchain.
CDH_MAJOR_VERSION	“5”	Identifier used to uniqueify paths for potentially incompatible component builds.
IMPALA_CONFIG_SOURCED	“1”	Set by ${IMPALA_HOME}/bin/impala-config.sh (internal use)
JAVA_HOME	“/usr/lib/jvm/${JAVA_VERSION}”	Used to locate Java
JAVA_VERSION	“java-7-oracle-amd64”	Can override to set a local Java version.
JAVA	“${JAVA_HOME}/bin/java”	Java binary location.
CLASSPATH		See bin/set-classpath.sh for details.
PYTHONPATH	Will be changed to include: “${IMPALA_HOME}/shell/gen-py” “${IMPALA_HOME}/testdata” “${THRIFT_HOME}/python/lib/python2.7/site-packages” “${HIVE_HOME}/lib/py” “${IMPALA_HOME}/shell/ext-py/prettytable-0.7.1/dist/prettytable-0.7.1” "${IMPALA_HOME}/shell/ext-py/sasl-0.1.1/dist/sasl-0.1.1-py2.7-linux-x "${IMPALA_HOME}/shell/ext-py/sqlparse-0.1.19/dist/sqlparse-0.1.19-py2

Source Directories for Impala

Environment variable	Default value	Description
IMPALA_BE_DIR	“${IMPALA_HOME}/be”	Backend directory. Build output is also stored here.
IMPALA_FE_DIR	“${IMPALA_HOME}/fe”	Frontend directory
IMPALA_COMMON_DIR	“${IMPALA_HOME}/common”	Common code (thrift, function registry)

Various Compilation Settings

Environment variable	Default value	Description
IMPALA_BUILD_THREADS	“8” or set to number of processors by default.	Used for make -j and distcc -j settings.
IMPALA_MAKE_FLAGS	""	Any extra settings to pass to make. Also used when copying udfs / udas into HDFS.
USE_SYSTEM_GCC	“0”	If set to any other value, directs cmake to not set GCC_ROOT, CMAKE_C_COMPILER, CMAKE_CXX_COMPILER, as well as setting TOOLCHAIN_LINK_FLAGS
IMPALA_CXX_COMPILER	“default”	Used by cmake (cmake_modules/toolchain and clang_toolchain.cmake) to select gcc / clang
USE_GOLD_LINKER	“true”	Directs backend cmake to use gold.
IS_OSX	“false”	(Experimental) currently only used to disable Kudu.

Dependencies

Environment variable	Default value	Description
HADOOP_HOME	“${CDH_COMPONENTS_HOME}/hadoop-${IMPALA_HADOOP_VERSION}/”	Used to locate Hadoop
HADOOP_INCLUDE_DIR	“${HADOOP_HOME}/include”	For ‘hdfs.h’
HADOOP_LIB_DIR	“${HADOOP_HOME}/lib”	For ‘libhdfs.a’ or ‘libhdfs.so’
HIVE_HOME	“${CDH_COMPONENTS_HOME}/{hive-${IMPALA_HIVE_VERSION}/”
HBASE_HOME	“${CDH_COMPONENTS_HOME}/hbase-${IMPALA_HBASE_VERSION}/”
SENTRY_HOME	“${CDH_COMPONENTS_HOME}/sentry-${IMPALA_SENTRY_VERSION}/”	Used to setup test data
THRIFT_HOME	“${IMPALA_TOOLCHAIN}/thrift-${IMPALA_THRIFT_VERSION}”