[
https://issues.apache.org/jira/browse/HIVE-22974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051277#comment-17051277
]
Naveen Gangam commented on HIVE-22974:
--------------------------------------
[~amagyar] The fix checks for location only at the creation and alteration of
the table. For metadata that is being upgraded, this check does not come into
play. We allow the location to be as-is, regardless of whether it is legal or
not.
The reason we are running into an issue is because of some post-processing to
relocate some tables during upgrade. We need to see if we can make a fix to
this processing to change the order of things, or performing some offline
metadata changes (HMS is offline), via metatool or something of that sort.
I dont believe this check should be optional in the translation layer. One of
the things we want to accomplish with this translation is to enforce
constraints on the metadata. Relaxing just this one check does not make much
sense to me.
Could you please investigate to see if anything could be changed in the
post-upgrade code to make this work? Thanks
> Metastore's table location check should be optional
> ---------------------------------------------------
>
> Key: HIVE-22974
> URL: https://issues.apache.org/jira/browse/HIVE-22974
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Reporter: Attila Magyar
> Assignee: Attila Magyar
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-22974.1.patch
>
>
> In HIVE-22189 a check was introduced to make sure managed and external tables
> are located at the proper space. This condition cannot be satisfied during an
> upgrade.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
