You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Masahiro Yamaguchi (JIRA)" <ji...@apache.org> on 2014/10/28 00:37:34 UTC
[jira] [Created] (SQOOP-1631) Staging-table name check don't need
using PGBulkloadManager
Masahiro Yamaguchi created SQOOP-1631:
-----------------------------------------
Summary: 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.5
Reporter: Masahiro Yamaguchi
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)