aphadke f87da848f5 IMPALA-4863/IMPALA-5311: Correctly account the file type and compression codec ...

If a scan range is skipped at runtime the scan node skips reading
the range and never figures out the underlying compression codec used
to compress the files. In such a scenario we default the compression
codec to NONE which can be misleading. This change marks these files
as filtered in the scan node profile

e.g. - File Formats: TEXT/NONE:364 TEXT/NONE(Skipped):1460

Change-Id: I797916505f62e568f4159e07099481b8ff571da2
Reviewed-on: http://gerrit.cloudera.org:8080/7245
Reviewed-by: Tim Armstrong <tarmstrong@cloudera.com>
Tested-by: Tim Armstrong <tarmstrong@cloudera.com>

2017-09-21 17:38:08 +00:00

..

queries

IMPALA-4863/IMPALA-5311: Correctly account the file type and compression codec

2017-09-21 17:38:08 +00:00

functional-query_core.csv

IMPALA-3718: Support subset of functional-query for Kudu

2016-09-14 22:11:04 +00:00

functional-query_dimensions.csv

Starting Kudu as part of the run-all.sh command / data loading

2015-06-01 15:53:34 -07:00

functional-query_exhaustive.csv

IMPALA-3718: Support subset of functional-query for Kudu

2016-09-14 22:11:04 +00:00

functional-query_pairwise.csv

IMPALA-3718: Support subset of functional-query for Kudu

2016-09-14 22:11:04 +00:00