sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abraham Fine (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-878) Sqoop2: Detect corrupted repository
Date Wed, 15 Jun 2016 18:37:10 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abraham Fine updated SQOOP-878:
-------------------------------
    Fix Version/s: no-release

> 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: no-release
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message