Github user mwws commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-192150357
@jelez you can create an HiveContextSingleton to workaround it. Refer to
example "SqlNetWorkWordCount"
@tdas Why you removed HiveContext.getOrCreate? I can't find o
Github user jelez commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-191898780
Can you guys point me what is the proper way to use getOrCreate with
HiveContext?
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6006
---
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 enab
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104418524
I merging this! Thanks @marmbrus for reviewing.
---
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 proj
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104417350
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104417337
[Test build #33264 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33264/consoleFull)
for PR 6006 at commit
[`25f4da9`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104417348
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104388729
[Test build #33264 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33264/consoleFull)
for PR 6006 at commit
[`25f4da9`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104388649
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104388617
Merged build triggered.
---
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 h
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6006#discussion_r30831007
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -1270,9 +1271,59 @@ class SQLContext(@transient val sparkContext:
SparkContext)
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6006#discussion_r30830692
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -1270,9 +1271,59 @@ class SQLContext(@transient val sparkContext:
SparkContext)
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104371577
Minor comments, otherwise LGTM.
---
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
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/6006#discussion_r30827922
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -1270,9 +1271,59 @@ class SQLContext(@transient val sparkContext:
SparkContext
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/6006#discussion_r30827823
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -1270,9 +1271,59 @@ class SQLContext(@transient val sparkContext:
SparkContext
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104131013
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104131015
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104131005
[Test build #33207 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33207/consoleFull)
for PR 6006 at commit
[`79fe069`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104112669
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104112673
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104112651
[Test build #33201 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33201/consoleFull)
for PR 6006 at commit
[`c66ca76`](https://git
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104109324
@marmbrus Could you take a look?
---
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 ha
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104106154
[Test build #33207 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33207/consoleFull)
for PR 6006 at commit
[`79fe069`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104106010
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104106021
Merged build started.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104089926
[Test build #33201 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33201/consoleFull)
for PR 6006 at commit
[`c66ca76`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104089901
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104089887
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104089752
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104089751
Build finished. Test FAILed.
---
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 n
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104089402
Build started.
---
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 f
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104089442
[Test build #33199 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33199/consoleFull)
for PR 6006 at commit
[`48adb14`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-104089385
Build triggered.
---
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 thi
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102730578
HiveContext use derby as the metastore database defaultly which only
support single instance for one metastore path.
I think you need config the ```javax.jdo.option
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102722259
@marmbrus Can you help me debug this?
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102605009
[Test build #32904 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32904/consoleFull)
for PR 6006 at commit
[`bf8cf50`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102605012
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102605011
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102604796
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102604789
[Test build #32903 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32903/consoleFull)
for PR 6006 at commit
[`dec5594`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102604795
Merged build finished. Test FAILed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102593680
[Test build #32904 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32904/consoleFull)
for PR 6006 at commit
[`bf8cf50`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102593572
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102593537
Merged build triggered.
---
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102592949
[Test build #32903 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32903/consoleFull)
for PR 6006 at commit
[`dec5594`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102592902
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102592907
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102591954
Build finished. Test FAILed.
---
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 n
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102591955
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102591947
[Test build #32891 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32891/consoleFull)
for PR 6006 at commit
[`d3ea8e4`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102589669
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102589667
[Test build #32894 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32894/consoleFull)
for PR 6006 at commit
[`b4e9721`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102589668
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102584202
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102584203
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-10258
[Test build #32894 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32894/consoleFull)
for PR 6006 at commit
[`b4e9721`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102583276
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102583284
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102582704
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102582700
Merged build triggered.
---
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 h
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102582626
[Test build #32891 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32891/consoleFull)
for PR 6006 at commit
[`d3ea8e4`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102582564
Build triggered.
---
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 thi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102582568
Build started.
---
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102572014
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102572010
[Test build #32880 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32880/consoleFull)
for PR 6006 at commit
[`83bc950`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102572016
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102567369
[Test build #32880 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32880/consoleFull)
for PR 6006 at commit
[`83bc950`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102567196
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-102567198
Merged build started.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100356985
[Test build #32264 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32264/consoleFull)
for PR 6006 at commit
[`f82ae81`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100357001
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100356996
Merged build finished. Test FAILed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100351872
[Test build #32264 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32264/consoleFull)
for PR 6006 at commit
[`f82ae81`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100351657
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100351689
Merged build started.
---
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
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100351266
So `HiveContext.getOrCreate` sounds good?
---
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 do
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100351106
test this please.
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100334821
Yeah the first part seems reasonable. But I think you also need a way to
force the getOrCreate command to create a hive context.
---
If your project is set up for it,
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100332361
@marmbrus Good you raised the question. @rxin and I had half-a-discussion
offline about it. Correct me if I am wrong but HiveContext is a superset of the
SQLContext in term
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100329387
What about `HiveContext`?
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100184502
[Test build #32224 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32224/consoleFull)
for PR 6006 at commit
[`f82ae81`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100184515
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100184512
Merged build finished. Test FAILed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100180763
[Test build #32224 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32224/consoleFull)
for PR 6006 at commit
[`f82ae81`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100180494
Merged build started.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100180478
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100159724
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100159728
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100159709
[Test build #32220 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32220/consoleFull)
for PR 6006 at commit
[`bc72868`](https://git
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6006#discussion_r29924867
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -1272,6 +1273,56 @@ class SQLContext(@transient val sparkContext:
SparkContext)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100152669
[Test build #32220 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32220/consoleFull)
for PR 6006 at commit
[`bc72868`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100152398
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100152416
Merged build started.
---
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
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/6006
[SPARK-7478][SQL] Added SQLContext.getOrCreate
Having a SQLContext singleton would make it easier for applications to use
a lazily instantiated single shared instance of SQLContext when needed. It
wou
94 matches
Mail list logo
