Venkat Ranganathan created SQOOP-1278:
-----------------------------------------
Summary: Allow use of uncommitted isolation on databases that
support is an import option
Key: SQOOP-1278
URL: https://issues.apache.org/jira/browse/SQOOP-1278
Project: Sqoop
Issue Type: Bug
Affects Versions: 1.4.4, 1.4.3
Environment: All DBs that support uncommitted read transaction
isolation
Reporter: Venkat Ranganathan
Assignee: Venkat Ranganathan
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)
