You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2014/12/16 18:03:14 UTC
[jira] [Resolved] (SQOOP-1631) Drop confusing use of
--clean-staging-table parameter from PGBulkloadManager
[ https://issues.apache.org/jira/browse/SQOOP-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Jarcec Cecho resolved SQOOP-1631.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.4.6
Assignee: Masahiro Yamaguchi
Thank you for your contribution [~yamaguchimsf]!
> 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
> Assignee: Masahiro Yamaguchi
> Fix For: 1.4.6
>
> 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)