You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2014/06/29 01:44:25 UTC
[jira] [Assigned] (SQOOP-1341) Sqoop Export Upsert for MySQL lacks
batch support
[ https://issues.apache.org/jira/browse/SQOOP-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Jarcec Cecho reassigned SQOOP-1341:
-----------------------------------------
Assignee: Andy Skelton
> 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)