[
https://issues.apache.org/jira/browse/HIVE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904388#action_12904388
]
Carl Steinbach commented on HIVE-675:
-------------------------------------
I removed these methods since they implicitly target the {{default}} database.
I can put them
back with a deprecation warning, but I also want to point out that old code
that depends on
these methods is probably no longer correct now that Hive supports multiple
databases.
Removing these methods entirely may be the easiest way to help people find
these errors.
> 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.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-08-16.patch.txt,
> HIVE-675-2010-7-16.patch.txt, HIVE-675-2010-8-4.patch.txt,
> HIVE-675.10.patch.txt, HIVE-675.11.patch.txt, HIVE-675.12.patch.txt,
> HIVE-675.13.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.
