[
https://issues.apache.org/jira/browse/SQOOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15686393#comment-15686393
]
ASF subversion and git services commented on SQOOP-3028:
--------------------------------------------------------
Commit c08c194eb9a34733305535a9512f3b642ef33f95 in sqoop's branch
refs/heads/trunk from [~maugli]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=c08c194 ]
SQOOP-3028: Include stack trace in the logging of exceptions in ExportTool
(Boglarka Egyed via Attila Szabo)
> 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)
