[
https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897275#action_12897275
]
HBase Review Board commented on HIVE-675:
-----------------------------------------
Message from: "namit jain" <[email protected]>
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.cloudera.org/r/508/#review838
-----------------------------------------------------------
metastore/if/hive_metastore.thrift
<http://review.cloudera.org/r/508/#comment2816>
Same as John's earlier comment - do we need
to change the name.
No-one is using this table in the metastore currently,
so it might be OK - but not sure, how JDO would
handle renaming a column
ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g
<http://review.cloudera.org/r/508/#comment2817>
remove KW_SCHEMAS
ql/src/test/queries/clientpositive/database.q
<http://review.cloudera.org/r/508/#comment2818>
also add a test for 'show databases for a pattern'
- namit
> add database/schema support Hive QL
> -----------------------------------
>
> Key: HIVE-675
> URL: https://issues.apache.org/jira/browse/HIVE-675
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Metastore, Query Processor
> Reporter: Prasad Chakka
> Assignee: Carl Steinbach
> Fix For: 0.6.0, 0.7.0
>
> Attachments: hive-675-2009-9-16.patch, hive-675-2009-9-19.patch,
> hive-675-2009-9-21.patch, hive-675-2009-9-23.patch, hive-675-2009-9-7.patch,
> hive-675-2009-9-8.patch, HIVE-675-2010-7-16.patch.txt,
> HIVE-675-2010-8-4.patch.txt
>
>
> 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.
