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 thread) and be picked in child thread (job thread). Basically if
the creation of `SparkContext` and submitting job are in two threads, local
properties should be passed from parent thread to child thread. IIUC, there's
no way for user to set it in the job thread specifically, so that's why I
changed long time ago, here is the original PR
(https://github.com/mesos/spark/pull/937).
If there's other solution to solve this issue, I fully agree with the
change to non-inheritable variables.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
