You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2018/03/29 23:45:00 UTC

[jira] [Updated] (ATLAS-2524) Hive hook with V2 notifications - incorrect handling of 'alter view as' operation

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

Madhan Neethiraj updated ATLAS-2524:
------------------------------------
    Reporter: Sharmadha Sainath  (was: Madhan Neethiraj)

> Hive hook with V2 notifications - incorrect handling of 'alter view as' operation
> ---------------------------------------------------------------------------------
>
>                 Key: ATLAS-2524
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2524
>             Project: Atlas
>          Issue Type: Bug
>          Components: atlas-intg
>    Affects Versions: 1.0.0, 0.8.3
>            Reporter: Sharmadha Sainath
>            Assignee: Madhan Neethiraj
>            Priority: Major
>
> After recent update of Hive hook, to replace use of V1 notifications with V2 notifications (ATLAS-2491), 'alter view as' operation results in incorrect metadata update. Consider the following Hive statements which create a view and followed by an alter view:
> {code}
> create table table1(col1 int, col2 string);
> create table table2(col3 date , col4 string);
> create view view1 as select * from table1;
> alter view view1 as select * from table2;
> {code}
> With earlier Hive hook implementation, after "alter view as", 'view1' would have columns col1 and col2 as DELETED and col3, col4 as ACTIVE.
> After update in ATLAS-2491, view1 continues to show col1 and col2 in ACTIVE state; and doesn't have col3 and col4 columns.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)