Nope, you shouldn't have to do that anymore. As of https://github.com/apache/spark/pull/2624, which is in Spark 1.2.0+, SparkEnv's thread-local stuff was removed and replaced by a simple global variable (since it was used in an *effectively* global way before (see my comments on that PR)). As a result, there shouldn't really be any need for you to call SparkEnv.set(env) in your user threads anymore.
On Thu, Dec 10, 2015 at 11:03 AM, Nirav Patel <npa...@xactlycorp.com> wrote: > As subject says, do we still need to use static env in every thread that > access sparkContext? I read some ref here. > > > http://qnalist.com/questions/4956211/is-spark-context-in-local-mode-thread-safe > > > > [image: What's New with Xactly] <http://www.xactlycorp.com/email-click/> > > <https://www.nyse.com/quote/XNYS:XTLY> [image: LinkedIn] > <https://www.linkedin.com/company/xactly-corporation> [image: Twitter] > <https://twitter.com/Xactly> [image: Facebook] > <https://www.facebook.com/XactlyCorp> [image: YouTube] > <http://www.youtube.com/xactlycorporation>
