This loads data into Kudu as part of end-to-end test setup, which
was previously disabled as INSERT was missing.
Specifically this used Impala loading (vs. hive loading) and uses
Kudu specific handling in two ways:
- Tables are created "managed", i.e. without the EXTERNAL keyword
so that tables are actually dropped in kudu as part of the setup.
This was required as Kudu does not support overwriting tables
(i.e. INSERT OVERWRITE).
- Insert statements in Kudu do not have the OVERWRITE keyword since
tables in kudu cannot be safely overwritten, so this replaces
OVERWRITE with INTO.
Change-Id: I4ee3ded542e9b5c71207fd0cb494e0c2c0890667
Reviewed-on: http://gerrit.sjc.cloudera.com:8080/6985
Tested-by: jenkins
Reviewed-by: Martin Grund <mgrund@cloudera.com>
2bea2dbeb7