sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-1631) Drop confusing use of --clean-staging-table parameter from PGBulkloadManager
Date Tue, 16 Dec 2014 17:01:13 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jarek Jarcec Cecho updated SQOOP-1631:
--------------------------------------
    Summary: Drop confusing use of --clean-staging-table parameter from PGBulkloadManager
 (was: Staging-table name check don't need using PGBulkloadManager)

> Drop confusing use of --clean-staging-table parameter from 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, SQOOP-1631_3.patch, SQOOP-1631_4.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