You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Saisai Shao (Jira)" <ji...@apache.org> on 2019/09/29 08:21:00 UTC
[jira] [Resolved] (LIVY-688) Error message of LivyClient only keep
outer stackTrace but discard cause's stackTrace
[ https://issues.apache.org/jira/browse/LIVY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Saisai Shao resolved LIVY-688.
------------------------------
Fix Version/s: 0.7.0
Resolution: Fixed
Issue resolved by pull request 237
[https://github.com/apache/incubator-livy/pull/237]
> Error message of LivyClient only keep outer stackTrace but discard cause's stackTrace
> -------------------------------------------------------------------------------------
>
> Key: LIVY-688
> URL: https://issues.apache.org/jira/browse/LIVY-688
> Project: Livy
> Issue Type: Improvement
> Components: RSC
> Affects Versions: 0.6.0
> Reporter: weiwenda
> Priority: Trivial
> Fix For: 0.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 1. SparkSession maybe failed when initialize ExternalCatalog at sometime. As SparkSession call _SharedState.reflect_ to instance an ExternalCatalog, any exception happened during this process will wrapped by InvocationTargetException.
> IllegalArgumentException
> └──InvocationTargetException
> └──the indeed Exception
> 2. org.apache.livy.rsc.Utils.stackTraceAsString only keep IllegalArgumentException's stackTrace but discard the indeed Exception's stackTrace and message, which makes the final java.util.concurrent.ExecutionException's message ambiguous.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)