[ 
https://issues.apache.org/jira/browse/HIVE-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017277#comment-13017277
 ] 

Ning Zhang commented on HIVE-2032:
----------------------------------

Thiruvel, HIVE-1820 (actually the subtask of it HIVE-1836) is not intended to 
define the database LOCATION. The database metastore schema already contains a 
LOCATION field, but it was not currently exposed through the CREATE DATABASE 
syntax. That's what HIVE-1537 is about to solve. HIVE-1836 is to introduce 
dbproperties of generic key-value pairs. The dbproperties can be 
used/interpreted by application-level pre-execution hooks. We currently do not 
require the warehouse.dir (if it is one of the keys) must be consistent with 
the LOCATION field, and I think probably we don't need to keep 2 piece of 
information with the same semantics. 

If you want to change the database location URL I think probably a better way 
is to change the CREATE DATABASE syntax to add location (HIVE-1537) and any 
table created under that database should honor the database location property. 
What do you think?


> create database does not honour warehouse.dir in dbproperties
> -------------------------------------------------------------
>
>                 Key: HIVE-2032
>                 URL: https://issues.apache.org/jira/browse/HIVE-2032
>             Project: Hive
>          Issue Type: Bug
>          Components: Clients
>    Affects Versions: 0.7.0, 0.8.0
>            Reporter: Thiruvel Thirumoolan
>            Assignee: Thiruvel Thirumoolan
>             Fix For: 0.8.0
>
>         Attachments: DatabaseLocation.patch
>
>
> # create database db with dbproperties ('hive.metastore.warehouse.dir' = 
> 'loc');
> The above command does not set location of 'db' to 'loc'. It instead creates 
> 'db.db' under the warehouse directory configured in hive-site.xml of CLI. 
> Looks conflicting with HIVE-1820's expectation. If scratch dir is specified 
> here, that is honoured.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to