[jira] [Resolved] (IMPALA-9093) Fix ACID upgrade tests to account for HIVE-22158 (table translation)

["Gabor Kaszab (Jira)" <ji...@apache.org>]

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

Gabor Kaszab resolved IMPALA-9093.
----------------------------------
    Fix Version/s: Impala 3.4.0
       Resolution: Fixed

> Fix ACID upgrade tests to account for HIVE-22158 (table translation)
> --------------------------------------------------------------------
>
>                 Key: IMPALA-9093
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9093
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 3.4.0
>            Reporter: Joe McDonnell
>            Assignee: Gabor Kaszab
>            Priority: Blocker
>             Fix For: Impala 3.4.0
>
>
> There are tests that create a normal managed table and upgrade that table to a transactional table. For example, in test_acid.py, we run acid.test, which has:
> {noformat}
> create table upgraded_table (x int);
> insert into upgraded_table values (1);
> # Upgrade to the table to insert only acid when there are already values in it.
> alter table upgraded_table set tblproperties
>  ('transactional' = 'true', 'transactional_properties' = 'insert_only');
> insert into upgraded_table values (2);
> insert into upgraded_table values (3);{noformat}
> With HIVE-22158, the create table is now translated to an external table, and this now fails with:
> {noformat}
> E   ImpalaBeeswaxException: ImpalaBeeswaxException:
> E    INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>
> E    MESSAGE: ImpalaRuntimeException: Error making 'alter_table' RPC to Hive Metastore: 
> E   CAUSED BY: MetaException: test_acid_basic_5d04240b.upgraded_table cannot be declared transactional because it's an external table{noformat}
> If external tables can't be upgraded and all managed tables are now external, then this test case is invalid and can be removed. We should make sure that this is how it is supposed to work.



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