[ 
https://issues.apache.org/jira/browse/HIVE-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875344#comment-13875344
 ] 

Hive QA commented on HIVE-6209:
-------------------------------



{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12623703/HIVE-6209.patch

{color:green}SUCCESS:{color} +1 4940 tests passed

Test results: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/950/testReport
Console output: 
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/950/console

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12623703

> 'LOAD DATA INPATH ... OVERWRITE ..' doesn't overwrite current data
> ------------------------------------------------------------------
>
>                 Key: HIVE-6209
>                 URL: https://issues.apache.org/jira/browse/HIVE-6209
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>            Reporter: Szehon Ho
>            Assignee: Szehon Ho
>         Attachments: HIVE-6209.patch
>
>
> In case where user loads data into table using overwrite, using a different 
> file, it is not being overwritten.
> {code}
> $ hdfs dfs -cat /tmp/data
> aaa
> bbb
> ccc
> $ hdfs dfs -cat /tmp/data2
> ddd
> eee
> fff
> $ hive
> hive> create table test (id string); 
> hive> load data inpath '/tmp/data' overwrite into table test;
> hive> select * from test;
> aaa
> bbb
> ccc
> hive> load data inpath '/tmp/data2' overwrite into table test;
> hive> select * from test;
> aaa
> bbb
> ccc
> ddd
> eee
> fff
> {code}
> It seems it is broken by HIVE-3756 which added another condition to whether 
> "rmr" should be run on old directory, and skips in this case.
> There is a workaround of set fs.hdfs.impl.disable.cache=true; 
> which sabotages this condition, but this condition should be removed in 
> long-term.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to