You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Abraham Elmahrek (JIRA)" <ji...@apache.org> on 2013/04/24 02:39:17 UTC

[jira] [Closed] (SQOOP-669) Make job delete operation more safer and easier

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

Abraham Elmahrek closed SQOOP-669.
----------------------------------

    
> 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