You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/12/21 19:08:00 UTC

[jira] [Resolved] (IMPALA-5151) Adding partition on impala over a table with old metadata

     [ https://issues.apache.org/jira/browse/IMPALA-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong resolved IMPALA-5151.
-----------------------------------
    Resolution: Fixed

We added support to pick up changes automatically with IMPALA-7954

> Adding partition on impala over a table with old metadata 
> ----------------------------------------------------------
>
>                 Key: IMPALA-5151
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5151
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Daniel Goldszmit
>            Priority: Major
>
> 1) connect on beeline and execute:
> CREATE TABLE test(id int,description string) PARTITIONED BY (year string) ;
> 2) connect on Impala and execute:
> invalidate metadata test;
> desc test;
> 3) from beeline change the table structure:
> ALTER TABLE test ADD COLUMNS  (missing_col string );
> 4) At this point Impala holds a old metadata, an impala does not know about the new column "missing_col"  when execute the SQL statement:
> alter table add partition (year='2017');
> Impala will change the table structure for the table test, basically reverting any changes that have been made on the table to the point from impala last invalidate metadata.
> 5) from beeline session executing the command:
> desc test
> the new field "missing_col" no longer will appear.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)