Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/13798
Right they are really SparkContext methods - I could leave/deprecate them
if you'd prefer, or separate that into a different PR?
---
If your project is set up for it, you can reply to this
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/13798
Hmm can we document somewhere why we want to remove this functionality ? Is
this because spark context is no longer accessible ?
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13798
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60903/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13798
**[Test build #60903 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60903/consoleFull)**
for PR 13798 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13798
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13798
**[Test build #60903 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60903/consoleFull)**
for PR 13798 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/13798
Opened a JIRA since we are removing methods.
---
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
