sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SQOOP-878) Sqoop2: Detect corrupted repository
Date Sat, 09 Feb 2013 04:47:12 GMT
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

Mime
View raw message