sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fero Szabo (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-3333) Change default behavior of the MS SQL connector to non-resilient.
Date Wed, 20 Jun 2018 11:28:00 GMT

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

Fero Szabo updated SQOOP-3333:
------------------------------
    Attachment: SQOOP-3333-11.patch

> Change default behavior of the MS SQL connector to non-resilient.
> -----------------------------------------------------------------
>
>                 Key: SQOOP-3333
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3333
>             Project: Sqoop
>          Issue Type: Task
>            Reporter: Fero Szabo
>            Assignee: Fero Szabo
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: SQOOP-3333-11.patch
>
>
> The default behavior of Sqoop is to use a "resilient" retry mechanism in the SQL Server
connector. However, this relies on the split-by column being unique and ordered ascending.
This can lead to obscure errors (duplicate or missing records in imports / exports) and should
be used only if specifically wanted by the users.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message