hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-8719) LoadSemanticAnalyzer ignores previous partition location if inserting into partition that already exists
Date Wed, 05 Nov 2014 04:07:34 GMT

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

Hive QA commented on HIVE-8719:
-------------------------------



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

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

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

Test results: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1636/testReport
Console output: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/1636/console
Test logs: http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-1636/

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: 12679129 - PreCommit-HIVE-TRUNK-Build

> LoadSemanticAnalyzer ignores previous partition location if inserting into partition
that already exists
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-8719
>                 URL: https://issues.apache.org/jira/browse/HIVE-8719
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.14.0
>            Reporter: Sushanth Sowmyan
>            Assignee: Sushanth Sowmyan
>         Attachments: HIVE-8719.patch
>
>
> LOAD DATA INSERT INTO seems to be broken currently for partitions that do not use hive's
native directory structure naming scheme, thus ignoring any location previously set by an
ALTER TABLE ADD PARTITION ... LOCATION ... command.
> Here is a simple reproducer:
> {noformat}
> echo 1 > /tmp/data1.txt
> hive -e "create external table testpart(id int) partitioned by (date string) location
'/tmp/testpart';"
> hive -e "alter table testpart add partition(date='2014-09-16')  location '/tmp/testpart/20140916';"
> hive -e "describe formatted testpart partition(date='2014-09-16') ;" | egrep '/tmp/testpart/(date=.?)?2014-?09-?16'
> /tmp/a
> hive -e "load data local inpath '/tmp/data1.txt' into table testpart partition(date='2014-09-16');"
> hive -e "describe formatted testpart partition(date='2014-09-16') ;" | egrep '/tmp/testpart/(date=.?)?2014-?09-?16'
> /tmp/b
> diff /tmp/a /tmp/b
> hadoop fs -ls /tmp/testpart/
> {noformat}
> Basically, what happens is that after the ALTER TABLE ADD PARTITION ... LOCATION, the
location is "/tmp/testpart/20140916". After the LOAD DATA has run, the partition location
becomes "/tmp/testpart/date=2014-09-16/". Any data previously present in the other location
will then be ignored as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message