sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jiraposter@reviews.apache.org (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-443) Calling sqoop with hive import is not working multiple times due to kept output directory
Date Thu, 19 Apr 2012 05:16:04 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257240#comment-13257240

jiraposter@reviews.apache.org commented on SQOOP-443:

This is an automatically generated e-mail. To reply, visit:

Review request for Sqoop, Arvind Prabhakar and Cheolsoo Park.


I've added code that is removing export directory in case that it's empty.

(Recreating review on moved SVN repository)

This addresses bug SQOOP-443.


Diff: https://reviews.apache.org/r/4798/diff


ant -Dhadoopversion={20, 23, 100} test
real testing environment based on CDH3



> Calling sqoop with hive import is not working multiple times due to  kept output directory
> ------------------------------------------------------------------------------------------
>                 Key: SQOOP-443
>                 URL: https://issues.apache.org/jira/browse/SQOOP-443
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.4.0-incubating, 1.4.1-incubating
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>            Priority: Minor
>         Attachments: SQOOP-443.patch
> Hive is not removing input directory when doing "LOAD DATA" command in all cases. This
input directory is actually sqoop's export directory. Because this directory is kept, calling
same sqoop command twice is failing on exception "org.apache.hadoop.mapred.FileAlreadyExistsException:
Output directory $table already exists".
> This issue might be easily overcome by manual directory removal, however it's putting
unnecessary burden on users. It's also complicating executing saved jobs as there is additional
script execution needed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message