Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/12456#issuecomment-212677776
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. Now if you have some streaming logics, in each batch duration
these streaming logics will be translated into RDD operations and submitted to
`SparkContext` in another job thread. So if local property is not inheritable,
the property picked by this job thread will be empty, unless you manually copy
the property from the thread you set the local property. For a user there's no
chance to do it. But if you will change the Spark code, I think there's always
a way to handle it.
---
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]
