Issue Details (XML | Word | Printable)

Key: HADOOP-5844
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Aaron Kimball
Reporter: Aaron Kimball
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Hadoop Common

Use mysqldump when connecting to local mysql instance in Sqoop

Created: 15/May/09 12:45 AM   Updated: 11/Jun/09 07:59 PM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: 0.21.0

Time Tracking:
Not Specified

File Attachments:
  Size
Text File Licensed for inclusion in ASF works mysqldump.patch 2009-05-15 12:45 AM Aaron Kimball 25 kB
Issue Links:
Dependants
 

Hadoop Flags: Reviewed
Resolution Date: 03/Jun/09 10:28 AM


 Description  « Hide
Sqoop uses MapReduce + DBInputFormat to read the contents of a table into HDFS. On many databases, this implementation is O(N^2) in the number of rows. Also, the use of multiple mappers has low value in terms of throughput, because the database itself is inherently singlethreaded. While DBInputFormat/JDBC provides a useful fallback mechanism for importing from databases, db-specific dump utilities will nearly always provide faster throughput, and should be selected when available. This patch allows users to use mysqldump to read from local mysql instances instead of the MapReduce-based input.

If you provide sqoop with arguments of the form " --connect jdbc:mysql://localhost/somedatabase --local", it will use the mysqldump fast path to perform the import.

This patch, naturally, requires that MySQL be installed on a machine to test it. Thus the test that this adds is called LocalMySQLTest (instead of the Hadoop-preferred file naming, TestLocalMySQL) so that Hudson doesn't automatically run it. You can run this test yourself by using "ant -Dtestcase=LocalMySQLTest test". See the notes in the javadoc for the LocalMySQLTest class in how to set up the MySQL test environment for this.



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Aaron Kimball added a comment - 15/May/09 12:45 AM
Attached initial implementation.

Hadoop QA added a comment - 19/May/09 02:30 AM
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12408205/mysqldump.patch
against trunk revision 776148.

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 5 new or modified tests.

-1 patch. The patch command could not apply the patch.

Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/351/console

This message is automatically generated.


Aaron Kimball added a comment - 26/May/09 05:39 PM
Cycling the patch status now that 5815 is in to actually test this

Aaron Kimball added a comment - 26/May/09 05:50 PM
As a side note, this patch fixes a bug in HADOOP-5815 wherein sqoop did not add sqoop.jar itself to the classpath to pass to javac. As a result, compilation of generated code only worked in unit test mode (which made direct references to the .class files in the build directory), or when sqoop.jar was present in $HADOOP_HOME/lib/ (the contents of which were passed to javac).

With this patch, generated code compilation works regardless of the location of sqoop.jar.


Hadoop QA added a comment - 28/May/09 09:00 PM
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12408205/mysqldump.patch
against trunk revision 779656.

+1 @author. The patch does not contain any @author tags.

+1 tests included. The patch appears to include 5 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 Eclipse classpath. The patch retains Eclipse classpath integrity.

+1 release audit. The applied patch does not increase the total number of release audit warnings.

+1 core tests. The patch passed core unit tests.

-1 contrib tests. The patch failed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/419/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/419/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/419/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/419/console

This message is automatically generated.


Aaron Kimball added a comment - 28/May/09 09:11 PM
The contrib test failure is unrelated.

Tom White added a comment - 02/Jun/09 08:27 PM
+1 Looks good.

Tom White added a comment - 03/Jun/09 10:28 AM
I've just committed this. Thanks Aaron!

Hudson added a comment - 11/Jun/09 07:59 PM