Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2263#discussion_r17096828
--- Diff: conf/hive-log4j.properties.template ---
@@ -0,0 +1,84 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2263#discussion_r17096824
--- Diff: conf/hive-log4j.properties.template ---
@@ -0,0 +1,84 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2263#discussion_r17096833
--- Diff: conf/hive-log4j.properties.template ---
@@ -0,0 +1,84 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2263#issuecomment-54410818
I know that `hive-log4j.properties.template` is copied from Hive, but this
file really makes me itchy...
Besides that, I think these are generally good to
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/2262#discussion_r17096863
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -97,6 +97,7 @@ case class Limit(limit: Int, child:
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/2262#discussion_r17096919
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -97,6 +97,7 @@ case class Limit(limit: Int, child: SparkPlan)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2214#issuecomment-54411030
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19735/consoleFull)**
after a configured wait of `120m`.
---
If your project
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2263#discussion_r17097013
--- Diff: conf/hive-log4j.properties.template ---
@@ -0,0 +1,84 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/2262#discussion_r17097010
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -164,6 +165,7 @@ case class Limit(limit: Int, child:
Github user watermen commented on the pull request:
https://github.com/apache/spark/pull/2216#issuecomment-54411613
@tdas When i use the function of updateStateByKey, and the number of key
are more than 10. I want to watch all values of keys to make sure the code is
right.
---
If
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2246#issuecomment-54412078
I have changed the code, now `compatibleType` and `findTightestCommonType`
looks different.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2246#issuecomment-54412046
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19754/consoleFull)
for PR 2246 at commit
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/2262#discussion_r17097138
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -97,6 +97,7 @@ case class Limit(limit: Int, child:
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2250#issuecomment-54412947
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 this
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/2258#discussion_r17097268
--- Diff: docs/sql-programming-guide.md ---
@@ -263,15 +300,195 @@ for teenName in teenNames.collect():
/div
-**Note that Spark SQL
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/2269
[Build] Removed -Phive-thriftserver since this profile has been removed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/liancheng/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2096#issuecomment-54413134
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19749/consoleFull)
for PR 2096 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2250#issuecomment-54413324
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19755/consoleFull)
for PR 2250 at commit
Github user li-zhihui commented on a diff in the pull request:
https://github.com/apache/spark/pull/1616#discussion_r17097313
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -317,13 +317,58 @@ private[spark] object Utils extends Logging {
}
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/2258#discussion_r17097430
--- Diff: python/pyspark/sql.py ---
@@ -287,7 +287,7 @@ class StructType(DataType):
Spark SQL StructType
-The data type
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2216#issuecomment-54414169
Ahh okay. As @ScrapCodes said, this can be done pretty easily with
foreachRDD, but I can see how this makes it a tad bit convenient. I am okay to
add this. However, please
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/2229#discussion_r17097578
--- Diff: bin/compute-classpath.sh ---
@@ -63,7 +63,7 @@ else
assembly_folder=$ASSEMBLY_DIR
fi
-num_jars=$(ls $assembly_folder | grep
GitHub user sarutak opened a pull request:
https://github.com/apache/spark/pull/2270
[SPARK-3399] Test for PySpark should ignore HADOOP_CONF_DIR and
YARN_CONF_DIR
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sarutak/spark
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/2229#discussion_r17097618
--- Diff: sbt/sbt-launch-lib.bash ---
@@ -190,5 +190,5 @@ runAlternateBoot() {
local bootpropsfile=$1
shift
addJava
GitHub user ankurdave opened a pull request:
https://github.com/apache/spark/pull/2271
[HOTFIX] [SPARK-3400] Revert 9b225ac fix GraphX EdgeRDD zipPartitions
9b225ac3072de522b40b46aba6df1f1c231f13ef has been causing GraphX tests
to fail nondeterministically, which is blocking
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/2271#issuecomment-54416619
@rxin @liancheng I'm going to merge this immediately.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2229#issuecomment-54416704
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19760/consoleFull)
for PR 2229 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2271#issuecomment-54416983
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 have this feature
enabled
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2271
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2251#issuecomment-54417319
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19746/consoleFull)
for PR 2251 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2250#issuecomment-54420383
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19755/consoleFull)
for PR 2250 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2271#issuecomment-54420735
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 have this feature
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2250#issuecomment-54421851
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2250#issuecomment-54422284
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19764/consoleFull)
for PR 2250 at commit
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/2273
[SPARK-3353] parent stage should have lower stage id.
Previously parent stages had higher stage id, but parent stages are
executed first. This pull request changes the behavior so parent stages would
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/2096#issuecomment-54423889
Jenkins, retest this please.
This was a problematic commit in GraphX which I just
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2263#issuecomment-54424705
Thanks for reviewing this, you're right, the log4j configuration template
mainly for Hive usage (particularly for MapReduce), I've updated the code and
keep it
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2246#issuecomment-54424875
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19754/consoleFull)
for PR 2246 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2272#issuecomment-54425075
Jenkins, 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
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/2246#issuecomment-54425114
I hate graphx :(
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/2272#issuecomment-54425102
LGTM pending Jenkins.
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/2246#issuecomment-54425261
Don't hate it :)
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/2246#issuecomment-54425279
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/2273#issuecomment-54425345
Jenkins, 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 this
Github user ChengXiangLi commented on the pull request:
https://github.com/apache/spark/pull/2194#issuecomment-54425347
we hit the binary incompatibilities error here, i already annotated new
added methods as DeveloperApi, do i miss something here?
---
If your project is set up for
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2272#issuecomment-54425969
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19767/consoleFull)
for PR 2272 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2273#issuecomment-54426303
Jenkins, add to whitelist.
---
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/2273#issuecomment-54426801
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19770/consoleFull)
for PR 2273 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2178#issuecomment-54429684
Ok I updated the PR to set spark.shuffle.spill.compress and
spark.shuffle.compress consistent for now.
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2178#issuecomment-54430749
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19771/consoleFull)
for PR 2178 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2229#issuecomment-54431089
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19760/consoleFull)
for PR 2229 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2265#issuecomment-54431508
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19772/consoleFull)
for PR 2265 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2216#issuecomment-54431716
@watermen @tdas PS do you think this can be added to the Java API too? it
needs to be a new additional method not a change to the existing one. Worth the
extra method,
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/2270#issuecomment-54431833
Jenkins, 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
GitHub user sryza opened a pull request:
https://github.com/apache/spark/pull/2274
SPARK-2978. Transformation with MR shuffle semantics
I didn't add this to the transformations list in the docs because it's kind
of obscure, but would be happy to do so if others think it would be
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2250#issuecomment-54432073
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19764/consoleFull)
for PR 2250 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2274#issuecomment-54432312
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19773/consoleFull)
for PR 2274 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2274#issuecomment-54432465
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19773/consoleFull)
for PR 2274 at commit
Github user chutium commented on a diff in the pull request:
https://github.com/apache/spark/pull/1612#discussion_r17101449
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/jdbc/JdbcResultSetRDD.scala ---
@@ -0,0 +1,72 @@
+/*
+ * Licensed to the Apache Software
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2268#issuecomment-54432582
@witgo The release process does this, I believe. I don't think you need to
open a PR for this especially before 1.1.0 is released
---
If your project is set up for it,
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2267#discussion_r17101501
--- Diff: spark2 ---
@@ -0,0 +1 @@
+Some changes
--- End diff --
What is this file? accidentally added?
---
If your project is set up for
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1612#issuecomment-54433054
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19775/consoleFull)
for PR 1612 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2267#discussion_r17101578
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/PairDStreamFunctions.scala
---
@@ -396,6 +396,26 @@ class PairDStreamFunctions[K,
Github user sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/1388#discussion_r17101588
--- Diff: python/pyspark/mllib/regression.py ---
@@ -66,6 +66,9 @@ def weights(self):
def intercept(self):
return self._intercept
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1612#issuecomment-54433211
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19775/consoleFull)
for PR 1612 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1388#issuecomment-54433745
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19776/consoleFull)
for PR 1388 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2274#issuecomment-54434254
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19777/consoleFull)
for PR 2274 at commit
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2035#issuecomment-54434388
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
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1567#issuecomment-54434357
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
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2261#issuecomment-54434450
Jenkins doesn't work?
---
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/2261#issuecomment-54434457
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2273#issuecomment-54434600
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19770/consoleFull)
for PR 2273 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2261#issuecomment-54434920
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19780/consoleFull)
for PR 2261 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1567#issuecomment-54434939
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19781/consoleFull)
for PR 1567 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-54434954
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19778/consoleFull)
for PR 1616 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2035#issuecomment-54434901
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19779/consoleFull)
for PR 2035 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2273#issuecomment-54435580
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19768/consoleFull)
for PR 2273 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2272#issuecomment-54436390
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19767/consoleFull)
for PR 2272 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1612#issuecomment-54436556
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19782/consoleFull)
for PR 1612 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2178#issuecomment-54438651
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19771/consoleFull)
for PR 2178 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2265#issuecomment-54441308
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19772/consoleFull)
for PR 2265 at commit
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2268#issuecomment-54441310
@srowen I agree with you. But
[SparkContext.SPARK_VERSION](https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/SparkContext.scala#L1300)
has
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2270#issuecomment-54441790
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19774/consoleFull)
for PR 2270 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1388#issuecomment-54441755
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19776/consoleFull)
for PR 1388 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2274#issuecomment-54443225
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19777/consoleFull)
for PR 2274 at commit
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/2035#issuecomment-54443276
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 and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2246#issuecomment-54443352
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19769/consoleFull)
for PR 2246 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1616#issuecomment-5557
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19778/consoleFull)
for PR 1616 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1567#issuecomment-54449841
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19781/consoleFull)
for PR 1567 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2261#issuecomment-54451537
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19780/consoleFull)
for PR 2261 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2035#issuecomment-54452278
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19779/consoleFull)
for PR 2035 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1612#issuecomment-54453005
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19782/consoleFull)
for PR 1612 at commit
Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-54457835
@JoshRosen @andrewor14 I have update comment. has any question for it?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user BigCrunsh commented on the pull request:
https://github.com/apache/spark/pull/2231#issuecomment-54459193
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
Github user BigCrunsh commented on the pull request:
https://github.com/apache/spark/pull/2231#issuecomment-54459168
@mengxr: done ;)
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2231#issuecomment-54460133
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19783/consoleFull)
for PR 2231 at commit
Github user jerry86 commented on the pull request:
https://github.com/apache/spark/pull/1156#issuecomment-54463121
@pwendell I think this seems to be the best choice at this moment. Not sure
if Amazon has made or will make any improvements to PVM that fits PySpark.
---
If your
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2194#issuecomment-54465038
I am looking at this. Mima check should have excluded those methods.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2231#issuecomment-54473057
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19783/consoleFull)
for PR 2231 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2247#issuecomment-54474045
Perhaps we should have a separate discussion on the dev mailing list as
what we consider public interfaces? That way everyone is in agreement or at
least is following
1 - 100 of 253 matches
Mail list logo
