[ https://issues.apache.org/jira/browse/IMPALA-9738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong resolved IMPALA-9738. ----------------------------------- Resolution: Invalid > incompatible Parquet schema for column "ex: x is of type String" Column type: > STRING, Parquet schema: > ----------------------------------------------------------------------------------------------------- > > Key: IMPALA-9738 > URL: https://issues.apache.org/jira/browse/IMPALA-9738 > Project: IMPALA > Issue Type: Question > Components: Clients > Affects Versions: Impala 2.12.0 > Environment: Test > Reporter: RK > Priority: Critical > Fix For: Impala 2.12.0 > > > I have an Existing External Table called for example A contains n number of > columns and this table is loaded daily with partitioned column as > extract_date. > We got a request from business to add few more columns in the existing table. > To implement this we have done following things. > alter table xxxx.yyyyyy add columns (`c10` string COMMENT '',`b` string > COMMENT '',`c11` string COMMENT '',`c12` string COMMENT '',`c13` string > COMMENT '',`c14` string COMMENT '',`c15` string COMMENT '') ; > alter table xxxx.yyyyyyy change `c8` `c8` string COMMENT '' after `c7` ; > After i did the above 2 steps, then i went to HIVE and did MSCK REPAIR TABLE > xxxx.yyyyyy; > Partitions added.(there are partitions from 2018). > > Before our change as mentioned above i can able to query the data bth from > IMPALA and HIVE but after executing ALTER COMMANDS, I am facing an error as > mentioned below. > > select * from xxxx.yyyyyyy where extract_date like '2019%'; > Query: select * from XXXXX.YYYYYYY where extract_date like '2019%' > Query submitted at: 2020-05-09 11:57:10 (Coordinator: ' xxxx.yyyyyyy .c9'. > Column type: STRING, Parquet schema: > optional fixed_len_byte_array a_auth [i:12 d:1 r:0] > > Where as in Hive same query i can able to browse the data. No issues. ONLY IN > IMPALA ITS GIVING AN ISSUE. > > Troubleshooting steps: > Created new table without additional columns and pointed the external path as > new and copied the Previously created partitions to new path. > MSCK REPAIR TABLE TABLE NAME; > Both in impala and Hive select query is working. > > 2. Added additional fields to the newly created table with alter commands > then did the following things > MSCK REPAIR TABLE TABLE NAME; > In Impala : REFRESH TABLE TABLE NAME; > INVALIDATE METADATA TABLE NAME; > This time in Hive select query worked but in Impala got the above mentioned > Error. > Can some one guide me why this is happening and how to fix this issue. > > Impala Shell v2.12.0-cdh5.16.2 > > > > > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)