You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Felix Cheung (JIRA)" <ji...@apache.org> on 2015/05/10 06:51:59 UTC
[jira] [Created] (ZEPPELIN-75) PySpark interpreter - useful
debugging traceback information is lost for any error from Spark
Felix Cheung created ZEPPELIN-75:
------------------------------------
Summary: PySpark interpreter - useful debugging traceback information is lost for any error from Spark
Key: ZEPPELIN-75
URL: https://issues.apache.org/jira/browse/ZEPPELIN-75
Project: Zeppelin
Issue Type: Bug
Components: Interpreters
Affects Versions: 0.5.0
Reporter: Felix Cheung
Assignee: Felix Cheung
When there is an error from Spark, the original error is not returned as output in the cell, instead a generic Py4JError is shown.
(<class 'py4j.protocol.Py4JJavaError'>, Py4JJavaError(u'An error occurred while calling o45.collect.\n', JavaObject id=o46), <traceback object at 0x7fb737ea72d8>)
While it is possible to look at zeppelin-interpreter-spark-root-node.log, it might not be accessible for a multi-user environment as it will require remote access to the host running Zeppelin.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)