[
https://issues.apache.org/jira/browse/SQOOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666610#comment-15666610
]
Boglarka Egyed commented on SQOOP-3028:
---------------------------------------
Hi [~maugli],
This improvement seems to be a good idea, however I think making an option for
this would be a little bit overkill. The full stack trace should be logged
anyway and IMHO it should not cause any breaking change.
Although, another JIRA could be open for introducing a cmd line argument to
make the usage of rethrow easier.
Thanks,
Bogi
> 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
>
>
> 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)
