Sqoop
  1. Sqoop
  2. SQOOP-1242

Shell option errors not displayed and client error not printed

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.99.3
    • Fix Version/s: 2.0.0
    • Component/s: sqoop2-client
    • Labels:
      None

      Description

      In shell interactive model, no error message is thrown when wrong option is used in sqoop command.

      Shell is not displaying the server error message in shell:
      Example:

      sqoop:000> show job -jid 2
      Exception has occurred during processing command 
      Exception: org.apache.sqoop.common.SqoopException Message: CLIENT_0001:Server has returned exception
      
      1. SQOOP-1242.patch
        1 kB
        Vasanth kumar RJ

        Issue Links

          Activity

          Hide
          Sqoop QA bot added a comment -

          Here are the results of testing the latest attachment
          https://issues.apache.org/jira/secure/attachment/12615189/SQOOP-1242.patch against branch sqoop2.

          Overall: -1 due to 2 errors

          ERROR: failed to build with patch (exit code 1)
          ERROR: Patch does not add/modifny any test case
          SUCCESS: Clean was successful
          SUCCESS: Patch applied correctly

          Console output: https://builds.apache.org/job/PreCommit-SQOOP-Build/199/console

          This message is automatically generated.

          Show
          Sqoop QA bot added a comment - Here are the results of testing the latest attachment https://issues.apache.org/jira/secure/attachment/12615189/SQOOP-1242.patch against branch sqoop2. Overall: -1 due to 2 errors ERROR: failed to build with patch (exit code 1) ERROR: Patch does not add/modifny any test case SUCCESS: Clean was successful SUCCESS: Patch applied correctly Console output: https://builds.apache.org/job/PreCommit-SQOOP-Build/199/console This message is automatically generated.
          Hide
          Jarek Jarcec Cecho added a comment -

          Hi Vasanth kumar RJ,
          I believe that the long stack traces are intentionally hidden from the user in the default settings. Try to set the verbose mode via following command:

          set option --name verbose --value true
          show job --jid 100
          

          I agree that the default CLIENT_0001 exception is not much helpful for the end user. Rather then copy&pasting the same error text from one exception to another and confusing user even more, what about rather creating real instance of the SqoopException (or some of it's variant) instead of the placeholder CLIENT_0001. What do you think?

          Show
          Jarek Jarcec Cecho added a comment - Hi Vasanth kumar RJ , I believe that the long stack traces are intentionally hidden from the user in the default settings. Try to set the verbose mode via following command: set option --name verbose --value true show job --jid 100 I agree that the default CLIENT_0001 exception is not much helpful for the end user. Rather then copy&pasting the same error text from one exception to another and confusing user even more, what about rather creating real instance of the SqoopException (or some of it's variant) instead of the placeholder CLIENT_0001 . What do you think?
          Hide
          Vasanth kumar RJ added a comment -

          Hi Jarcec,
          Yes. I suggest there should be some message printed on client side when command execution creates error in server. Let me try your suggestion.

          Show
          Vasanth kumar RJ added a comment - Hi Jarcec, Yes. I suggest there should be some message printed on client side when command execution creates error in server. Let me try your suggestion.
          Hide
          Jarek Jarcec Cecho added a comment -

          Canceling patch as we're waiting on incorporating review feedback.

          Show
          Jarek Jarcec Cecho added a comment - Canceling patch as we're waiting on incorporating review feedback.

            People

            • Assignee:
              Vasanth kumar RJ
              Reporter:
              Vasanth kumar RJ
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Development