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 2013/06/17 16:15:20 UTC
[jira] [Assigned] (SQOOP-1085) Support "INSERT IGNORE INTO"
statement in export job
[ https://issues.apache.org/jira/browse/SQOOP-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Jarcec Cecho reassigned SQOOP-1085:
-----------------------------------------
Assignee: David Quigley
Hi [~dquigley],
please go ahead with your proposal! I would suggest to add this option as a MySQL Connector extra argument to not mess standard sqoop arguments with connector specifics options.
Jarcec
> Support "INSERT IGNORE INTO" statement in export job
> ----------------------------------------------------
>
> Key: SQOOP-1085
> URL: https://issues.apache.org/jira/browse/SQOOP-1085
> Project: Sqoop
> Issue Type: New Feature
> Affects Versions: 1.4.3
> Environment: Linux hadoop-02 2.6.18-164.15.1.el5.centos.plusxen #1 SMP Wed Mar 17 20:32:20 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: David Quigley
> Assignee: David Quigley
> Labels: sqoop
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Currently sqoop export job does not support INSERT IGNORE INTO syntax/use case. "Upsert mode" https://issues.apache.org/jira/browse/SQOOP-327 handles INSERT INTO ON DUPLICATE KEY UPDATE syntax/use case. The new feature will allow exporting records while not updating existing keys. In the case of duplicate records, INSERT IGNORE INTO will result in faster running export.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira