Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/813#issuecomment-46144569
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1092
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1089
---
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1088#issuecomment-46145753
I think the title should say: `SPARK-2039` instead of `SPARK-2309`
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1088#issuecomment-46145766
LGTM - I can merge this and I'll just fix the title.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1088
---
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
Github user li-zhihui commented on a diff in the pull request:
https://github.com/apache/spark/pull/900#discussion_r13793268
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/CoarseGrainedSchedulerBackend.scala
---
@@ -48,6 +48,10 @@ class
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/981#issuecomment-46146650
@darabos hey that's a flaky unit test we fixed a while back. The issue is
that your patch doesn't merge cleanly with master, so it's not getting the
fix. Do you mind
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1091#issuecomment-46147420
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1086#issuecomment-46147737
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1086#issuecomment-46147727
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/813#issuecomment-46148949
Build finished.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/813#issuecomment-46148950
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15811/
---
If your project is set up for it, you can
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1093#discussion_r13794553
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/stat/KernelDensity.scala ---
@@ -0,0 +1,66 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1091#issuecomment-46150263
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/1068#issuecomment-46150437
@pwendell Did I miss anything ?
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1086#issuecomment-46150728
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15813/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1086#issuecomment-46150727
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1093#discussion_r13794772
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/stat/KernelDensity.scala ---
@@ -0,0 +1,66 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/1093#discussion_r13794760
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/stat/KernelDensity.scala ---
@@ -0,0 +1,66 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/1050#discussion_r13794758
--- Diff: bin/run-example ---
@@ -27,10 +27,12 @@ if [ -n $1 ]; then
EXAMPLE_CLASS=$1
shift
else
- echo Usage: ./bin/run-example
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/1088#issuecomment-46161534
@pwendell , ah, sorry for the mistake
thanks for fixing this
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/900#discussion_r13808991
--- Diff:
yarn/common/src/main/scala/org/apache/spark/scheduler/cluster/YarnClientSchedulerBackend.scala
---
@@ -77,6 +77,12 @@ private[spark] class
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/894#discussion_r13810314
--- Diff: docs/running-on-yarn.md ---
@@ -67,6 +67,20 @@ Most of the configs are the same for Spark on YARN as
for other deployment modes
The
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/894#discussion_r13810329
--- Diff: docs/running-on-yarn.md ---
@@ -67,6 +67,20 @@ Most of the configs are the same for Spark on YARN as
for other deployment modes
The
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/969#issuecomment-46191458
@witgo As I stated above, the config for client mode is not meant for the
end user, it is for internal use that is why I consider this an improvement and
not a bug.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/894#issuecomment-46192112
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/894#issuecomment-46192097
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/981#issuecomment-46192771
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/981#issuecomment-46192755
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
Github user scwf commented on a diff in the pull request:
https://github.com/apache/spark/pull/714#discussion_r13811545
--- Diff: core/src/main/scala/org/apache/spark/SparkConf.scala ---
@@ -236,6 +236,27 @@ class SparkConf(loadDefaults: Boolean) extends
Cloneable with Logging {
Github user scwf closed the pull request at:
https://github.com/apache/spark/pull/567
---
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
Github user scwf closed the pull request at:
https://github.com/apache/spark/pull/625
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/981#issuecomment-46198003
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15815/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/981#issuecomment-46198001
Merged build finished.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/894#issuecomment-46198004
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15814/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/894#issuecomment-46198002
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/969#issuecomment-46198873
@tgravescs The code should be like this?
ClientArguments:
```scala
// -archives/--files via spark submit or yarn-client defaults to use
file:// if not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/981#issuecomment-46199453
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/981#issuecomment-46199444
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
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46199870
@ScrapCodes: in that case, wouldn't it be better to just use echo
everywhere? Yeah, it's a little more verbose, but doesn't suffer from the
indentation issue.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1085#issuecomment-46200054
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1085#issuecomment-46200040
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
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1094#issuecomment-46201382
Hi @rahulsinghaliitd,
Thanks for filing this; this is something I had on my radar but hadn't
gotten down to it yet.
While I also want the feature, I
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/969#issuecomment-46202989
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/969#issuecomment-46203003
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1050#issuecomment-46203327
Yeah, I personally prefer echoes. The indentation thing is a little hard to
track sometimes, especially because this is bash.
---
If your project is set up for it,
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/714#discussion_r13816162
--- Diff: core/src/main/scala/org/apache/spark/SparkConf.scala ---
@@ -236,6 +236,18 @@ class SparkConf(loadDefaults: Boolean) extends
Cloneable with
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/714#issuecomment-46203619
Ah yes, this is much better. There is a missing indent. After you fix that
I think this is good to go.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/981#issuecomment-46204734
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15816/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/981#issuecomment-46204733
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/1095#issuecomment-46206220
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 have this feature
enabled
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1082#issuecomment-46209130
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1085#issuecomment-46209843
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15817/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1085#issuecomment-46209841
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/969#issuecomment-46209840
Merged build finished.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/969#issuecomment-46209842
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15818/
---
If your project is set up for it, you can
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1090#discussion_r13819928
--- Diff: core/src/main/scala/org/apache/spark/rdd/SortedParitionsRDD.scala
---
@@ -0,0 +1,337 @@
+/*
+ * Licensed to the Apache Software
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1090#discussion_r13820071
--- Diff: core/src/main/scala/org/apache/spark/rdd/SortedParitionsRDD.scala
---
@@ -0,0 +1,337 @@
+/*
+ * Licensed to the Apache Software
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1090#discussion_r13820032
--- Diff: core/src/main/scala/org/apache/spark/rdd/SortedParitionsRDD.scala
---
@@ -0,0 +1,337 @@
+/*
+ * Licensed to the Apache Software
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1090#discussion_r13820570
--- Diff: core/src/main/scala/org/apache/spark/rdd/SortedParitionsRDD.scala
---
@@ -0,0 +1,337 @@
+/*
+ * Licensed to the Apache Software
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1090#discussion_r13820746
--- Diff: core/src/main/scala/org/apache/spark/rdd/SortedParitionsRDD.scala
---
@@ -0,0 +1,337 @@
+/*
+ * Licensed to the Apache Software
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1090#discussion_r13820794
--- Diff: core/src/main/scala/org/apache/spark/rdd/SortedParitionsRDD.scala
---
@@ -0,0 +1,337 @@
+/*
+ * Licensed to the Apache Software
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1090#discussion_r13820829
--- Diff: core/src/main/scala/org/apache/spark/rdd/SortedParitionsRDD.scala
---
@@ -0,0 +1,337 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1055#issuecomment-46213424
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
Github user ash211 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1090#discussion_r13820938
--- Diff: core/src/main/scala/org/apache/spark/rdd/SortedParitionsRDD.scala
---
@@ -0,0 +1,337 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1041#issuecomment-46213668
Thanks. I've merged this in master branch-1.0.
---
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
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1090#discussion_r13820994
--- Diff: core/src/main/scala/org/apache/spark/rdd/SortedParitionsRDD.scala
---
@@ -0,0 +1,337 @@
+/*
+ * Licensed to the Apache Software
Github user concretevitamin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1055#discussion_r13821017
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -917,6 +919,19 @@ private[hive] object HiveQl {
case
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1041
---
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
Github user rahulsinghaliitd commented on the pull request:
https://github.com/apache/spark/pull/1094#issuecomment-46213984
Hi @vanzin,
I don't have any preference as to how the URL is formatted and I think that
changing the URL can be a separate activity. I am hoping this
Github user sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/1093#discussion_r13821125
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/stat/KernelDensity.scala ---
@@ -0,0 +1,66 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1055#issuecomment-46213443
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1082#issuecomment-46214558
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15819/
---
If your
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1090#issuecomment-46214599
Hi @msiddalingaiah, thanks for adding this much-needed functionality. I
haven't looked too closely into the details, but it seems that this shares much
of the logic
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1082#issuecomment-46214557
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user msiddalingaiah commented on the pull request:
https://github.com/apache/spark/pull/1090#issuecomment-46218706
Thanks. It's not clear to me if it can use ExternalAppendInlyMap as the
underlying buffer either. There was some discussion about how to handle memory
management
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/807#discussion_r13823899
--- Diff:
external/flume/src/main/scala/org/apache/spark/streaming/flume/EventTransformer.scala
---
@@ -0,0 +1,72 @@
+/*
+ * Licensed to the
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/807#discussion_r13823887
--- Diff:
external/flume/src/main/scala/org/apache/spark/streaming/flume/EventTransformer.scala
---
@@ -0,0 +1,72 @@
+/*
+ * Licensed to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/999#issuecomment-46222354
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/999#issuecomment-46222342
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/999#issuecomment-46222401
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15821/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/999#issuecomment-46222400
Merged build finished.
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/999#issuecomment-46222714
Have made a few changes:
* Removed the special SchemaRDD (JsonRDD) for JSON datasets. Now, when
users call `jsonFile` and `jsonRDD`, a SchemaRDD is returned.
* Added
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1083#issuecomment-46222984
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1083#issuecomment-46222973
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1055#issuecomment-46223170
Build finished.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1055#issuecomment-46223171
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15820/
---
If your project is set up for it, you can
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/894
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1085
---
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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1085#issuecomment-46224276
Thanks! Merged into master and 1.0.
---
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/807#discussion_r13825922
--- Diff:
external/flume/src/main/scala/org/apache/spark/streaming/flume/EventTransformer.scala
---
@@ -0,0 +1,72 @@
+/*
+ * Licensed to the Apache
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/807#discussion_r13825936
--- Diff:
external/flume/src/main/scala/org/apache/spark/streaming/flume/EventTransformer.scala
---
@@ -0,0 +1,72 @@
+/*
+ * Licensed to the Apache
Github user harishreedharan commented on a diff in the pull request:
https://github.com/apache/spark/pull/807#discussion_r13826375
--- Diff:
external/flume/src/main/scala/org/apache/spark/streaming/flume/EventTransformer.scala
---
@@ -0,0 +1,72 @@
+/*
+ * Licensed to the
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/718#issuecomment-46225589
No changes, just rebased on top of current master.
---
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
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/999#discussion_r13826595
--- Diff: docs/sql-programming-guide.md ---
@@ -17,20 +17,20 @@ Spark. At the core of this component is a new type of
RDD,
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/999#discussion_r13826671
--- Diff: docs/sql-programming-guide.md ---
@@ -62,10 +62,10 @@ descendants. To create a basic SQLContext, all you
need is a SparkContext.
{%
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/999#discussion_r13827260
--- Diff: docs/sql-programming-guide.md ---
@@ -98,7 +98,9 @@ sqlCtx = SQLContext(sc)
/div
-## Running SQL on RDDs
+# Data Sources
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/999#discussion_r13827230
--- Diff: docs/sql-programming-guide.md ---
@@ -98,7 +98,9 @@ sqlCtx = SQLContext(sc)
/div
-## Running SQL on RDDs
+# Data Sources
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1083#issuecomment-46229031
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
1 - 100 of 261 matches
Mail list logo
