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 "Thomas Tauber-Marshall (JIRA)" <ji...@apache.org> on 2018/10/25 20:32:00 UTC
[jira] [Assigned] (IMPALA-6343) Allow dropping of Kudu tables with
invalid master addresses
[ https://issues.apache.org/jira/browse/IMPALA-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Tauber-Marshall reassigned IMPALA-6343:
----------------------------------------------
Assignee: (was: Thomas Tauber-Marshall)
> Allow dropping of Kudu tables with invalid master addresses
> -----------------------------------------------------------
>
> Key: IMPALA-6343
> URL: https://issues.apache.org/jira/browse/IMPALA-6343
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Affects Versions: Impala 2.11.0
> Reporter: Thomas Tauber-Marshall
> Priority: Critical
> Labels: kudu
>
> Impala stores the master addresses for Kudu tables in the tables metadata. If the master addresses are wrong and there isn't a reachable master at them (eg. because the previous master failed) no operations can be performed on the table through Impala. This problem is tracked by IMPALA-5399
> The main workaround we recommend is to directly modify the underlying HMS database to change the master addresses, but this can be confusing/scary for users.
> We could improve the usability here by at least allowing such tables to be dropped. Users could then fix the situation entirely through Impala by dropping the affected tables and recreating them as external tables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org