[
https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
He Yongqiang updated HIVE-675:
------------------------------
Attachment: hive-675-2009-9-21.patch
>>What is the reason for not using a default path (<hive.root>/dbname) if
>>location argument is null? It is possible that tools other than Hive CLI can
>>create databases and they don't necessarily know what is the default path
>>should be.
At the first try of implementing this feature, i thought it's not a good idea
to host other database in the default db's directory (i did not know that the
default db can not be drop at that time). So hive-675-2009-9-21.patch removed
the constrain of must specifying a location.
And also added "create database" testcase in positive cli test as Namit
suggested in an earlier comment.
Thanks Prasad and Namit!
> 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.
