[
https://issues.apache.org/jira/browse/ZEPPELIN-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388136#comment-14388136
]
ASF GitHub Bot commented on ZEPPELIN-16:
----------------------------------------
GitHub user RamVenkatesh opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/17
ZEPPELIN-16 Some failures from Spark and SparkSql note execution are not
reported
... reported
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/RamVenkatesh/incubator-zeppelin ZEPPELIN-16
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/17.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #17
----
commit 80793c4e1101f4c9579a8298187ea084c2714cbd
Author: Ram Venkatesh <[email protected]>
Date: 2015-03-31T06:51:04Z
ZEPPELIN-16 Some failures from Spark and SparkSql note execution are not
reported
----
> Some failures from Spark and SparkSql note execution are not reported
> ---------------------------------------------------------------------
>
> Key: ZEPPELIN-16
> URL: https://issues.apache.org/jira/browse/ZEPPELIN-16
> Project: Zeppelin
> Issue Type: New Feature
> Reporter: Ram Venkatesh
>
> Some spark and spark sql note execution can silently fail - the result
> progress line is drawn but no results are returned. For example, run the
> tutorial sql script with a typo in it, such as changing the table name to
> non_existent.
> The root cause seems to be the following pattern:
> {code}
> return new InterpreterResult(Code.ERROR, e.getMessage());
> {code}
> Unfortunately, when the Spark framework throws an InvocationTargetException,
> the message is empty.
> I will provide a patch for this shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
