You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "mahesh kumar behera (Jira)" <ji...@apache.org> on 2021/12/14 15:22:00 UTC

[jira] [Resolved] (HIVE-25778) Hive DB creation is failing when MANAGEDLOCATION is specified with existing location

     [ https://issues.apache.org/jira/browse/HIVE-25778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mahesh kumar behera resolved HIVE-25778.
----------------------------------------
    Resolution: Won't Fix

Closing this Jira as supporting this scenario may lead to data loss/corruption if user is not very careful. 

> Hive DB creation is failing when MANAGEDLOCATION is specified with existing location
> ------------------------------------------------------------------------------------
>
>                 Key: HIVE-25778
>                 URL: https://issues.apache.org/jira/browse/HIVE-25778
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2, Metastore
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> As part of HIVE-23387 check is added to restrict user from creating database with managed table location, if the location is already present. This was not the case. As this is causing backward compatibility issue, the check needs to be removed.
>  
> {code:java}
> if (madeManagedDir) {
>   LOG.info("Created database path in managed directory " + dbMgdPath);
> } else {
>   throw new MetaException(
>       "Unable to create database managed directory " + dbMgdPath + ", failed to create database " + db.getName());
> }  {code}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)