[
https://issues.apache.org/jira/browse/SQOOP-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047010#comment-14047010
]
Hudson commented on SQOOP-1341:
-------------------------------
SUCCESS: Integrated in Sqoop-ant-jdk-1.6-hadoop200 #894 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop200/894/])
SQOOP-1341: Sqoop Export Upsert for MySQL lacks batch support (jarcec:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=d03faf3544b1ef07c9496fa7641ed6a42f58cb1d)
* src/java/org/apache/sqoop/mapreduce/mysql/MySQLUpsertOutputFormat.java
> Sqoop Export Upsert for MySQL lacks batch support
> -------------------------------------------------
>
> Key: SQOOP-1341
> URL: https://issues.apache.org/jira/browse/SQOOP-1341
> Project: Sqoop
> Issue Type: Improvement
> Components: connectors/mysql
> Affects Versions: 1.4.4
> Reporter: Andy Skelton
> Assignee: Andy Skelton
> Labels: easyfix, newbie, patch
> Fix For: 1.4.5
>
> Attachments: SQOOP-1341.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> MySQL export upserts are limited to one row per statement. This wastes
> bandwidth and makes the exports unusably slow.
> I wrote a patch to support multiple rows per statement at
> (https://github.com/cloudera/sqoop/pull/22/files). Now the
> records.per.statement parameter actually works, and I get fast exports (60k
> rows/sec) with 1000 records per statement, 10 statements per transactions,
> and 5 mappers.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
