[
https://issues.apache.org/jira/browse/IMPALA-10746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397861#comment-17397861
]
ASF subversion and git services commented on IMPALA-10746:
----------------------------------------------------------
Commit fcbb15a5ea902e66ac9c09c9b114f9ba9c7c109e in impala's branch
refs/heads/master from Sourabh Goyal
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=fcbb15a ]
IMPALA-10746: Drop table/db from catalog cache when drop table/db HMS
apis are accessed from catalog's metastore server.
This patch fixes a scenario where if table/db already exists in
cache and a user drops it via catalog metastore server endpoint
(i.e drop_table HMS api). When recreating the same via Impala
Shell, user gets an error that table/db already exists. The patch
fixes it by dropping table/db from HMS endpoints so that new
table/db succeeds
Testing:
Added new unit tests which cover drop_database and
drop_table HMS API
Change-Id: Ic2e2ad2630e2028b8ad26a6272ee766b27e0935c
Reviewed-on: http://gerrit.cloudera.org:8080/17576
Reviewed-by: <[email protected]>
Reviewed-by: Vihang Karajgaonkar <[email protected]>
Tested-by: Vihang Karajgaonkar <[email protected]>
> Create table fails after dropping same table from catalog HMS endpoint
> -----------------------------------------------------------------------
>
> Key: IMPALA-10746
> URL: https://issues.apache.org/jira/browse/IMPALA-10746
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog
> Reporter: Sourabh Goyal
> Priority: Major
>
> Consider the following sequence of operation on the same table:
> # User drops it via catalog HMS api like drop_table
> # User creates a table with same name
> Currently #2 fails with table already exists error. This is because the table
> is not dropped from catalog cache after step 1.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
