[
https://issues.apache.org/jira/browse/SQOOP-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fero Szabo updated SQOOP-3332:
------------------------------
Description:
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.
was:
The non-resilient flag can be used to avoid 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.
> 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
>
> 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)
