You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Sahil Takiar (JIRA)" <ji...@apache.org> on 2019/04/07 20:22:00 UTC

[jira] [Resolved] (IMPALA-7640) ALTER TABLE RENAME on managed Kudu table should rename underlying Kudu table

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

Sahil Takiar resolved IMPALA-7640.
----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.3.0

> ALTER TABLE RENAME on managed Kudu table should rename underlying Kudu table
> ----------------------------------------------------------------------------
>
>                 Key: IMPALA-7640
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7640
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Catalog
>    Affects Versions: Impala 2.12.0
>            Reporter: Mike Percy
>            Assignee: Sahil Takiar
>            Priority: Major
>             Fix For: Impala 3.3.0
>
>
> Currently, when I execute ALTER TABLE RENAME on a managed Kudu table it will not rename the underlying Kudu table. Because of IMPALA-5654 it becomes nearly impossible to rename the underlying Kudu table, which is confusing and makes the Kudu tables harder to identify and manage.



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