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

Jarek Jarcec Cecho commented on SQOOP-1631:
-------------------------------------------

The last patch looks good to me [~yamaguchimsf]. You're right that we need to 
also update the [user 
documentation|https://github.com/apache/sqoop/blob/trunk/src/docs/user/connectors.txt#L289]
 that is located in {{src/doc/user/connectors.txt}} file. You can build the 
documentation with command {{ant docs}}.

> 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, 
> SQOOP-1631_3.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)

Reply via email to