Uploaded image for project: 'Sqoop'
  1. Sqoop
  2. SQOOP-1278

Allow use of uncommitted isolation for databases that support it as an import option

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.4.3, 1.4.4
    • Fix Version/s: 1.4.5
    • Component/s: None
    • Labels:
      None
    • Environment:

      All DBs that support uncommitted read transaction isolation

      Description

      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

        Attachments

        1. SQOOP-1278.diff
          9 kB
          Venkat Ranganathan
        2. SQOOP-1278-3.diff
          10 kB
          Venkat Ranganathan

          Activity

            People

            • Assignee:
              venkatnrangan Venkat Ranganathan
              Reporter:
              venkatnrangan Venkat Ranganathan

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment