You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Vihang Karajgaonkar (Jira)" <ji...@apache.org> on 2020/06/14 06:26:00 UTC
[jira] [Commented] (IMPALA-9095) Alter table events generated by
renames are not renaming the table to a different DB.
[ https://issues.apache.org/jira/browse/IMPALA-9095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135053#comment-17135053 ]
Vihang Karajgaonkar commented on IMPALA-9095:
---------------------------------------------
Hi [~anuragmantri] Do you remember if this was a regression caused by IMPALA-9017? The description suggests this was introduced by some other patch.
> Alter table events generated by renames are not renaming the table to a different DB.
> -------------------------------------------------------------------------------------
>
> Key: IMPALA-9095
> URL: https://issues.apache.org/jira/browse/IMPALA-9095
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Reporter: Anurag Mantripragada
> Assignee: Anurag Mantripragada
> Priority: Critical
> Fix For: Impala 3.4.0
>
>
> Alter table renames was recently refactored. This introduced a bug where rename to a different database is not applied correctly.
> Steps to reproduce:
> From Hive:
> {code:java}
> create database bug1;
> create table bug1.foo (id int);
> create database bug2;
> alter table bug1.foo rename to bug2.foo;{code}
>
> From Impala:
> {code:java}
> use bug2;
> show tables;{code}
>
> Expect foo to show up in bug2, it doesn't.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org