[
https://issues.apache.org/jira/browse/KUDU-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192292#comment-17192292
]
Grant Henke commented on KUDU-2883:
-----------------------------------
This was fixed via
https://github.com/apache/kudu/commit/1ccebcc43e28b86d58a6642d844958413a2f1354
> HMS check/fix tool should accommodate tables without ID for dropping orphan
> hms tables.
> ---------------------------------------------------------------------------------------
>
> Key: KUDU-2883
> URL: https://issues.apache.org/jira/browse/KUDU-2883
> Project: Kudu
> Issue Type: Bug
> Components: CLI, hms
> Affects Versions: 1.10.0
> Reporter: Hao Hao
> Priority: Major
>
> In cases that table has no ID(created when HMS integration is disabled), HMS
> check/fix tool should accommodate such cases for dropping orphan hms tables
> (https://github.com/apache/kudu/blob/master/src/kudu/tools/tool_action_hms.cc#L616).
> As of now, in attempt to run the {{kudu hms fix}} tool in the presence of
> such tables (e.g., {{db_name.table_name}} below), the tool reports an error:
> {noformat}
> sudo -u kudu kudu hms fix localhost --drop_orphan_hms_tables --force
> --ignore_other_clusters=false
> Remote error: failed to drop orphan HMS table db_name.table_name: failed to
> drop Hive Metastore table: TException - service has thrown:
> MetaException(message=Kudu table ID does not match the HMS entry)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
