[
https://issues.apache.org/jira/browse/SPARK-8870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiangrui Meng resolved SPARK-8870.
----------------------------------
Resolution: Won't Fix
Based on the discussion on the Github page, this approach doesn't save us much.
And it may have issues with multiple SparkContexts. So I'm closing this JIRA
now. Sorry about giving something wrong!
[~Kico Wang], please try another starter task to get started:)
[~y-shimizu], please check JIRA comments and see whether there are people
already working on the issue. This is to avoid duplicate work. For small JIRAs,
we usually fill the assignee field after PR is merged. Sorry for the confusion!
> Use SQLContext.getOrCreate in model save/load
> ---------------------------------------------
>
> Key: SPARK-8870
> URL: https://issues.apache.org/jira/browse/SPARK-8870
> Project: Spark
> Issue Type: Improvement
> Components: MLlib
> Affects Versions: 1.4.0
> Reporter: Xiangrui Meng
> Priority: Minor
> Labels: starter
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> In many model save/load code, we use `new SQLContext(sc)` to create a
> SQLContext. This could be replace by `SQLContext.getOrCreate(sc)` to reuse an
> existing context.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
