You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Keegan Witt (JIRA)" <ji...@apache.org> on 2014/09/25 19:34:33 UTC

[jira] [Updated] (SQOOP-1403) Upsert export for SQL Server

     [ 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_2.patch

I added a SqlServerUpsertOutputFormatTest that tests that the SQL string is generated properly (and that test passes).  But are you talking about adding a case to SQLServerManagerExportManualTest?  I tried doing that, but I must not have had my environment configured properly because it just hung.  I attached what I tried to run, if it works for you, I'll go ahead and add it to review board.

> 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.patch, SQOOP-1403_2.patch, SQOOP-1403_non_func.patch, SQOOP-1403_with_conditional_upsert.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
(v6.3.4#6332)