Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/360#discussion_r13373005
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/types/dataTypes.scala
---
@@ -29,25 +31,36 @@ abstract class DataType {
case e:
Github user ankurdave commented on a diff in the pull request:
https://github.com/apache/spark/pull/967#discussion_r13372794
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/Graph.scala ---
@@ -131,6 +131,19 @@ abstract class Graph[VD: ClassTag, ED: ClassTag]
protected () ex
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/967#discussion_r13372785
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/Graph.scala ---
@@ -131,6 +131,19 @@ abstract class Graph[VD: ClassTag, ED: ClassTag]
protected () extends
Github user zhpengg closed the pull request at:
https://github.com/apache/spark/pull/854
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/555#issuecomment-45056296
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15435/
---
If your project is set up for it, you can r
Github user ankurdave commented on a diff in the pull request:
https://github.com/apache/spark/pull/967#discussion_r13372714
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/Graph.scala ---
@@ -131,6 +131,19 @@ abstract class Graph[VD: ClassTag, ED: ClassTag]
protected () ex
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/555#issuecomment-45056295
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/894#issuecomment-45055404
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15434/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/894#issuecomment-45055403
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. If
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/755#issuecomment-45054683
BTW I forgot to add, but we should also add this to the PySpark programming
guide. Opened https://issues.apache.org/jira/browse/SPARK-2013 to track it.
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/964#issuecomment-45054649
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/964#issuecomment-45054651
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15436/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/964#issuecomment-45054565
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/964#issuecomment-45054572
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/964#issuecomment-45054524
Jenkins, this is ok to test
---
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/555#issuecomment-45054345
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/555#issuecomment-45054340
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 ha
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/555#issuecomment-45054230
Jenkins, retest this please. Seems reasonable to bump this up.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/369#issuecomment-45053945
@rxin want to give this a final sign off?
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/967#discussion_r13371929
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/Graph.scala ---
@@ -131,6 +131,19 @@ abstract class Graph[VD: ClassTag, ED: ClassTag]
protected () extends
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/735#issuecomment-45053682
@koertkuipers any interest in updating the docs and bumping the default?
This would be a good change to have.
---
If your project is set up for it, you can reply to this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/944
---
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 enabl
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/944#issuecomment-45053625
Thanks. I've merged this into master branch.
---
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 d
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/705#issuecomment-45053611
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15432/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/705#issuecomment-45053609
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 have
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/854#issuecomment-45053546
@zhpengg mind closing this? For some reason it didn't close correctly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/894#issuecomment-45053449
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-45053440
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 ha
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/930#issuecomment-45053395
I think right now of the user uses `--arg` before specifying the app jar it
will say "unrecognized option --arg". This might be the best behavior we can
achieve.
---
If
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/930#issuecomment-45053339
What if the user application legitimately has a flag called --arg? Won't
this cause it to break?
Also (just wondering) - why do you think users would be setting `
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/920
---
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 enabl
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-45053194
Hey - I still haven't heard back from the Mesos folks, by I'm fairly sure
they are wire-compatible across client library versions. If not, this patch can
be trivially rev
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/919#discussion_r13371699
--- Diff: core/src/test/java/org/apache/spark/JavaAPISuite.java ---
@@ -145,6 +135,27 @@ public void intersection() {
}
@Test
+ public v
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/938
---
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 enabl
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/938#issuecomment-45053075
I went ahead and merged this and manually resolved the conflict.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/781#issuecomment-45052694
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/781#issuecomment-45052695
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15433/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/781#issuecomment-45052647
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 fe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/781#issuecomment-45052644
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 this
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/781#issuecomment-45052549
Jenkins, retest this please. LGTM pending tests.
---
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 p
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/941#issuecomment-45052282
To keep it simple, I'd prefer to just create a new function in the scope.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/705#issuecomment-45052057
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/705#issuecomment-45052046
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 ha
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/705#issuecomment-45051978
Jenkins, retest 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/944#issuecomment-45051509
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/944#issuecomment-45051510
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15431/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/967#issuecomment-45050122
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15430/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/967#issuecomment-45050121
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. If
Github user kanzhang commented on the pull request:
https://github.com/apache/spark/pull/944#issuecomment-45049954
@rxin rebased just now. Thanks!
---
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/944#issuecomment-45049924
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/944#issuecomment-45049915
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 ha
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/961#discussion_r13370405
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/ReceiverInputDStream.scala
---
@@ -74,7 +74,7 @@ abstract class ReceiverInputDStream[T:
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/967#issuecomment-45049523
@ankurdave in general new methods should be fine wrt compatibility.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/719
---
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 enabl
Github user sujeetv commented on a diff in the pull request:
https://github.com/apache/spark/pull/960#discussion_r13370140
--- Diff: ec2/spark_ec2.py ---
@@ -538,7 +543,12 @@ def get_num_disks(instance_type):
"c3.xlarge": 2,
"c3.2xlarge": 2,
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/967#issuecomment-45048620
Actually, never mind about the backporting -- apparently introducing new
methods breaks compatibility.
---
If your project is set up for it, you can reply to this email
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/967#issuecomment-45048487
@rxin This is a binary-compatible bugfix, so it should also be backported
into branch-1.0.
---
If your project is set up for it, you can reply to this email and have yo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/967#issuecomment-45048510
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/967#issuecomment-45048505
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 ha
GitHub user ankurdave opened a pull request:
https://github.com/apache/spark/pull/967
[SPARK-1552] Fix type comparison bug in {map,outerJoin}Vertices
In GraphImpl, mapVertices and outerJoinVertices use a more efficient
implementation when the map function conserves vertex attribute
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/966#issuecomment-45047729
Can one of the admins verify this patch?
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/944#issuecomment-45047703
Yeah this is one case where we need to manually add excludes. The reason is
MIMA doesn't have proper support for package privacy, and our work-around can't
handle the cas
GitHub user nevillelyh opened a pull request:
https://github.com/apache/spark/pull/966
[MLLIB] set RDD names in ALS
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nevillelyh/spark master
Alternatively you can review and apply t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/952#issuecomment-45046963
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15429/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/952#issuecomment-45046961
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/956#issuecomment-45046694
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15425/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/965#issuecomment-45046692
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/965#issuecomment-45046695
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15426/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/956#issuecomment-45046691
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 have
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/948#issuecomment-45046324
@marmbrus Agree. I'll try to remove the `lazy` qualifier of
`SchemaRDD.queryExecution` since the field object itself is rather cheap (all
of its fields are lazy), and th
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/944#issuecomment-45046091
BTW due to two recent PR merges, I think this no longer merges cleanly. Do
you mind updating the PR to rebase it to master? Thanks.
---
If your project is set up for it, yo
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/944#issuecomment-45046041
Yea we should just add the rules. I had to work around the same problem
when I removed SerializableHyperLogLog.
---
If your project is set up for it, you can reply to this
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/956#issuecomment-45046006
Can you also add a feature that typing "set abcd" should output the value
of abcd.
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user CrazyJvm commented on the pull request:
https://github.com/apache/spark/pull/952#issuecomment-45045909
thanks, witgo. I think maybe your suggestion is better than my current
solution since we do not need modify shell.
Another problem is that the spark-shell can not r
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/962#discussion_r13368954
--- Diff: core/src/main/scala/org/apache/spark/rdd/HadoopRDD.scala ---
@@ -189,13 +190,18 @@ class HadoopRDD[K, V](
context.stageId, theSplit.index, c
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/952#issuecomment-45045254
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/952#issuecomment-45045240
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/895#issuecomment-45044597
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/895#issuecomment-45044600
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15428/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/895#issuecomment-45044557
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 fe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/895#issuecomment-45044548
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 this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/965
---
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 enabl
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/965#issuecomment-45043894
I merged this in 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 project does not have this fe
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/895#issuecomment-45043900
@pwendell This is okay to review.
The failure above seems unrelated.
I will also add these configurations to the configuration docs.
---
If your project is
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/895#issuecomment-45043814
Jenkins, test this again.
---
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/895#issuecomment-45043590
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15427/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/895#issuecomment-45043589
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/897#issuecomment-45043516
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/897#issuecomment-45043520
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15422/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/705#issuecomment-45043515
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/963#issuecomment-45043517
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15421/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/965#issuecomment-45043527
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/963#issuecomment-45043513
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/895#issuecomment-45043512
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 this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/705#issuecomment-45043518
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15423/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/965#issuecomment-45043509
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/897#issuecomment-45043519
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15424/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/897#issuecomment-45043514
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/895#issuecomment-45043534
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 fe
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/952#issuecomment-45043437
```scala
// Global defaults. These should be keep to minimum to avoid confusing
behavior.
master = Option(master).getOrElse {
if (System.getenv
1 - 100 of 438 matches
Mail list logo
