[
https://issues.apache.org/jira/browse/SQOOP-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248484#comment-14248484
]
ASF subversion and git services commented on SQOOP-1631:
--------------------------------------------------------
Commit 412bc4fd8c5ad74ab97c63666b37894a0af93696 in sqoop's branch
refs/heads/trunk from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=412bc4f ]
SQOOP-1631: Drop confusing use of --clean-staging-table parameter from
PGBulkloadManager
(Masahiro Yamaguchi via Jarek Jarcec Cecho)
> 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)
