You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2014/11/03 03:03:34 UTC
[jira] [Commented] (SQOOP-1125) Out of memory errors when number of
records to import < 0.5 * splitSize
[ https://issues.apache.org/jira/browse/SQOOP-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194177#comment-14194177 ]
Jarek Jarcec Cecho commented on SQOOP-1125:
-------------------------------------------
Looks good [~SaiKarthik]. Could you please merge both patch into single file, remove trailing whitespaces and upload it here? Also be careful when generating the final patch - the latest attached file doesn't seem to be fully valid:
{code}
jarcec@arlene sqoop % git apply SQOOP-1125.patch
SQOOP-1125.patch:17: trailing whitespace.
SQOOP-1125.patch:27: trailing whitespace.
SQOOP-1125.patch:48: trailing whitespace.
SQOOP-1125.patch:50: trailing whitespace.
fatal: corrupt patch at line 53
{code}
> Out of memory errors when number of records to import < 0.5 * splitSize
> -----------------------------------------------------------------------
>
> Key: SQOOP-1125
> URL: https://issues.apache.org/jira/browse/SQOOP-1125
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.3
> Reporter: Dave Kincaid
> Assignee: Sai Karthik Ganguru
> Priority: Critical
> Labels: newbie
> Attachments: SQOOP-1125.patch, Sqoop-1125.patch
>
>
> We are getting out of memory errors during import if the number of records to import is less than 0.5*splitSize (and is nonterminating decimal).
> For example, if the numSplits = 3, minVal = 100, maxVal = 101 then in BigDecimalSplitter.split() an extraordinary number of tiny values will be added to the splits List and run out of memory eventually.
> I also noticed that there are no tests for BigDecimalSplitter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)