[
https://issues.apache.org/jira/browse/HIVE-22158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16972455#comment-16972455
]
Naveen Gangam commented on HIVE-22158:
--------------------------------------
Hi [~lirui]
The change to convert to external table is by-design. So this external table
behaves exactly like a managed table, table data gets dropped on drop table. In
your case, I believe the {{hive.metastore.warehouse.external.dir}} /
{{metastore.warehouse.external.dir}} is not set in your configuration. This
causes one of the APIs to return a default location to be within the
warehouse.dir for external tables. So this should be a bug in this API to not
use the warehouse.dir as default for external tables.
To resolve this, please set the warehouse.external.dir to a location OUTSIDE
the warehouse.dir. Let me know if that works for you. THanks
> HMS Translation layer - Disallow non-ACID MANAGED tables.
> ---------------------------------------------------------
>
> Key: HIVE-22158
> URL: https://issues.apache.org/jira/browse/HIVE-22158
> Project: Hive
> Issue Type: Sub-task
> Components: Hive
> Affects Versions: 4.0.0
> Reporter: Naveen Gangam
> Assignee: Naveen Gangam
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-22158.1.patch, HIVE-22158.1.patch,
> HIVE-22158.2.patch
>
>
> In the recent commits, we have allowed non-ACID MANAGED tables to be created
> by clients that have some form of ACID WRITE capabilities.
> I think it would make sense to disallow this entirely. MANAGED tables should
> be ACID tables only.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
