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 "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/10/28 15:17: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=16961148#comment-16961148 ]
ASF subversion and git services commented on IMPALA-9095:
---------------------------------------------------------
Commit 351a92217d8a406f452a844ef9389b7dce1d3448 in impala's branch refs/heads/master from Anurag Mantripragada
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=351a922 ]
IMPALA-9095: Alter table events generated by renames should apply renames
properly.
A recent change refactored alter table event handler for rename operations
which introduced a bug that causes renames to a different db to be applied
incorrectly to the same db. This change adds a check to see if both the old
db and the new db are in catalog and applies the change to newdb properly.
Testing:
1. We did not have a rename testcase that crossed a single db. Added a test
case for renaming to a different db.
2. Ran MetastoreEventsProcessorTests.
Change-Id: I5bf46a75cd872aba268e15dd7c02c2cb46d64890
Reviewed-on: http://gerrit.cloudera.org:8080/14549
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> 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
>
> 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