hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-4064) Handle db qualified names consistently across all HiveQL statements
Date Fri, 01 Aug 2014 22:53:40 GMT


Hive QA commented on HIVE-4064:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 5847 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed

This message is automatically generated.


> Handle db qualified names consistently across all HiveQL statements
> -------------------------------------------------------------------
>                 Key: HIVE-4064
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message