sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-629) Provide better exception handling during server-client communication
Date Wed, 17 Oct 2012 16:46:03 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jarek Jarcec Cecho updated SQOOP-629:

    Attachment: bugSQOOP-629.patch
> Provide better exception handling during server-client communication
> --------------------------------------------------------------------
>                 Key: SQOOP-629
>                 URL: https://issues.apache.org/jira/browse/SQOOP-629
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 2.0.0
>         Attachments: bugSQOOP-629.patch, bugSQOOP-629.patch
> Currently in case of an exception on the server side we're transferring exception's message,
error code and printed stack trace (that is not displayed on the client at all). Would be
great if this logic would be improved to transfer entire exception including all "caused by"
exceptions. Also appropriate error printing on client side would be great.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message