[
https://issues.apache.org/jira/browse/SQOOP-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877552#comment-13877552
]
Venkat Ranganathan commented on SQOOP-1270:
-------------------------------------------
[~harisekhon] - It is a good suggestion. This is something that can be
attempted, but what can be done now is that a user can create a
function/procedure with the needed body for a table - say <tablename>_upsert
and use the call export feature of sqoop to export data to Postgres by calling
the procedure (instead of inserting into table)
For example sqoop export --connect <url> --call <upsert proc> \
--export-dir /results/bar_data
> Sqoop PostgreSQL Export Upsert Functionality Request
> ----------------------------------------------------
>
> Key: SQOOP-1270
> URL: https://issues.apache.org/jira/browse/SQOOP-1270
> Project: Sqoop
> Issue Type: New Feature
> Components: connectors/postgresql
> Affects Versions: 1.4.3
> Environment: CDH 4.5
> Reporter: Hari Sekhon
>
> Hi,
> One of my Hadoop developers is trying to re-export to PostgreSQL but is
> hitting the following error:
> ERROR tool.ExportTool: Error during export: Mixed update/insert is not
> supported against the target database yet
> Could we please add upsert functionality to the PostgreSQL connector?
> Although Postgres doesn't have direct upsert functionality it's possible to
> construct SQL to handle this like so:
> http://www.postgresql.org/docs/current/static/plpgsql-control-structures.html#PLPGSQL-UPSERT-EXAMPLE
> A similar request to add upsert functionality for MySQL was addressed here:
> https://issues.apache.org/jira/browse/SQOOP-621
> Thanks
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
