Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6855
---
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 adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6843#discussion_r32672177
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -313,3 +313,131 @@ case class
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6346#discussion_r32672235
--- Diff: python/pyspark/mllib/feature.py ---
@@ -525,6 +526,41 @@ def fit(self, data):
return Word2VecModel(jmodel)
+class
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6827#issuecomment-112943729
Ok I'm going to merge this into master 1.4 after addressing the comments
myself thanks.
---
If your project is set up for it, you can reply to this email and have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6702
---
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/6858#issuecomment-112947982
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/6858#issuecomment-112947951
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6456#issuecomment-112948921
Sorry slipped on this a little. I'm merging it into master now thanks Ryan!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user hntd187 commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-112948835
@avulanov How about I take the read and you take the write?
In an ideal world we should be able to take the implementation from here
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6761#issuecomment-11294
@acidghost Thanks for the updated PR! I'll try to make a closer pass soon.
In the meantime, unit tests do sound great. I think one of the best ways to
test
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6456
---
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6826#discussion_r32674770
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonRDD.scala
---
@@ -425,6 +425,11 @@ private[spark] object PythonRDD extends Logging {
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6796#issuecomment-112954757
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 feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6796#issuecomment-112955352
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/5659#issuecomment-112960569
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6853#issuecomment-112960343
[Test build #35063 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35063/consoleFull)
for PR 6853 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6852#issuecomment-112939012
[Test build #35050 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35050/console)
for PR 6852 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5426
---
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/6827
---
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/6788#issuecomment-112946911
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112946764
[Test build #35054 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35054/console)
for PR 6831 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-112946829
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6788#issuecomment-112946946
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/6758#issuecomment-112946978
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/6826#discussion_r32674187
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonRDD.scala
---
@@ -425,6 +425,11 @@ private[spark] object PythonRDD extends Logging {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5659#issuecomment-112952353
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6796#issuecomment-112957441
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/6796#issuecomment-112957431
[Test build #35062 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35062/console)
for PR 6796 at commit
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6852#issuecomment-112962440
@srowen We have been seeing some flakiness in this test in our daily master
builds in Jenkins. So these fixes LGTM.
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6863#issuecomment-112966905
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/6863#issuecomment-112966838
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 tarekauel commented on the pull request:
https://github.com/apache/spark/pull/6804#issuecomment-112995751
@chenghao-intel First of all thanks for all your comments and thoughts. I
guess the `UTF8String` is only used in SPARK SQL, isn't it? Because of that I
think the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6782#issuecomment-112997625
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/6782#issuecomment-112997616
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 adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/6782#issuecomment-112997633
@chenghao-intel
---
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/6394#issuecomment-112997631
Yes, I think so, still need to do some small modifications, but I think the
most of this patch is settled, any comment is greatly appreciated.
---
If your project is
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-112997746
Just left one problem as you mentioned to consider the locality of pending
request, currently I didn't address this problem, I'd like to move it to
another PR.
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6865#issuecomment-113000277
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 jerryshao commented on the pull request:
https://github.com/apache/spark/pull/5632#issuecomment-113000205
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6865#issuecomment-113000238
[Test build #35067 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35067/console)
for PR 6865 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5632#issuecomment-113004270
[Test build #35070 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35070/console)
for PR 5632 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6782#issuecomment-113003741
[Test build #35072 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35072/consoleFull)
for PR 6782 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5632#issuecomment-113004310
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/6854#issuecomment-113007125
[Test build #35075 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35075/consoleFull)
for PR 6854 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113009538
[Test build #35077 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35077/consoleFull)
for PR 6864 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113009510
The last build failure looks pretty weird: a large part of Jenkins build
log output are replaced by tens of thousands of lines of integer triples, and
none of the 5
Github user chiyingyunhua commented on the pull request:
https://github.com/apache/spark/pull/5654#issuecomment-113010184
请é®ï¼æ使ç¨spark1.3.1çsparksqlä¸dataframeçä¸ä¸ªsaveastableæ¹æ³åäºä¸ä¸ªdataframeï¼ä½æ¯ç¨hive读çæ¶ååºéäºFailed
with exception
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5632#issuecomment-113010215
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5632#issuecomment-113010241
[Test build #35080 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35080/consoleFull)
for PR 5632 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/5632#issuecomment-113010111
This failure is not caused by your code; it's due to a bug in a change that
we made to the test runner script. I'm going to push a hotfix now or will
revert in the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5632#issuecomment-113010224
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/6859#issuecomment-113010770
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/5632#issuecomment-113010777
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/6859#issuecomment-113010791
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/6854#issuecomment-113010774
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113010743
OK, found out that those integers are printed by `SQLQuerySuite.test script
transform for stderr`. See [Josh's comment] [1].
---
If your project is set up for it,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5632#issuecomment-113010793
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/5632#issuecomment-113013520
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/5632#issuecomment-113013491
[Test build #35080 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35080/console)
for PR 5632 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6863#discussion_r32694426
--- Diff: docs/streaming-kafka-integration.md ---
@@ -74,15 +74,15 @@ Next, we discuss how to use this approach in your
streaming application.
[Maven
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5643#issuecomment-113015474
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/6859#discussion_r32694593
--- Diff:
core/src/main/scala/org/apache/spark/ui/scope/RDDOperationGraph.scala ---
@@ -165,12 +165,12 @@ private[ui] object RDDOperationGraph extends Logging
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-113015368
@JoshRosen Can you take a look at this PR, especially the SparkListener
updates.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5643#issuecomment-113015485
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 XuTingjun commented on the pull request:
https://github.com/apache/spark/pull/6839#issuecomment-113015490
@andrewor14, I have updated the title and code, please have a look again,
thanks.
---
If your project is set up for it, you can reply to this email and have your
Github user koeninger commented on the pull request:
https://github.com/apache/spark/pull/6863#issuecomment-113022865
Yeah, the spacing in that document in general is a mess (mix of tabs and
spaces, some 2 spaces between sentences, etc). I cleaned it up somewhat. Also
further fixed
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6854#issuecomment-113024090
[Test build #35082 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35082/console)
for PR 6854 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6854#issuecomment-113024097
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5694#discussion_r32697343
--- Diff: dev/run-tests.py ---
@@ -0,0 +1,536 @@
+#!/usr/bin/env python2
+
+#
+# Licensed to the Apache Software Foundation (ASF) under one
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6782#issuecomment-113038547
LGTM except some minor issues.
---
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 MechCoder commented on the pull request:
https://github.com/apache/spark/pull/6346#issuecomment-113040170
@davies Thanks. Do you want me to look at any particular PR if it needs
reviews?
---
If your project is set up for it, you can reply to this email and have your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6346
---
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/6788
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/6346#issuecomment-113043984
Any comments on any PR or JIRA are welcome, 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
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6869#issuecomment-113044642
cc @liancheng @rxin @JoshRosen
---
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/6869#issuecomment-113044641
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/6869#issuecomment-113044658
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 davies opened a pull request:
https://github.com/apache/spark/pull/6869
[WIP] remove expensive api from InternalRow
This is a follow up PR for #6792, to use narrow down the APIs in
InternalRow (remove those expensive ones).
You can merge this pull request into a Git
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/6870
[SPARK-8425][Core][WIP] Add blacklist mechanism in task scheduling
This is a proposal to add blacklist mechanism in Spark for better
scheduling task to avoid running on the bad enough executors,
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6831#issuecomment-113045048
LGTM, so I'm going to merge this into master. Thanks @lianhuiwang!
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6775#discussion_r32700753
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -313,3 +312,78 @@ case class StringLength(child:
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6775#discussion_r32700846
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/FunctionRegistry.scala
---
@@ -172,7 +174,7 @@ object FunctionRegistry {
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6867#issuecomment-113039790
merged into master, 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
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6346#issuecomment-113039940
LGTM, merging into 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6867
---
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/6782#issuecomment-113041436
[Test build #35091 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35091/consoleFull)
for PR 6782 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6839#issuecomment-113042025
Thanks, I'm merging this into master 1.4.
---
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/6826#discussion_r32700117
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonRDD.scala
---
@@ -425,6 +425,11 @@ private[spark] object PythonRDD extends Logging {
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/6746#issuecomment-113044527
Hmm. The present supported format is coherent with that done in Scala.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6746#issuecomment-113044436
There could be many different formats in a string, so I'm not sure which
format we should support. It's better to be done by user.
cc @mengxr
---
If your
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6775#discussion_r32700683
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DataFrameFunctionsSuite.scala ---
@@ -85,6 +86,52 @@ class DataFrameFunctionsSuite extends QueryTest {
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6831
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/6746#issuecomment-113045261
I see, in order to have similar functionality as Scala, we should do
similar things as in #685, having MLUtils.loadLabelPoints() ...
---
If your project is set up for
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6746#issuecomment-113045343
Also the format we used here, should match with LabelPoint.__str__(), then
it can load the RDD after saveAsTextFile.
---
If your project is set up for it, you can reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6870#issuecomment-113046185
[Test build #35093 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35093/consoleFull)
for PR 6870 at commit
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6607#discussion_r32691426
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/scheduler/SchedulerSuite.scala
---
@@ -0,0 +1,91 @@
+/*
+ * Licensed to the Apache
Github user adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6775#discussion_r32691936
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DataFrameFunctionsSuite.scala ---
@@ -85,6 +86,52 @@ class DataFrameFunctionsSuite extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6775#issuecomment-112999257
[Test build #35069 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35069/consoleFull)
for PR 6775 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6865#issuecomment-113001333
I think we can close this since it's subsumed by #6866.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6866#issuecomment-113002194
[Test build #35071 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35071/consoleFull)
for PR 6866 at commit
201 - 300 of 714 matches
Mail list logo
