[
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-19.patch
A new patch integrates Namit's comments (Thanks Namit!).
>>1. No positive test for CREATE DATEBASE
CREATE DATEBASE needs an absolute uri argument. So i guess hive cannot get such
an uri at testing.
>>3. More positive tests - the test that you mentioned in the beginning -
>>insert into db2 while selecting from db1 -
This also needs an file system location argument.
>>4. database_test.q and database_switch_test.q seem to be the same.
This is bad mistake i made. I intend to rename database_test.q to
database_switch_test.q, but forget to delete the old one.
>>2. Instead of having a separate processor, it might be a good idea to support
>>'use database' in Hive.g - in general, we are trying to add everything to
>>Hive.g, since it will make adding different clients easy.
moved it from processor to hive.g
will open several follow up for this jira.
1. move table from one database to another
2. support ' show databases';
3. support mutilpe databse support in HWI
4.
bq. this current path does not support <DBNAME>.<TBLNAME>.<COLUMN>. If you are
not planning to add that support then create a new JIRA.
5. moving SessionState from ql to common (from Prasad)
please add more.
> 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-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.
