[
https://issues.apache.org/jira/browse/IMPALA-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-6343:
----------------------------------
Priority: Major (was: Critical)
> 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: Major
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
