Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/180#issuecomment-38491639
Here's what the stack trace looks like:
```
java.lang.RuntimeException
at org.apache.spark.util.Utils$.getCallSiteInfo(Utils.scala:687)
at
org.apache.spark.util.Utils$.formatCallSiteInfo$default$1(Utils.scala:723)
at
org.apache.spark.SparkContext$$anonfun$getCallSite$1.apply(SparkContext.scala:880)
at
org.apache.spark.SparkContext$$anonfun$getCallSite$1.apply(SparkContext.scala:880)
at scala.Option.getOrElse(Option.scala:120)
at org.apache.spark.SparkContext.getCallSite(SparkContext.scala:880)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:898)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:920)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:934)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:948)
at org.apache.spark.rdd.RDD.collect(RDD.scala:657)
...
at org.apache.spark.repl.SparkILoop.process(SparkILoop.scala:981)
at org.apache.spark.repl.Main$.main(Main.scala:31)
at org.apache.spark.repl.Main.main(Main.scala)
```
It appears this was accidentally introduced when
[SparkContext:880](https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/SparkContext.scala#L880)
was changed to use the Option pattern. I've talked with Patrick (who made that
change) and we came to the conclusion that the better solution for now would be
to pull out the getCallSiteInfo from the Option and pass it into
formatCallSiteInfo.
Perhaps we could also add a unit test to make sure this doesn't happen in
the future if someone uses some Scala operation on the code path leading up to
the getCallSiteInfo.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
