sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keegan Witt (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-1403) Upsert export for SQL Server
Date Tue, 05 Aug 2014 17:26:17 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Keegan Witt updated SQOOP-1403:

    Attachment: SQOOP_1403_non_func.patch

Yes, I know about {{OracleUpsertRecordWriter.getUpdateStatement()}}.  What I didn't understand
was how that method worked in conjunction with {{UpdateRecordWriter.getPreparedStatement()}}.
 That method wasn't overridden by {{OracleUpsertRecordWriter}}, and it seems to me the key
substitution would be in the wrong spot and no all the substitutions would be made.

I've attached a preliminary (and non-functional) patch.  Maybe you could point out where I
might have gone wrong?

> Upsert export for SQL Server
> ----------------------------
>                 Key: SQOOP-1403
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1403
>             Project: Sqoop
>          Issue Type: New Feature
>          Components: connectors/sqlserver
>            Reporter: Keegan Witt
>            Assignee: Keegan Witt
>         Attachments: SQOOP_1403_non_func.patch
> Same as has been done in SQOOP-327 and SQOOP-621 (and requested in SQOOP-1270), but for
SQL Server.

This message was sent by Atlassian JIRA

View raw message