sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abraham Elmahrek (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SQOOP-669) Make job delete operation more safer and easier
Date Tue, 23 Apr 2013 23:23:16 GMT

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

Abraham Elmahrek resolved SQOOP-669.

    Resolution: Not A Problem

All of the submission tables have ON DELETE CASCADE already.
> Make job delete operation more safer and easier
> -----------------------------------------------
>                 Key: SQOOP-669
>                 URL: https://issues.apache.org/jira/browse/SQOOP-669
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Abraham Elmahrek
>              Labels: newbie
>             Fix For: 2.0.0
> We should enforce to delete job metadata object only in case that there are no running
jobs and also to remove all connected submissions (e.g. ON DELETE CASCADE in derby metastore).

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

View raw message