Matei Zaharia created SPARK-1710:
------------------------------------
Summary: spark-submit should print better errors than
"InvocationTargetException"
Key: SPARK-1710
URL: https://issues.apache.org/jira/browse/SPARK-1710
Project: Spark
Issue Type: Improvement
Reporter: Matei Zaharia
Priority: Minor
It's not horrible, but it is a bit confusing that exceptions in your driver
program get hidden inside InvocationTargetException:
{code}
matei@mbp-3:~/workspace/apache-spark$ bin/spark-submit --class SparkTest
../spark-test/target/scala-2.10/simple-project_2.10-1.0.jar
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.spark.deploy.SparkSubmit$.launch(SparkSubmit.scala:256)
at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:54)
at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
Caused by: org.apache.spark.SparkException: An application name must be set in
your configuration
at org.apache.spark.SparkContext.<init>(SparkContext.scala:163)
at SparkTest$.main(Test.scala:7)
at SparkTest.main(Test.scala)
... 7 more
{code}
It would be better to print just the stack trace of the nested exception
--
This message was sent by Atlassian JIRA
(v6.2#6252)
