sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Atul Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-2334) Sqoop Volume Per Mapper
Date Mon, 18 May 2015 09:04:02 GMT

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

Atul Gupta updated SQOOP-2334:
    Assignee: Rakesh Sharma

> Sqoop Volume Per Mapper
> -----------------------
>                 Key: SQOOP-2334
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2334
>             Project: Sqoop
>          Issue Type: New Feature
>    Affects Versions: 1.4.5
>            Reporter: Atul Gupta
>            Assignee: Rakesh Sharma
>             Fix For: 1.4.7
> There is no way where user can define the upper limit of volume that each  mapper can
handle. Current Sqoop does the calculation based on mapper by Switch -m and --split-by but
this does not give control user to specify the upper limit of volume handle by the mapper
> if we can add such functionality in the Sqoop that would help us to load the bigger data
set in case we don't have continuous key data available and there is a huge gap in maximum
and minimum data set value. 

This message was sent by Atlassian JIRA

View raw message