Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.4.5
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- links to
This is the patch created using git diff and contains all the changes required for Volume per mapper changes.