hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-6374) Hive job submitted with non-default name node ( doesn't process locations properly
Date Sun, 04 May 2014 22:53:15 GMT


Hive QA commented on HIVE-6374:

{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 6 failed/errored test(s), 5496 tests executed
*Failed tests:*

Test results:
Console output:

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: 6 tests failed

This message is automatically generated.


> Hive job submitted with non-default name node ( doesn't process locations
> ---------------------------------------------------------------------------------------------------
>                 Key: HIVE-6374
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 0.11.0, 0.12.0, 0.13.0
>         Environment: Any
>            Reporter: Benjamin Zhitomirsky
>            Assignee: Benjamin Zhitomirsky
>         Attachments: Design of the fix HIVE-6374.docx, hive-6374.1.patch, hive-6374.3.patch,
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> Create table/index/database and add partition DDL doesn't work properly if all following
conditions are true:
> - Metastore service is used
> - is specified and it differs from the default one
> - Location is not specified or specified as a not fully qualified URI
> The root cause of this behavior is that Hive client doesn't pass configuration context
to the metastore services which tries to resolve the paths. The fix is it too resolve the
path in the Hive client if is specified and it differs from the default one
(it is must easier then start passing the context, which would be a major change).
> The CR will submitted shortly after tests are done

This message was sent by Atlassian JIRA

View raw message