[
https://issues.apache.org/jira/browse/SQOOP-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830429#comment-13830429
]
Jarek Jarcec Cecho commented on SQOOP-1242:
-------------------------------------------
Hi [~vasanthkumar],
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:
{code}
set option --name verbose --value true
show job --jid 100
{code}
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?
> Shell option errors not displayed and client error not printed
> --------------------------------------------------------------
>
> Key: SQOOP-1242
> URL: https://issues.apache.org/jira/browse/SQOOP-1242
> Project: Sqoop
> Issue Type: Bug
> Components: sqoop2-client
> Affects Versions: 1.99.3
> Reporter: Vasanth kumar RJ
> Assignee: Vasanth kumar RJ
> Fix For: 1.99.4
>
> Attachments: SQOOP-1242.patch
>
>
> 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:
> {code}
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
