Uploaded image for project: 'Sqoop (Retired)'
  1. Sqoop (Retired)
  2. SQOOP-878

Sqoop2: Detect corrupted repository

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Invalid
    • 1.99.1
    • no-release
    • None
    • None

    Description

      During our testing we found out that if we start sqoop2 server and quickly turn it off, tomcat will just kill Sqoop bootstrap process. If the process was in the middle of schema creation it might not create all the tables. However next start will not detect incorrect schema and will silently continue resulting in very strange exception later.

      I believe that we can quite easily solve this particular issue by creating entire schema in one transaction. Right now each table is being created in it's own transaction.

      Attachments

        Issue Links

          is blocked by

          Improvement - An improvement or enhancement to an existing feature or task. SQOOP-943 Sqoop2: Repository wide configuration of immutable disk structures

          • Major - Major loss of function.
          • Resolved
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SQOOP-944 Sqoop2: Persist table schema version in database in Derby repository

          • Major - Major loss of function.
          • Resolved
          is superceded by

          Improvement - An improvement or enhancement to an existing feature or task. SQOOP-1111 Sqoop2: Implement version detection and structure updates into Derby repository

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              jarcec Jarek Jarcec Cecho
              jarcec Jarek Jarcec Cecho
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: