[ 
https://issues.apache.org/jira/browse/SQOOP-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100787#comment-13100787
 ] 

Hudson commented on SQOOP-327:
------------------------------

Integrated in Sqoop-jdk-1.6 #21 (See 
[https://builds.apache.org/job/Sqoop-jdk-1.6/21/])
    SQOOP-327. Mixed update/insert export for Oracle.

(Bilung Lee via Arvind Prabhakar)

arvind : http://svn.apache.org/viewvc/?view=rev&rev=1166930
Files : 
* /incubator/sqoop/trunk/src/docs/man/sqoop-export.txt
* /incubator/sqoop/trunk/src/docs/user/export.txt
* /incubator/sqoop/trunk/src/java/com/cloudera/sqoop/SqoopOptions.java
* /incubator/sqoop/trunk/src/java/com/cloudera/sqoop/manager/ConnManager.java
* /incubator/sqoop/trunk/src/java/com/cloudera/sqoop/manager/OracleManager.java
* 
/incubator/sqoop/trunk/src/java/com/cloudera/sqoop/mapreduce/JdbcUpsertExportJob.java
* 
/incubator/sqoop/trunk/src/java/com/cloudera/sqoop/mapreduce/OracleUpsertOutputFormat.java
* 
/incubator/sqoop/trunk/src/java/com/cloudera/sqoop/mapreduce/UpdateOutputFormat.java
* /incubator/sqoop/trunk/src/java/com/cloudera/sqoop/tool/BaseSqoopTool.java
* /incubator/sqoop/trunk/src/java/com/cloudera/sqoop/tool/ExportTool.java
* 
/incubator/sqoop/trunk/src/test/com/cloudera/sqoop/manager/OracleExportTest.java


> 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
>         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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to