[
https://issues.apache.org/jira/browse/IMPALA-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648729#comment-17648729
]
Michael Smith commented on IMPALA-1818:
---------------------------------------
HMS will refuse a rename into a location that already exists (including an
empty table). And you can't set a policy on a location that doesn't exist, and
policy is removed when the location is deleted. So I'm unable to reproduce this
issue.
> ALTER TABLE RENAME fails between different HDFS encryption zones
> ----------------------------------------------------------------
>
> Key: IMPALA-1818
> URL: https://issues.apache.org/jira/browse/IMPALA-1818
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 2.0
> Reporter: Matthew Jacobs
> Priority: Minor
> Labels: security, usability
>
> ALTER TABLE RENAME fails if the original table directory is in a different
> HDFS encryption zone than the parent directory, i.e. the Hive warehouse dir.
> (Note RENAME only applies to managed tables.)
> This is somewhat of a corner case because it requires that a managed table be
> created in Impala/Hive and, before any data is inserted, it be added as an
> HDFS encryption zone (because encryption zones must be configured on empty
> directories). This does not apply to external tables which use ALTER TABLE
> ... SET LOCATION.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
