You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Thomas Tauber-Marshall (JIRA)" <ji...@apache.org> on 2017/12/19 00:22:00 UTC

[jira] [Created] (IMPALA-6343) Allow dropping of Kudu tables with invalid master addresses

Thomas Tauber-Marshall created IMPALA-6343:
----------------------------------------------

             Summary: 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
            Assignee: Thomas Tauber-Marshall
            Priority: Critical


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
(v6.4.14#64029)