[ https://issues.apache.org/jira/browse/MAPREDUCE-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727224#action_12727224 ]
Hadoop QA commented on MAPREDUCE-685: ------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12412298/MAPREDUCE-685.patch.2 against trunk revision 790971. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. -1 contrib tests. The patch failed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/354/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/354/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/354/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/354/console This message is automatically generated. > Sqoop will fail with OutOfMemory on large tables using mysql > ------------------------------------------------------------ > > Key: MAPREDUCE-685 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-685 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: contrib/sqoop > Reporter: Aaron Kimball > Assignee: Aaron Kimball > Attachments: MAPREDUCE-685.patch, MAPREDUCE-685.patch.2 > > > The default MySQL JDBC client behavior is to buffer the entire ResultSet in > the client before allowing the user to use the ResultSet object. On large > SELECTs, this can cause OutOfMemory exceptions, even when the client intends > to close the ResultSet after reading only a few rows. The MySQL ConnManager > should configure its connection to use row-at-a-time delivery of results to > the client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.