[
https://issues.apache.org/jira/browse/SQOOP-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289440#comment-14289440
]
Veena Basavaraj edited comment on SQOOP-2043 at 1/23/15 4:04 PM:
-----------------------------------------------------------------
there is a duplicate ticket for this, it is even worse when it says class not
found on the Error class when there is an actual exception, I wonder if this is
with Kerberos changes since we changed the client from jersery to xxxx if the
suspect is regression
was (Author: vybs):
there is a duplicate ticket for this, it is even worse when it says class not
found on the Error class when there is an actual exception
> Sqoop2: Server errors don't look informative enough in the client
> -----------------------------------------------------------------
>
> Key: SQOOP-2043
> URL: https://issues.apache.org/jira/browse/SQOOP-2043
> Project: Sqoop
> Issue Type: Bug
> Reporter: Gwen Shapira
>
> sqoop:000> start job -jid 5
> Exception has occurred during processing command
> Exception: org.apache.sqoop.common.SqoopException Message: CLIENT_0001:Server
> has returned exception
> I had to go to the server log to see what went wrong. Clearly this is not
> very useful. I seem to remember that in the past we actually got more useful
> errors on the CLI, so this is possibly a regression.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
