[jira] [Commented] (SQOOP-696) Client command submission status will finish gracefully when executed for non existing job

["Bilung Lee (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SQOOP-696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526995#comment-13526995 ] 

Bilung Lee commented on SQOOP-696:
----------------------------------

Look like you attached a patch for a different JIRA (SQOOP-644).  Could you please reattach?  Thanks.
                
> Client command submission status will finish gracefully when executed for non existing job
> ------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-696
>                 URL: https://issues.apache.org/jira/browse/SQOOP-696
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Jarek Jarcec Cecho
>              Labels: newbie
>             Fix For: 1.99.1
>
>         Attachments: bugSQOOP-644.patch
>
>
> Getting submission status for non existing job will finish gracefully whereas similar command for starting new job will end up with exception. I would recommend to unify the behavior.
> {code}
> sqoop:000> submission start --jid 666
> Exception has occurred during processing command 
> Server has returned exception: Exception: java.lang.Throwable Message: DERBYREPO_0030:Unable to load specific job metadata from repository - Couldn't find job with id 666
> sqoop:000> submission status --jid 666
> Submission details
> Job id: 666
> Status: NEVER_EXECUTED
> Creation date: 2012-26-14 11:26:40 PST
> Last update date: 2012-26-14 11:26:40 PST
> {code}

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