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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 1.99.1
• Labels: newbie
• Assignee: Jarek Jarcec Cecho
• Reporter: Jarek Jarcec Cecho
• Created: 14/Nov/12 19:28
• Updated: 08/Dec/12 03:27
• Resolved: 08/Dec/12 03:27

Description

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.

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

Issue Links

• links to: Review board