[
https://issues.apache.org/jira/browse/SQOOP-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087976#comment-13087976
]
Hudson commented on SQOOP-314:
------------------------------
Integrated in Sqoop-jdk-1.6 #14 (See
[https://builds.apache.org/job/Sqoop-jdk-1.6/14/])
SQOOP-314. Support for batch insert.
(Bilung Lee via Arvind Prabhakar)
arvind : http://svn.apache.org/viewvc/?view=rev&rev=1159773
Files :
*
/incubator/sqoop/trunk/src/java/com/cloudera/sqoop/manager/SQLServerManager.java
*
/incubator/sqoop/trunk/src/java/com/cloudera/sqoop/mapreduce/ExportBatchOutputFormat.java
* /incubator/sqoop/trunk/src/java/com/cloudera/sqoop/SqoopOptions.java
* /incubator/sqoop/trunk/src/java/com/cloudera/sqoop/manager/OracleManager.java
*
/incubator/sqoop/trunk/src/java/com/cloudera/sqoop/mapreduce/ExportJobBase.java
*
/incubator/sqoop/trunk/src/java/com/cloudera/sqoop/mapreduce/ExportOutputFormat.java
* /incubator/sqoop/trunk/src/docs/user/export.txt
*
/incubator/sqoop/trunk/src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java
* /incubator/sqoop/trunk/src/docs/man/sqoop-export.txt
*
/incubator/sqoop/trunk/src/java/com/cloudera/sqoop/mapreduce/AsyncSqlRecordWriter.java
* /incubator/sqoop/trunk/src/java/com/cloudera/sqoop/tool/BaseSqoopTool.java
* /incubator/sqoop/trunk/src/java/com/cloudera/sqoop/tool/ExportTool.java
> Basic export hangs when target database does not support INSERT syntax with
> multiple rows of values
> ---------------------------------------------------------------------------------------------------
>
> Key: SQOOP-314
> URL: https://issues.apache.org/jira/browse/SQOOP-314
> Project: Sqoop
> Issue Type: Bug
> Reporter: Bilung Lee
> Assignee: Bilung Lee
> Fix For: 1.4.0
>
> Attachments: SQOOP-314.diff
>
>
> Basic export job will hang when the target database does not support INSERT
> syntax with multiple rows of values, such as INSERT INTO tbl (col1, col2)
> VALUES(11, 12),(21, 22),(23, 24)
> This is because, in close(), AsyncSqlRecordWriter will still wait for
> AsyncSqlExecThread to finish even when an SQLException is thrown underneath.
> The configuration variable "sqoop.export.records.per.statement" can be set to
> 1 as a workaround for this problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
