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

He Yongqiang commented on HIVE-675:
-----------------------------------

>>Do you want to check for the existence of the location while creating a 
>>database - do we want to throw an error if it already exists.
Currently, it will not throw any error if the database dir is already there. I 
think this is the same as creating table. And i always do "drop table" and 
"create table" stuff, and i can switch machines, and only need to redo the 
"create table ..." and the data is available. I think this is very useful.

>>in create_db_bad_location, can you throw a more meaningful error - location 
>>is bad or something like that 
Actually i already throw an exception with msg "Database location must be an 
absolute URI.". But i think the error msg "FAILED: Unknown exception : null" is 
not unique to this, and i think it has been reported somewhere in mailist or a 
jira page.

> add database/scheme support Hive QL
> -----------------------------------
>
>                 Key: HIVE-675
>                 URL: https://issues.apache.org/jira/browse/HIVE-675
>             Project: Hadoop Hive
>          Issue Type: New Feature
>          Components: Query Processor
>            Reporter: Prasad Chakka
>            Assignee: He Yongqiang
>         Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch, 
> hive-675-2009-9-21.patch, hive-675-2009-9-7.patch, hive-675-2009-9-8.patch
>
>
> Currently all Hive tables reside in single namespace (default). Hive should 
> support multiple namespaces (databases or schemas) such that users can create 
> tables in their specific namespaces. These name spaces can have different 
> warehouse directories (with a default naming scheme) and possibly different 
> properties.
> There is already some support for this in metastore but Hive query parser 
> should have this feature as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to