Github user mtustin-handy commented on the pull request:
https://github.com/apache/spark/pull/12456#issuecomment-213037791
@jerryshao Makes sense. Would having an explicitly inheritable facility, or
a way to switch the spark context into inheritable mode (whatever that design
looks
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/12456#issuecomment-21266
For example, if you have a main thread to create a `SparkContext`, and a
child thread to use this `SparkContext` to create `StreamingContext` and set
local property.
Github user marcintustin commented on the pull request:
https://github.com/apache/spark/pull/12456#issuecomment-212672809
@jerryshao
> there's no way for user to set it in the job thread specifically,
Can you explain what you mean by that? Or link us to some code?
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/12456#issuecomment-211700705
Hi @rxin , the reason to use inheritable variable is for some scenarios
like Spark Streaming + FIFO scheduling, the property of pool is set in parent
thread (main
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12456#issuecomment-211505486
cc @jerryshao
I just talked to @JoshRosen more and thinking whether we should make this
always non-inheritable. Josh said Jerry might've added something in the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12456#issuecomment-211487324
Can one of the admins verify this patch?
---
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
