sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Masahiro Yamaguchi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1631) Staging-table name check don't need using PGBulkloadManager
Date Sat, 06 Dec 2014 11:55:12 GMT

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

Masahiro Yamaguchi commented on SQOOP-1631:
-------------------------------------------

I forgot to write one premise, {{Jarek Jarcec Cecho}}.
We can do export without using {{--staging-table-name}} option, but I want to add {{--clear-staging-table}}
option to re-run when I export data from HDFS to Database. 
If Sqoop MapReduce job fail in some errors on map phase,  some staging-tables are not erased.
When using the {{--clear-staging-table}} option, {{--staging-table-name}} option has to be
set.
So I want to omit this check only in PGBulkloadManager.

> Staging-table name check don't need using PGBulkloadManager
> -----------------------------------------------------------
>
>                 Key: SQOOP-1631
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1631
>             Project: Sqoop
>          Issue Type: Bug
>          Components: connectors/postgresql
>    Affects Versions: 1.4.6
>            Reporter: Masahiro Yamaguchi
>         Attachments: SQOOP-1631_1.patch, SQOOP-1631_2.patch
>
>
> If we use PGBulkloadManager, the number of staging-tables  equals number of map tasks.
> And staging-table's name is decided as follows.
>   tmpTableName = table + "_" + context.getTaskAttemptID().toString();
> ExportTools check staging-table's name, but this check don't need using PGBulkloadManager.



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

Mime
View raw message