Github user zjffdu commented on the issue:
    The internal SparkConf of the context will not be the same instance as conf.
    This is the existing implementation that python is different from scala. 
But I think it is correct. I guess the reason why in scala the internal 
SparkConf of the SparkContext is not the same instance as conf is to make sure 
changing SparkConf take effect after SparkContext is created would not take 
effect. pyspark is the same in this perspective. Although in pyspark the 
internal SparkConf of SparkContext is the same instance as conf,  changing conf 
after SparkContext is created would not take effect  as it is guaranteed in 
scala side. 

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 or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to