[
https://issues.apache.org/jira/browse/SQOOP-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237192#comment-14237192
]
Jarek Jarcec Cecho commented on SQOOP-1631:
-------------------------------------------
Got it [~yamaguchimsf]. The parameter {{\-\-staging\-table\-name}} is not used
in PGBulkload connector, but {{\-\-clear\-staging\-table}} is and using this
parameter also requires to enter {{\-\-staging\-table\-name}} per our usual
validations.
> 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)
