[
https://issues.apache.org/jira/browse/IMPALA-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853445#comment-16853445
]
Todd Lipcon commented on IMPALA-8459:
-------------------------------------
One possibility for a workaround: could you alter the storage engine of the
table to be non-kudu before dropping? We may prevent ALTER from changing the
storage handler, but if not, it's a thought.
Another idea (though not a very nice one) is to use the Kudu client to recreate
the table (with arbitrary schema and no contents) and then drop it via Impala?
eg 'kudu perf loadgen -table_name=impala::foo.bar --keep_auto_table' is an easy
way to create a small table from the CLI.
> Cannot delete impala/kudu table if backing kudu table dropped with local
> catalog
> --------------------------------------------------------------------------------
>
> Key: IMPALA-8459
> URL: https://issues.apache.org/jira/browse/IMPALA-8459
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 3.3.0
> Reporter: Tim Armstrong
> Assignee: Todd Lipcon
> Priority: Critical
> Labels: kudu
>
> test_delete_external_kudu_table and test_delete_managed_kudu_table fail with
> local catalog, e.g. with:
> {noformat}
> E HiveServer2Error: LocalCatalogException: Error opening Kudu table
> 'testimpalakuduintegration_1715_p3r46w.ogslbjblgv', Kudu error: the table
> does not exist: table_name: "testimpalakuduintegration_1715_p3r46w.ogslbjblgv"
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
