Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/7321#issuecomment-120088764
I know the motivation of re-using SQLContexts but I wonder save/load really
don't have chances they receive another instance of SparkContext with different
configuration in one application.
For example, even it maybe rare case, does following code work with this
patch?
```
val conf = new SparkConf().setAppName("...").setMaster("...")
val sc1 = new SparkContext(conf)
...
NaiveBayesModel.save(sc1, path1)
sc1.stop
...
val sc2 = new SparkContext(conf)
...
NaiveBayesModel.save(sc2, path2) // may fail?
```
---
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]
