[
https://issues.apache.org/jira/browse/HIVE-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588626#comment-13588626
]
Jarek Jarcec Cecho commented on HIVE-4086:
------------------------------------------
Hi Todd,
thank you very much for reporting this issue. We already have JIRA HIVE-4064 to
track this requirement so I'm closing this one as a duplicate to keep all the
information in one place.
To immediately unblock you, did you consider using SQL query {{USE <dbname>}}
to change working database from {{default}} to {{<dbname>}}?
Jarcec
> Cross Database Support for Indexes and Partitions (or all DDL statements)
> -------------------------------------------------------------------------
>
> Key: HIVE-4086
> URL: https://issues.apache.org/jira/browse/HIVE-4086
> Project: Hive
> Issue Type: Improvement
> Components: Database/Schema, ODBC, SQL
> Affects Versions: 0.9.0
> Environment: Writing a query tool in .NET connecting with ODBC to
> Hadoop on Linux.
> Reporter: Todd Wilson
>
> I'd like to see more cross-database support. I'm using a Cloudera
> implementation on Hive .9. Currently, you can create new databases, you can
> create tables and views in those databases, but you cannot create indexes or
> partitions on those tables. Likewise, commands like show partitions or show
> indexes will only work on table in the default database. This would probably
> also affect statements like Alter Table and Recover Partitions. Probably
> also something like Create Function, but if you want to keep all functions
> being created in the default database that would work. I would be more
> interested in full cross-database support for tables and views to start.
> Functions for example could all be created in default. Thank you.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
