Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11895#issuecomment-200687758
**[Test build #54008 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54008/consoleFull)**
for PR 11895 at commit
Github user tejasapatil commented on the pull request:
https://github.com/apache/spark/pull/11723#issuecomment-200687233
@rxin : I would really like to have this PR in trunk. As things stand, for
anyone using their own scheduler, one has to maintain a patch over open source
release
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/11895#discussion_r57277319
--- Diff:
sql/core/src/test/java/test/org/apache/spark/sql/JavaDataFrameSuite.java ---
@@ -303,27 +305,42 @@ public void pivot() {
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/11895#discussion_r57277180
--- Diff:
sql/core/src/test/java/test/org/apache/spark/sql/JavaDataFrameSuite.java ---
@@ -303,27 +305,42 @@ public void pivot() {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11895#issuecomment-200684929
**[Test build #54007 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54007/consoleFull)**
for PR 11895 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11925#issuecomment-200682795
**[Test build #54006 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54006/consoleFull)**
for PR 11925 at commit
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11723#discussion_r57276779
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/ExternalClusterManagerSuite.scala
---
@@ -0,0 +1,65 @@
+/*
+ * Licensed to the Apache
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11723#discussion_r57276711
--- Diff: dev/.rat-excludes ---
@@ -98,3 +98,4 @@ LZ4BlockInputStream.java
spark-deps-.*
.*csv
.*tsv
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11723#discussion_r57276691
--- Diff:
core/src/test/resources/META-INF/services/org.apache.spark.scheduler.ExternalClusterManager
---
@@ -0,0 +1 @@
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11723#discussion_r57276663
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/ExternalClusterManager.scala ---
@@ -0,0 +1,62 @@
+/*
+ * Licensed to the Apache
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11723#discussion_r57276660
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/ExternalClusterManager.scala ---
@@ -0,0 +1,62 @@
+/*
+ * Licensed to the Apache
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11723#discussion_r57276618
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/ExternalClusterManagerSuite.scala
---
@@ -0,0 +1,65 @@
+/*
+ * Licensed to the Apache
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200679647
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200679645
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11922#issuecomment-200679591
**[Test build #54005 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54005/consoleFull)**
for PR 11922 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200679249
**[Test build #53998 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53998/consoleFull)**
for PR 11916 at commit
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11723#discussion_r57276344
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/ExternalClusterManager.scala ---
@@ -0,0 +1,62 @@
+/*
+ * Licensed to the Apache
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11723#discussion_r57276268
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -149,7 +149,14 @@ private[spark] class Executor(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11809#issuecomment-200678468
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11809#issuecomment-200678465
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11809#issuecomment-200677948
**[Test build #53999 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53999/consoleFull)**
for PR 11809 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11824#issuecomment-200677903
**[Test build #54004 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54004/consoleFull)**
for PR 11824 at commit
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11723#discussion_r57276201
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -149,7 +149,14 @@ private[spark] class Executor(
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11723#discussion_r57276211
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -149,7 +149,14 @@ private[spark] class Executor(
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11854#issuecomment-200676690
The motivation of this function `distinctSet` is to obtain the uniqueness
constraint from the child operators. The output of `Distinct`, `Intersect`,
`Except`, and
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11824#issuecomment-200676764
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 tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11723#discussion_r57276135
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -2443,8 +2443,34 @@ object SparkContext extends Logging {
"in the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11928#issuecomment-200676208
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11928#issuecomment-200676206
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11928#issuecomment-200675840
**[Test build #54000 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54000/consoleFull)**
for PR 11928 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11927#issuecomment-200674840
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11927#issuecomment-200675269
**[Test build #2676 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2676/consoleFull)**
for PR 11927 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11929#issuecomment-200674607
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
GitHub user wangyang1992 opened a pull request:
https://github.com/apache/spark/pull/11929
[SPARK-13934][SQL] fixed table identifier
## What changes were proposed in this pull request?
Table identifier that starts in a form of scientific notation (like 1e34)
will throw an
Github user andrewor14 closed the pull request at:
https://github.com/apache/spark/pull/11923
---
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11923#issuecomment-200672391
I'm going to close this for now since we reverted the original patch.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/11927#discussion_r57275794
--- Diff: core/src/main/scala/org/apache/spark/rdd/PipedRDD.scala ---
@@ -205,6 +206,8 @@ private[spark] class PipedRDD[T: ClassTag](
private
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/9#issuecomment-200672196
@jkbradley Sure, I'll leave it here and check back later. :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11927#discussion_r57275342
--- Diff: core/src/main/scala/org/apache/spark/rdd/PipedRDD.scala ---
@@ -205,6 +206,8 @@ private[spark] class PipedRDD[T: ClassTag](
private def
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/11621#discussion_r57275251
--- Diff: python/pyspark/ml/wrapper.py ---
@@ -223,3 +223,20 @@ def _call_java(self, name, *args):
sc = SparkContext._active_spark_context
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11854#issuecomment-200665778
**[Test build #54003 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54003/consoleFull)**
for PR 11854 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11854#issuecomment-200665098
Added a function `distinctSet` into `QueryPlan`. This function will return
the set of attributes whose combination can uniquely identify a row. Maybe I
should
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11926#issuecomment-200663369
**[Test build #54002 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54002/consoleFull)**
for PR 11926 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11926#issuecomment-200663292
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
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/11926#issuecomment-200663281
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11926#issuecomment-200663293
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11926#issuecomment-200663135
**[Test build #53997 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53997/consoleFull)**
for PR 11926 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/10399#issuecomment-200662936
ping @marmbrus please let me know if this is ok for you now, thanks.
---
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/11920#issuecomment-200662831
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11920#issuecomment-200662829
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11920#issuecomment-200662764
**[Test build #53995 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53995/consoleFull)**
for PR 11920 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11928#issuecomment-200662362
**[Test build #54000 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54000/consoleFull)**
for PR 11928 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11578#issuecomment-200662364
**[Test build #54001 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54001/consoleFull)**
for PR 11578 at commit
GitHub user jkbradley opened a pull request:
https://github.com/apache/spark/pull/11928
[SPARK-10691][ML] Make LogisticRegressionModel, LinearRegressionModel
evaluate() public
## What changes were proposed in this pull request?
Made evaluate method public. Fixed
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/11621#discussion_r57274042
--- Diff: python/pyspark/ml/classification.py ---
@@ -231,6 +232,210 @@ def intercept(self):
"""
return
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-200660263
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-200660261
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-200660184
**[Test build #53993 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53993/consoleFull)**
for PR 9893 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11892#issuecomment-200660088
**[Test build #2675 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2675/consoleFull)**
for PR 11892 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-200659749
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-200659748
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-200659678
**[Test build #53996 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53996/consoleFull)**
for PR 11301 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/11832#issuecomment-200659606
LGTM Ready to merge?
---
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/11796#issuecomment-200659325
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11796#issuecomment-200659327
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11796#issuecomment-200658889
**[Test build #53992 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53992/consoleFull)**
for PR 11796 at commit
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/11832#discussion_r57273260
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/HashingTF.scala ---
@@ -53,9 +65,10 @@ class HashingTF(val numFeatures: Int) extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11892#issuecomment-200657826
**[Test build #2675 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2675/consoleFull)**
for PR 11892 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/11892#issuecomment-200657678
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 this
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9#issuecomment-200657397
@yinxusen Well, I still think we should support initial models, and
hopefully some of the code (like unit tests) would be reusable. Feel free to
leave this open
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/11855#issuecomment-200656539
I'll go ahead and merge this with 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-200653658
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-200653654
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-200653343
**[Test build #53994 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53994/consoleFull)**
for PR 11301 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11927#issuecomment-200652969
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
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11557#discussion_r57272561
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/parser/ng/PlanParserSuite.scala
---
@@ -0,0 +1,408 @@
+/*
+ * Licensed to the
GitHub user tejasapatil opened a pull request:
https://github.com/apache/spark/pull/11927
[SPARK-14110] [CORE] PipedRDD to print the command ran on non zero exit
## What changes were proposed in this pull request?
In case of failure in subprocess launched in PipedRDD, the
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11557#discussion_r57272283
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/parser/ng/PlanParserSuite.scala
---
@@ -0,0 +1,408 @@
+/*
+ * Licensed to the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11809#issuecomment-200650936
**[Test build #53999 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53999/consoleFull)**
for PR 11809 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11557#discussion_r57272248
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/parser/ng/PlanParserSuite.scala
---
@@ -0,0 +1,408 @@
+/*
+ * Licensed to the
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/11809#issuecomment-200650254
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 jerryshao commented on the pull request:
https://github.com/apache/spark/pull/11885#issuecomment-200646933
OK, thanks a lot for your explanation :smile: .
---
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 falaki commented on a diff in the pull request:
https://github.com/apache/spark/pull/11724#discussion_r57272004
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/csv/CSVInferSchema.scala
---
@@ -108,14 +109,38 @@ private[csv] object
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11557#discussion_r57271935
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/parser/ng/ExpressionParserSuite.scala
---
@@ -0,0 +1,494 @@
+/*
+ * Licensed
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/11885#issuecomment-200644697
As I've said above, spark does *not* use the Hadoop configuration from the
classpath in the executors. It uses the hadoop configuration broadcast from the
driver.
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11557#discussion_r57271566
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/parser/ng/ExpressionParserSuite.scala
---
@@ -0,0 +1,494 @@
+/*
+ * Licensed
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200643122
**[Test build #53998 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53998/consoleFull)**
for PR 11916 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11916#issuecomment-200641412
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11557#discussion_r57271266
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/parser/ng/ExpressionParserSuite.scala
---
@@ -0,0 +1,494 @@
+/*
+ * Licensed
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11926#issuecomment-200640177
**[Test build #53997 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53997/consoleFull)**
for PR 11926 at commit
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/11885#issuecomment-200640251
Thanks a lot for your explanation.
I'm not sure if I understand correctly, currently we will add
`/etc/hadoop` into the classpath by default for AM and
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11557#discussion_r57271242
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/parser/ng/ExpressionParserSuite.scala
---
@@ -0,0 +1,494 @@
+/*
+ * Licensed
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/11926
[SPARK-14111][SQL] Correct output nullability with constraints for logical
plans
## What changes were proposed in this pull request?
JIRA: https://issues.apache.org/jira/browse/SPARK-14111
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/11885#issuecomment-200638308
There's no "several paths". Spark will broadcast the hadoop configs before
running tasks and use that in the executors, so Spark won't use whatever is in
the executor's
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11904#issuecomment-200636903
thanks, merging to 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
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/11885#issuecomment-200637889
My concern is about hadoop related configurations, who will take the
precedence if several paths have different configurations.
---
If your project is set up for
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11904#issuecomment-200637711
Thank you!
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/11885#issuecomment-200635731
I don't think there's any harm in using the archive everywhere; it's
currently only used in the AM mostly as an optimization, since it wasn't really
used in the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-200635290
**[Test build #53996 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/53996/consoleFull)**
for PR 11301 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/11722#issuecomment-200637490
I come up another approach for this problem. Close this now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
1 - 100 of 863 matches
Mail list logo
