sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh Sharma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-2334) Sqoop Volume Per Mapper
Date Thu, 21 May 2015 10:28:00 GMT

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

Rakesh Sharma commented on SQOOP-2334:
--------------------------------------

The new review request is created : https://reviews.apache.org/r/34536/
The patch is also uploaded there for review

> 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: VolumePerMapper.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
(v6.3.4#6332)

Mime
View raw message