sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boglarka Egyed (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SQOOP-3332) Extend Documentation of --resilient flag and add warning message when detected
Date Thu, 28 Jun 2018 15:57:00 GMT

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

Boglarka Egyed resolved SQOOP-3332.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0

Thanks for improving our documentation [~fero]! Please don't forget to close the related Review
Request.

> Extend Documentation of --resilient flag and add warning message when detected
> ------------------------------------------------------------------------------
>
>                 Key: SQOOP-3332
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3332
>             Project: Sqoop
>          Issue Type: Task
>            Reporter: Fero Szabo
>            Assignee: Fero Szabo
>            Priority: Major
>             Fix For: 3.0.0
>
>
> The resilient flag can be used to trigger the retry mechanism in the SQL Server connector.
The documentation only tells that it can be used in export, however it can be used in import
as well.
> Also, the feature itself relies on the implicit assumption that the split-by column is
unique and sorted in ascending order. The users have to be warned about this limitation, at
the very least.



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

Mime
View raw message