[
https://issues.apache.org/jira/browse/SQOOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686497#comment-15686497
]
Hudson commented on SQOOP-3028:
-------------------------------
FAILURE: Integrated in Jenkins build Sqoop-hadoop23 #1271 (See
[https://builds.apache.org/job/Sqoop-hadoop23/1271/])
SQOOP-3028: Include stack trace in the logging of exceptions in (maugli:
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=c08c194eb9a34733305535a9512f3b642ef33f95])
* (edit) src/java/org/apache/sqoop/tool/ExportTool.java
> Include stack trace in the logging of exceptions in ExportTool
> --------------------------------------------------------------
>
> Key: SQOOP-3028
> URL: https://issues.apache.org/jira/browse/SQOOP-3028
> Project: Sqoop
> Issue Type: Improvement
> Reporter: Attila Szabo
> Assignee: Boglarka Egyed
> Priority: Trivial
> Fix For: 1.4.7
>
> Attachments: SQOOP-3028.patch
>
>
> Currently only the message of the IOException/Export is logged in runExport
> method. Although it's possible to rethrow the root cause as a runtime
> exception it would be nice to improve to add an option which makes possible
> to have the improved logging details without an additional exception (as that
> could be problematic on tooling side).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
