You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Aaron Kimball (JIRA)" <ji...@apache.org> on 2009/08/15 01:13:14 UTC
[jira] Created: (MAPREDUCE-876) Sqoop import of large tables can
time out
Sqoop import of large tables can time out
-----------------------------------------
Key: MAPREDUCE-876
URL: https://issues.apache.org/jira/browse/MAPREDUCE-876
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: contrib/sqoop
Reporter: Aaron Kimball
Assignee: Aaron Kimball
Related to MAPREDUCE-875, Sqoop should use a background thread to ensure that progress is being reported while a database does external work for the MapReduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-876) Sqoop import of large tables can
time out
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743561#action_12743561 ]
Hadoop QA commented on MAPREDUCE-876:
-------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12416630/MAPREDUCE-876.2.patch
against trunk revision 804284.
+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 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/478/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/478/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/478/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/478/console
This message is automatically generated.
> Sqoop import of large tables can time out
> -----------------------------------------
>
> Key: MAPREDUCE-876
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-876
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-876.2.patch, MAPREDUCE-876.patch
>
>
> Related to MAPREDUCE-875, Sqoop should use a background thread to ensure that progress is being reported while a database does external work for the MapReduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-876) Sqoop import of large tables can
time out
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated MAPREDUCE-876:
--------------------------------
Resolution: Fixed
Fix Version/s: 0.21.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
+1
I've just committed this. Thanks Aaron!
> Sqoop import of large tables can time out
> -----------------------------------------
>
> Key: MAPREDUCE-876
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-876
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-876.2.patch, MAPREDUCE-876.patch
>
>
> Related to MAPREDUCE-875, Sqoop should use a background thread to ensure that progress is being reported while a database does external work for the MapReduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-876) Sqoop import of large tables can
time out
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752124#action_12752124 ]
Hudson commented on MAPREDUCE-876:
----------------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #19 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk-Commit/19/])
. Sqoop import of large tables can time out. Contributed by Aaron Kimball.
> Sqoop import of large tables can time out
> -----------------------------------------
>
> Key: MAPREDUCE-876
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-876
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-876.2.patch, MAPREDUCE-876.patch
>
>
> Related to MAPREDUCE-875, Sqoop should use a background thread to ensure that progress is being reported while a database does external work for the MapReduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-876) Sqoop import of large tables can
time out
Posted by "Aaron Kimball (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Kimball updated MAPREDUCE-876:
------------------------------------
Status: Patch Available (was: Open)
> Sqoop import of large tables can time out
> -----------------------------------------
>
> Key: MAPREDUCE-876
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-876
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-876.patch
>
>
> Related to MAPREDUCE-875, Sqoop should use a background thread to ensure that progress is being reported while a database does external work for the MapReduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-876) Sqoop import of large tables can
time out
Posted by "Aaron Kimball (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Kimball updated MAPREDUCE-876:
------------------------------------
Attachment: MAPREDUCE-876.patch
Attaching patch containing AutoProgressMapRunner class. The ImportJob process now uses this MapRunner. Also includes tests. I further tested this by running a JDBC-based import of 2 GB of data which took 12 minutes.
> Sqoop import of large tables can time out
> -----------------------------------------
>
> Key: MAPREDUCE-876
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-876
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-876.patch
>
>
> Related to MAPREDUCE-875, Sqoop should use a background thread to ensure that progress is being reported while a database does external work for the MapReduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-876) Sqoop import of large tables can
time out
Posted by "Aaron Kimball (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Kimball updated MAPREDUCE-876:
------------------------------------
Attachment: MAPREDUCE-876.2.patch
Found a bug in the tests; attaching fixed patch
> Sqoop import of large tables can time out
> -----------------------------------------
>
> Key: MAPREDUCE-876
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-876
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-876.2.patch, MAPREDUCE-876.patch
>
>
> Related to MAPREDUCE-875, Sqoop should use a background thread to ensure that progress is being reported while a database does external work for the MapReduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MAPREDUCE-876) Sqoop import of large tables can
time out
Posted by "Aaron Kimball (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745139#action_12745139 ]
Aaron Kimball commented on MAPREDUCE-876:
-----------------------------------------
Failures are in capacity scheduler and streaming; unrelated.
> Sqoop import of large tables can time out
> -----------------------------------------
>
> Key: MAPREDUCE-876
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-876
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-876.2.patch, MAPREDUCE-876.patch
>
>
> Related to MAPREDUCE-875, Sqoop should use a background thread to ensure that progress is being reported while a database does external work for the MapReduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-876) Sqoop import of large tables can
time out
Posted by "Aaron Kimball (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Kimball updated MAPREDUCE-876:
------------------------------------
Status: Open (was: Patch Available)
> Sqoop import of large tables can time out
> -----------------------------------------
>
> Key: MAPREDUCE-876
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-876
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-876.2.patch, MAPREDUCE-876.patch
>
>
> Related to MAPREDUCE-875, Sqoop should use a background thread to ensure that progress is being reported while a database does external work for the MapReduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-876) Sqoop import of large tables can
time out
Posted by "Aaron Kimball (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron Kimball updated MAPREDUCE-876:
------------------------------------
Status: Patch Available (was: Open)
> Sqoop import of large tables can time out
> -----------------------------------------
>
> Key: MAPREDUCE-876
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-876
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/sqoop
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-876.2.patch, MAPREDUCE-876.patch
>
>
> Related to MAPREDUCE-875, Sqoop should use a background thread to ensure that progress is being reported while a database does external work for the MapReduce task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.