[
https://issues.apache.org/jira/browse/IMPALA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-779.
----------------------------------
Resolution: Duplicate
> Incompatible type error when querying file created from AvroParquetWriter.
> --------------------------------------------------------------------------
>
> Key: IMPALA-779
> URL: https://issues.apache.org/jira/browse/IMPALA-779
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 1.2.1
> Environment: CDH4.3
> Impala 1.2.1
> Reporter: Doug Meil
> Priority: Minor
> Labels: usability
>
> Scenario:
> 1) Created Parquet file with AvroParquetWriter in code with 100 or so columns.
> 2) Created external table with Parquet against this file defined with only
> the first 4 columns and queried them all successfully.
> 3) Created second external table against this same file that was defined with
> the last 4 columns and the query blows up - complaining about the first
> column, and that wasn't even in the table definition.
> {code}
> [rd-namenode.explorys:21000] > select * from mytable2 limit 4;
> Query: select * from mytable2 limit 4
> ERROR: File
> hdfs://namenode:8021/user/doug.meil/parquet/mytable/regid=2/myfile.prq has an
> incompatible type with the table schema for column long1. Expected type:
> BYTE_ARRAY. Actual type: INT64
> ERROR: Invalid query handle
> {code}
> The original Avro schema defined 'long1' like this...
> {code}
> {"name": "long1", "type": "long"},
> {code}
> The fact that the "Actual type" is INT64 seems correct - because I meant to
> put a long in there. Why does Impala think the expected type is a BYTE_ARRAY?
> Note: summary queries (e.g., select count(*) from mytable2) actually WORK.
> Go figure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
