[
https://issues.apache.org/jira/browse/SQOOP-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated SQOOP-878:
-------------------------------------
Fix Version/s: 2.0.0
> 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
> Assignee: Jarek Jarcec Cecho
> Fix For: 2.0.0
>
>
> 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
