[
https://issues.apache.org/jira/browse/SPARK-13172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137575#comment-15137575
]
Jakob Odersky edited comment on SPARK-13172 at 2/8/16 8:03 PM:
---------------------------------------------------------------
I would suggest taking similar approach to what the Scala library does:
https://github.com/scala/scala/blob/v2.11.7/src/library/scala/runtime/RichException.scala#L16,
that is just call mkString on the stack trace.
Using e.printStackTrace is not as flexible, it doesn't give you a string and as
far as I know it prints to stderr with no option to redirect.
was (Author: jodersky):
I would suggest taking similar approach to what the Scala library does:
https://github.com/scala/scala/blob/v2.11.7/src/library/scala/runtime/RichException.scala#L1,
that is just call mkString on the stack trace.
Using e.printStackTrace is not as flexible, it doesn't give you a string and as
far as I know it prints to stderr with no option to redirect.
> Stop using RichException.getStackTrace it is deprecated
> -------------------------------------------------------
>
> Key: SPARK-13172
> URL: https://issues.apache.org/jira/browse/SPARK-13172
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Reporter: holdenk
> Priority: Trivial
>
> Throwable getStackTrace is the recommended alternative.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
