hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5967) Sqoop should only use a single map task
Date Tue, 23 Jun 2009 19:54:07 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Tom White updated HADOOP-5967:

       Resolution: Fixed
    Fix Version/s: 0.21.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)


I've just committed this. Thanks Aaron!

> Sqoop should only use a single map task
> ---------------------------------------
>                 Key: HADOOP-5967
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5967
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Aaron Kimball
>            Assignee: Aaron Kimball
>            Priority: Minor
>             Fix For: 0.21.0
>         Attachments: single-mapper.patch
> The current DBInputFormat implementation uses SELECT ... LIMIT ... OFFSET statements
to read from a database table. This actually results in several queries all accessing the
same table at the same time. Most database implementations will actually use a full table
scan for each such query, starting at row 1 and scanning down until the OFFSET is reached
before emitting data to the client. The upshot of this is that we see O(n^2) performance in
the size of the table when using a large number of mappers, when a single mapper would read
through the table in O(n) time in the number of rows.
> This patch sets the number of map tasks to 1 in the MapReduce job sqoop launches.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message