mirror of
https://github.com/apache/impala.git
synced 2026-02-03 09:00:39 -05:00
faf322dd41
Currently, Impala always assumes that the data in the binary columns of JSON tables is base64 encoded. However, before HIVE-21240, Hive wrote binary data to JSON tables without base64 encoding it, instead writing it as escaped strings. After HIVE-21240, Hive defaults to base64 encoding binary data when writing to JSON tables and introduces the serde property 'json.binary.format' to indicate the encoding method of binary data in JSON tables. To maintain consistency with Hive and avoid correctness issues caused by reading data in an incorrect manner, this patch also introduces the serde property 'json.binary.format' to specify the reading method for binary data in JSON tables. Currently, this property supports reading in either base64 or rawstring formats, same as Hive. Additionally, this patch introduces a query option 'json_binary_format' to achieve the same effect. This query option will only take effect for JSON tables where the serde property 'json.binary.format' is not set. The reading format of binary columns in JSON tables can be configured globally by setting the 'default_query_options'. It should be noted that the default value of 'json_binary_format' is 'NONE', and impala will prohibit reading binary columns of JSON tables that either have "no 'json.binary.format' set and 'json_binary_format' is 'NONE'" or "an invalid 'json.binary.format' value set", and will provide an error message to avoid using an incorrect format without the user noticing. Testing: - Enabled existing binary type E2E tests for JSON tables - Added new E2E test for 'json.binary.format' Change-Id: Idf61fa3afc0f33caa63fbc05393e975733165e82 Reviewed-on: http://gerrit.cloudera.org:8080/22289 Reviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
87 lines
3.2 KiB
Plaintext
87 lines
3.2 KiB
Plaintext
This directory contains Impala test data sets. The directory layout is structured as follows:
|
|
|
|
datasets/
|
|
<data set>/<data set>_schema_template.sql
|
|
<data set>/<data files SF1>/data files
|
|
<data set>/<data files SF2>/data files
|
|
|
|
Where SF is the scale factor controlling data size. This allows for scaling the same schema to
|
|
different sizes based on the target test environment.
|
|
|
|
The schema template SQL files have the following format:
|
|
|
|
The goal is to provide a single place to define a table + data files
|
|
and have the schema and data load statements generated for each combination of file
|
|
format, compression, etc. The way this works is by specifying how to create a
|
|
'base table'. The base table can be used to generate tables in other file formats
|
|
by performing the defined INSERT / SELECT INTO statement. Each new table using the
|
|
file format/compression combination needs to have a unique name, so all the
|
|
statements are pameterized on table name.
|
|
The template file is read in by the 'generate_schema_statements.py' script to
|
|
to generate all the schema for the Impala benchmark tests.
|
|
|
|
Each table is defined as a new section in the file with the following format:
|
|
|
|
====
|
|
---- SECTION NAME
|
|
section contents
|
|
...
|
|
---- ANOTHER SECTION
|
|
... section contents
|
|
---- ... more sections...
|
|
|
|
Note that tables are delimited by '====' and that even the first table in the
|
|
file must include this header line.
|
|
|
|
The supported section names are:
|
|
|
|
DATASET
|
|
Data set name - Used to group sets of tables together
|
|
BASE_TABLE_NAME
|
|
The name of the table within the database
|
|
CREATE
|
|
Explicit CREATE statement used to create the table (executed by Impala)
|
|
CREATE_HIVE
|
|
Same as the above, but will be executed by Hive instead. If specified,
|
|
'CREATE' must not be specified.
|
|
CREATE_KUDU
|
|
Customized CREATE TABLE statement used to create the table for Kudu-specific
|
|
syntax.
|
|
|
|
COLUMNS
|
|
PARTITION_COLUMNS
|
|
ROW_FORMAT
|
|
HBASE_COLUMN_FAMILIES
|
|
TABLE_PROPERTIES
|
|
HBASE_REGION_SPLITS
|
|
If no explicit CREATE statement is provided, a CREATE statement is generated
|
|
from these sections (see 'build_table_template' function in
|
|
'generate-schema-statements.py' for details)
|
|
|
|
ALTER
|
|
A set of ALTER statements to be executed after the table is created
|
|
(typically to add partitions, but may also be used for other settings that
|
|
cannot be specified directly in the CREATE TABLE statement).
|
|
|
|
These statements are ignored for HBase and Kudu tables.
|
|
|
|
LOAD
|
|
The statement used to load the base (text) form of the table. This is
|
|
typically a LOAD DATA statement.
|
|
|
|
DEPENDENT_LOAD
|
|
DEPENDENT_LOAD_KUDU
|
|
DEPENDENT_LOAD_HIVE
|
|
DEPENDENT_LOAD_ACID
|
|
DEPENDENT_LOAD_JSON
|
|
Statements to be executed during the "dependent load" phase. These statements
|
|
are run after the initial (base table) load is complete.
|
|
|
|
HIVE_MAJOR_VERSION
|
|
The required major version of Hive for this table. If the major version
|
|
of Hive at runtime does not exactly match the version specified in this section,
|
|
the table will be skipped.
|
|
|
|
NOTE: this is not a _minimum_ version -- if HIVE_MAJOR_VERSION specifies '2',
|
|
the table will _not_ be loaded/created on Hive 3.
|