[
https://issues.apache.org/jira/browse/SQOOP-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098232#comment-13098232
]
[email protected] commented on SQOOP-327:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1717/
-----------------------------------------------------------
(Updated 2011-09-06 18:05:26.902743)
Review request for Sqoop, Ahmed Radwan, Arvind Prabhakar, and jmhsieh.
Summary
-------
A new option is introduced to allow update records if they exist in table
already or to insert records if they do not exist yet.
This addresses bug SQOOP-327.
https://issues.apache.org/jira/browse/SQOOP-327
Diffs (updated)
-----
src/test/com/cloudera/sqoop/manager/OracleExportTest.java 12858d7
src/java/com/cloudera/sqoop/mapreduce/UpdateOutputFormat.java d5339d9
src/java/com/cloudera/sqoop/tool/BaseSqoopTool.java 879c7c8
src/java/com/cloudera/sqoop/tool/ExportTool.java d156eeb
src/java/com/cloudera/sqoop/mapreduce/OracleUpsertOutputFormat.java
PRE-CREATION
src/java/com/cloudera/sqoop/manager/OracleManager.java 1d08c4d
src/java/com/cloudera/sqoop/mapreduce/JdbcUpsertExportJob.java PRE-CREATION
src/java/com/cloudera/sqoop/SqoopOptions.java d07aecc
src/java/com/cloudera/sqoop/manager/ConnManager.java f5f5a4b
src/docs/man/sqoop-export.txt 50052cc
src/docs/user/export.txt 4401c26
Diff: https://reviews.apache.org/r/1717/diff
Testing
-------
Thanks,
Bilung
> Mixed update/insert export support for OracleManager
> ----------------------------------------------------
>
> Key: SQOOP-327
> URL: https://issues.apache.org/jira/browse/SQOOP-327
> Project: Sqoop
> Issue Type: New Feature
> Reporter: Bilung Lee
> Assignee: Bilung Lee
>
> Currently Sqoop export job runs in insert mode (default) or update mode (with
> --update-key option). When in insert mode, all data are inserted and when in
> update mode, all data are updated in existing table. This leaves out the use
> case where some data may need to be updated while the rest needs to be
> inserted.
> It also causes problems
> - When in insert mode, new data may cause constraint violations if they exist
> already.
> - When in update mode, it could result in silent dropping of records that do
> not match the update key.
> The idea is to introduce a new "upsert" mode to update records if they exist
> in table already or to insert records if they do not exist yet.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
