[jira] Updated: (MAPREDUCE-876) Sqoop import of large tables can time out
[ 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] Updated: (MAPREDUCE-876) Sqoop import of large tables can time out
[ 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
[ 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
[ 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.
