[
https://issues.apache.org/jira/browse/HIVE-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086043#comment-14086043
]
Chun Chen commented on HIVE-4064:
---------------------------------
[~navis] It seems the patch doesn't cover "alter db.table rename to
db2.table2"? I think rename table across database is very useful for back up
tables. For example, we can create a database named backup. Each time we want
to backup a table, we could simply rename the table from its current db to the
backup db.
> Handle db qualified names consistently across all HiveQL statements
> -------------------------------------------------------------------
>
> Key: HIVE-4064
> URL: https://issues.apache.org/jira/browse/HIVE-4064
> Project: Hive
> Issue Type: Bug
> Components: SQL
> Affects Versions: 0.10.0
> Reporter: Shreepadma Venugopalan
> Assignee: Navis
> Attachments: HIVE-4064-1.patch, HIVE-4064.1.patch.txt,
> HIVE-4064.2.patch.txt, HIVE-4064.3.patch.txt, HIVE-4064.4.patch.txt,
> HIVE-4064.5.patch.txt
>
>
> Hive doesn't consistently handle db qualified names across all HiveQL
> statements. While some HiveQL statements such as SELECT support DB qualified
> names, other such as CREATE INDEX doesn't.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
