hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
Date Tue, 16 Oct 2018 19:26:00 GMT


Hive QA commented on HIVE-20708:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 15085 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[repl_2_exim_basic] (batchId=84)

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
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.

ATTACHMENT ID: 12944081 - PreCommit-HIVE-Build

> Load (dumped) an external table as an external table on target with the same location
as on the source
> ------------------------------------------------------------------------------------------------------
>                 Key: HIVE-20708
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: repl
>            Reporter: Ashutosh Bapat
>            Assignee: Ashutosh Bapat
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-20708.01
> External tables are currently mapped to managed tables on target. A lot of jobs in user
environment are dependent upon locations specified in external table definitions to run, hence,
the path for external tables on the target and on the source are expected to be the same.
An external table being loaded as a  managed table makes it difficult for failover (Controlled
Failover) / failback since there is no option of moving data from managed to external table.
So the external table replicated to target cluster needs to be kept as external table with
same location as on the source.

This message was sent by Atlassian JIRA

View raw message