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 2012/10/17 02:24:03 UTC

[jira] [Updated] (SQOOP-630) Check if connection/job is in use before deleting as deleting used entity might result in FK violations

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

Jarek Jarcec Cecho updated SQOOP-630:
-------------------------------------

    Attachment: SQOOP-630.patch
    
> Check if connection/job is in use before deleting as deleting used entity might result in FK violations
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-630
>                 URL: https://issues.apache.org/jira/browse/SQOOP-630
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 2.0.0
>
>         Attachments: SQOOP-630.patch
>
>
> Currently Sqoop will end up with SqlException in case that user will try to delete connection that have associated job objects. Would be nice to add checks to prevent that.

--
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