hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Janus Chow (JIRA)" <>
Subject [jira] [Commented] (HIVE-19994) Impala "drop table" fails with Hive Metastore exception
Date Mon, 29 Jul 2019 08:05:00 GMT


Janus Chow commented on HIVE-19994:

[~karthik.manamcheri] Hello, after I added this patch, I still got the same error.
 Besides, I was wondering if the name of the foreign-key does matter, because in the error,
the message is
"a foreign key constraint fails ("xxx"."COLUMNS_V2", CONSTRAINT "COLUMNS_V2_FK1"{code}
And in the patch, it was "COLUMNS_V2_FK".

> Impala "drop table" fails with Hive Metastore exception
> -------------------------------------------------------
>                 Key: HIVE-19994
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 1.1.0
>         Environment: Hadoop distribution: CHD 5.14.2
> Hive version:  1.1.0-cdh5.14.2
> Impala version: 2.11.0
> Kudu version: 1.6.0
>            Reporter: Rodion Myronov
>            Assignee: Karthik Manamcheri
>            Priority: Major
>             Fix For: 4.0.0
>         Attachments: HIVE-19994.1.patch, metastore_exception.txt
> "drop table" statement in Impala shell fails with the following exception:
> {{ImpalaRuntimeException: Error making 'dropTable' RPC to Hive Metastore: CAUSED BY:
MetaException: One or more instances could not be deleted}}
> Metastore log file shows that "DELETE FROM `PARTITION_KEYS` WHERE `TBL_ID`=?" statement
fails because of foreign key violation (full stacktrace will be added):
> {{Caused by: java.sql.BatchUpdateException: Cannot delete or update a parent row: a foreign
key constraint fails ("hivemetastore_emtig3vtq7qp1tiooo07sb70ud"."COLUMNS_V2", CONSTRAINT
> The table is created and then dropped as a part of ETL process executed every hour. Most
of the time it works fine, the issue is not reproducible at will.
> Table creation script is:
> {{CREATE TABLE IF NOT EXISTS price_advisor_ouput.t_switching_coef_source}}
> {{( }}
> {{...fields here...}}
> {{PRIMARY KEY (...PK field here...)}}
> {{)}}
> Not sure how to approach diagnostics and fix, so any input will be really appreciated. 
> Thanks in advance, 
> Rodion Myronov

This message was sent by Atlassian JIRA

View raw message