Background: The data type of some fields in the Hive table has been modified, such as from String-> Double, at which point the underlying file format for the table is parquet, after the modification, the Impala index is updated, and then the fields that modify the data type appear with the Parquet Problem with schema column data type incompatibility.
such as: impala--
Extracting results for the following error:
Bad status for Request Tfetchresultsreq (fetchtype=0, Operationhandle=toperationhandle (Hasresultset=true, Modifiedrowcount=none, Operationtype=0, Operationid=thandleidentifier (secret= ' d\x11\x18]\xf7\xa2e*\x8f\x99ky\x9c \xc8\xda> ', guid= ' d\x11\x18]\xf7\xa2e*\x8f\x99ky\x9c\xc8\xda> '), orientation=4, maxRows=100): Tfetchresultsresp (Status=tstatus errorcode=none, errormessage= "File" hdfs://xxx:8020/user/hdfs/test/ 0f399649-1e1d-444b-9d71-24c8db0ac7f3.parquet ' has a incompatible parquet schema for column ' default.test.yyy '. Column type:double, parquet schema:\noptional byte_array QTY [i:30 d:1 r:0]\n], sqlstate= ' HY000 ', Infomessages=none, stat uscode=3), Results=none, Hasmorerows=none)
To view the error message:
Errormessage= "File ' Hdfs://xxx:8020/user/hdfs/test/0f399649-1e1d-444b-9d71-24c8db0ac7f3.parquet ' has" Incompatible parquet schema for column ' default.test.yyy '. Column type:double, parquet schema:\noptional byte_array QTY [i:30 d:1 r:0]\n]
Corresponding hive similar, solution, reference:
1. Http://stackoverflow.com/questions/36085891/hive-doesnt-change-parquet-schema
2. https://issues.cloudera.org/browse/IMPALA-779