jprdonnelly/impala
1
0
Fork 0
mirror of https://github.com/apache/impala.git synced 2026-01-06 06:01:03 -05:00
Code Issues Projects Releases Wiki Activity

IMPALA-5903: Inconsistent specification of result set and result set metadata

Browse Source 
Before this commit it was quite random which DDL oprations
returned a result set and which didn't.

With this commit, every DDL operations return a summary of
its execution. They declare their result set schema in
Frontend.java, and provide the summary in CalatogOpExecutor.java.

Updated the tests according to the new behavior.

Change-Id: Ic542fb8e49e850052416ac663ee329ee3974e3b9
Reviewed-on: http://gerrit.cloudera.org:8080/9090
Reviewed-by: Alex Behm <alex.behm@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
This commit is contained in:
Zoltan Borok-Nagy
2018-04-05 14:54:27 +02:00
committed by Impala Public Jenkins
parent 27c028f057
commit 2ee914d5b3
37 changed files with 366 additions and 72 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
testdata/workloads/functional-query/queries/QueryTest/insert_permutation.test vendored
View File

@@ -3,6 +3,7 @@
create database insert_permutation_test location
'$FILESYSTEM_PREFIX/test-warehouse/insert_permutation_test'
---- RESULTS
'Database has been created.'
====
---- QUERY
use insert_permutation_test
@@ -14,6 +15,7 @@ create table perm_part(int_col1 int, string_col string) partitioned by (p1 int,
create table parquet_part(int_col1 int, string_col string)
partitioned by (p1 int, p2 string) stored as parquet;
---- RESULTS
'Table has been created.'
====
---- QUERY
# Simple non-permutation