sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-2334) Sqoop Volume Per Mapper
Date Tue, 30 Jun 2015 03:36:05 GMT

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

ASF subversion and git services commented on SQOOP-2334:

Commit e21529ac6aad03bdcb572c61420e258be2d823fe in sqoop's branch refs/heads/trunk from [~venkatnrangan]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=e21529a ]

SQOOP-2334:  Sqoop Volume Per Mapper
 (Rakesh Sharma via Venkat Ranganathan)

> 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
>         Attachments: SQOOP-2334.patch, SQOOP-2334_1.patch, SQOOP-2334_2.patch
> 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