[
https://issues.apache.org/jira/browse/HIVE-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093713#comment-14093713
]
Lefty Leverenz commented on HIVE-4064:
--------------------------------------
Many thanks for this work, [~navis].
Could we please have a release note listing HiveQL statements that can take
database qualified names starting with this patch? (But more are expected with
HIVE-7681, so perhaps we should wait for that.)
> 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
> Labels: TODOC14
> Fix For: 0.14.0
>
> 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-4064.6.patch.txt, HIVE-4064.7.patch.txt,
> HIVE-4064.8.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)
