mirror of
https://github.com/apache/impala.git
synced 2025-12-30 03:01:44 -05:00
99d3caacb7
The S3 work really enabled any Hadoop FileSystem to work with Impala, but a small tweak is needed for LocalFileSystem due to how the Hadoop Path code deals with URIs that don't have an authority component. While we aren't claiming support for arbitrary FileSystem's at this tiem, it is useful to test this. Since the S3 testing is done as a nightly test rather than pre-checkin, we can use the LocalFileSystem to regression test that: 1) Impala can access table data living on a secondary filesystem, i.e. not the filesystem specified by fs.defaultFS. 2) Impala does not make assumptions that the filesystem has type DistributedFileSystem. Change-Id: Ie9b858ea440c9b3b332602e034c8052b168c57da Reviewed-on: http://gerrit.cloudera.org:8080/121 Reviewed-by: Martin Grund <mgrund@cloudera.com> Tested-by: Internal Jenkins
bad_parquet_data.parquet:
Generated with parquet-mr 1.2.5
Contains 3 single-column rows:
"parquet"
"is"
"fun"
repeated_values.parquet:
Generated with parquet-mr 1.2.5
Contains 3 single-column rows:
"parquet"
"parquet"
"parquet"
multiple_rowgroups.parquet:
Generated with parquet-mr 1.2.5
Populated with:
hive> set parquet.block.size=500;
hive> INSERT INTO TABLE tbl
SELECT l_comment FROM tpch.lineitem LIMIT 1000;
alltypesagg_hive_13_1.parquet:
Generated with parquet-mr version 1.5.0-cdh5.4.0-SNAPSHOT
hive> create table alltypesagg_hive_13_1 stored as parquet as select * from alltypesagg;