Uploaded image for project: 'Sqoop'
  1. Sqoop
  2. SQOOP-696

Client command submission status will finish gracefully when executed for non existing job

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 1.99.1
    • Component/s: None
    • Labels:

      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
      

        Attachments

        1. bugSQOOP-696.patch
          0.8 kB
          Jarek Jarcec Cecho

          Issue Links

            Activity

              People

              • Assignee:
                jarcec Jarek Jarcec Cecho
                Reporter:
                jarcec Jarek Jarcec Cecho
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: