You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/02/04 22:04:09 UTC

[jira] [Commented] (SQOOP-1278) Allow use of uncommitted isolation for databases that support it as an import option

    [ https://issues.apache.org/jira/browse/SQOOP-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891199#comment-13891199 ] 

ASF subversion and git services commented on SQOOP-1278:
--------------------------------------------------------

Commit d3758915bb8b265ec157cd4bc21a7e17d922458e in branch refs/heads/trunk from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=d375891 ]

SQOOP-1278: Allow use of uncommitted isolation for databases that support it as an import option

(Venkat Ranganathan via Jarek Jarcec Cecho)


> 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
>         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
(v6.1.5#6160)