You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2013/02/09 05:47:12 UTC

[jira] [Created] (SQOOP-878) Sqoop2: Detect corrupted repository

Jarek Jarcec Cecho created SQOOP-878:
----------------------------------------

             Summary: Sqoop2: Detect corrupted repository
                 Key: SQOOP-878
                 URL: https://issues.apache.org/jira/browse/SQOOP-878
             Project: Sqoop
          Issue Type: Bug
    Affects Versions: 1.99.1
            Reporter: Jarek Jarcec Cecho


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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira