[
https://issues.apache.org/jira/browse/SQOOP-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038517#comment-17038517
]
punit gupta commented on SQOOP-1278:
------------------------------------
its 2020 and I am still getting the same error running sqoop 1.4.6 and fix
around this?
> Allow use of uncommitted isolation for databases that support it as an import
> option
> ------------------------------------------------------------------------------------
>
> Key: SQOOP-1278
> URL: https://issues.apache.org/jira/browse/SQOOP-1278
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.3, 1.4.4
> Environment: All DBs that support uncommitted read transaction
> isolation
> Reporter: Venkat Ranganathan
> Assignee: Venkat Ranganathan
> Priority: Major
> Fix For: 1.4.5
>
> Attachments: SQOOP-1278-3.diff, SQOOP-1278.diff
>
>
> Some customers might have ETL workflows that depend on data to be imported
> while the table is otherwise available for the regular data processing.
> The current read committed isolation can cause failure because of locking
> semantics used in the database systems used also.
> So, this is to provide a relaxation of the connection isolation used by the
> mappers to be read uncommitted using a sqoop option. Note that read
> uncommitted is not a valid option for Oracle so it is not supported with the
> database and will be ignored for Oracle
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
