You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Aaron Kimball (JIRA)" <ji...@apache.org> on 2010/05/03 20:42:01 UTC
[jira] Resolved: (MAPREDUCE-1473) Sqoop should allow users to
control export parallelism
[ https://issues.apache.org/jira/browse/MAPREDUCE-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Kimball resolved MAPREDUCE-1473.
--------------------------------------
Resolution: Won't Fix
This is part of Sqoop which has been removed from the MapReduce project.
> Sqoop should allow users to control export parallelism
> ------------------------------------------------------
>
> Key: MAPREDUCE-1473
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1473
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-1473.2.patch, MAPREDUCE-1473.patch
>
>
> Sqoop uses MapReduce jobs to export files back to a table in the database. The degree of parallelism is controlled by the number of splits; i.e., the number of input files used. The bottleneck in the system, though, is likely to be the database itself.
> Users should have the ability to tune the number of parallel exporters being used to a degree appropriate to their database deployment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.