We would still probably catch the error when it went to use the SparkContext to call runJob, it would be a bit further down the call stack though (although I just traced the code and it looks like we would get a null pointer exception since we have a second accessor method to the internal sparkcontext called context so I wrapped that access method as well).