You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Abhishek (Jira)" <ji...@apache.org> on 2021/06/25 02:51:00 UTC
[jira] [Created] (KUDU-3299) Improve error logging when restoring a
table with "impala::" prefix
Abhishek created KUDU-3299:
------------------------------
Summary: Improve error logging when restoring a table with "impala::" prefix
Key: KUDU-3299
URL: https://issues.apache.org/jira/browse/KUDU-3299
Project: Kudu
Issue Type: Improvement
Components: backup
Reporter: Abhishek
When a kudu table created through impala is backed up in a cluster without Kudu+HMS integration, it will be containing the "impala::" prefix. If this table backup is restored in a cluster with Kudu+HMS integration in place it fails with the below error message:
{code:java}
ERROR backup.KuduRestore$: Failed to restore table impala::default.my_first_table: Look back in the logs for the full exception. Error: Failure(org.apache.kudu.client.NonRecoverableException: failed to create HMS catalog entry for table [id=077ea8941ffa49aea5b934dbaa890f9c]: when the Hive Metastore integration is enabled, Kudu table names must be a period ('.') separated database and table name identifier pair, each containing only ASCII alphanumeric characters, '_', and '/': impala::default.my_first_table){code}
In this scenario it would be helpful if we can present the option of removing "impala::" prefix as a part of the above error message (–removeImpalaPrefix). This option is available as a part of the restore job
--
This message was sent by Atlassian Jira
(v8.3.4#803005)