[
https://issues.apache.org/jira/browse/SQOOP-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arvind Prabhakar updated SQOOP-327:
-----------------------------------
Fix Version/s: 1.4.0-incubating
> 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
> Fix For: 1.4.0-incubating
>
> Attachments: SQOOP-327.diff
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
