https://community.cloudera.com/t5/Support-Questions/IMPALA-scale-that-does-not-match-the-table-metadata-scale/m-p/277359#M207535 <P>Hi&nbsp;<a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/53391">@ravikumashi</a>,</P><P>This issue happens because individual INSERT statements open new parquet files, which means that the new file is created with the new schema. Although, Hive is able to read parquet files where the schema has different precision than the table metadata this feature is under development in Impala, please see<SPAN>&nbsp;</SPAN><A href="https://issues.apache.org/jira/browse/IMPALA-7087" target="_blank" rel="noopener">IMPALA-7087</A><SPAN>. The parquet schema can be checked with <EM>"parquet-tools schema"</EM>, it is deployed with CDH and should give similar outputs in this case like this:</SPAN></P><PRE># Pre-Alter<BR /># parquet-tools schema f04187260a7a7eb5-b49e8a5000000000_938468120_data.0.parq<BR />message schema {<BR /> optional fixed_len_byte_array(4) prec (DECIMAL(7,2));<BR />}<BR /># Post-Alter<BR /># parquet-tools schema f14ce5c3b035caed-8f4c958400000000_1136483050_data.0.parq<BR />message schema {<BR /> optional fixed_len_byte_array(4) prec (DECIMAL(9,6));<BR />}&nbsp;&nbsp;</PRE><P>&nbsp;</P> Mon, 16 Sep 2019 14:51:20 GMT tmater 2019-09-16T14:51:20Z