Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6902#issuecomment-113525808
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/6902#issuecomment-113525842
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 MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/5081#discussion_r32833024
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Matrices.scala
---
@@ -100,6 +100,50 @@ sealed trait Matrix extends Serializable {
*
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5250#issuecomment-113508330
I think this should be closed now in favor of
https://github.com/apache/spark/pull/5368 right?
---
If your project is set up for it, you can reply to this email and
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/6905
[SPARK-8468][ML] Add param to CrossValidator for choosing whether to
maximize evaulation value
JIRA: https://issues.apache.org/jira/browse/SPARK-8468
You can merge this pull request into a Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-113522886
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/6905#issuecomment-113522885
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/6905#issuecomment-113522827
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 MechCoder commented on the pull request:
https://github.com/apache/spark/pull/5081#issuecomment-113522900
@mengxr Please have a look at https://github.com/apache/spark/pull/6904/
This will help in ruling out some cases with minimum code repetition.
---
If your project is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6904#issuecomment-113522887
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/6904#issuecomment-113522839
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/4055#issuecomment-113523988
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/6902#issuecomment-113526363
[Test build #35270 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35270/consoleFull)
for PR 6902 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6904#issuecomment-113527096
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/6904#issuecomment-113527061
[Test build #35267 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35267/console)
for PR 6904 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113475413
[Test build #35259 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35259/console)
for PR 6864 at commit
Github user BenFradet commented on the pull request:
https://github.com/apache/spark/pull/6845#issuecomment-113474928
As promised, here are the screenshots:
Before:
After:
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113477295
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 BenFradet opened a pull request:
https://github.com/apache/spark/pull/6902
[SPARK-8356][SQL] Reconcile callUDF and callUdf
Deprecates ```callUdf``` in favor of ```callUDF```.
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6685#issuecomment-113494186
[Test build #35264 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35264/consoleFull)
for PR 6685 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6685#issuecomment-113497962
[Test build #35264 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35264/console)
for PR 6685 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6685#issuecomment-113497971
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/6846#issuecomment-113505608
LGTM; do you consider this to resolve SPARK-8389 or is there more coming?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4402#issuecomment-113507059
@ankurdave OK with 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113470297
[Test build #35255 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35255/console)
for PR 4055 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113470330
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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/6832#issuecomment-113480419
I am inclined towards having sed replacement command which is compatible
with POSIX (works both on bsd and GNU). I do not have a BSD system handy right
now. :/ to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6737#issuecomment-113485026
[Test build #35261 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35261/console)
for PR 6737 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6737#issuecomment-113485046
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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/6832#issuecomment-113498883
I am going to give it a shot, if you allow me some time.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user bolkedebruin commented on the pull request:
https://github.com/apache/spark/pull/4064#issuecomment-113505275
@zhzhan @WangTaoTheTonic I just cloned the latest and this issue still
seems to exist. This is on Hadoop 2.6 from HDP 2.2 and Hive 0.14 + Kerberos
---
If your
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6882#discussion_r32825688
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/ScriptTransformation.scala
---
@@ -173,7 +171,20 @@ case class ScriptTransformation(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-113469710
[Test build #35257 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35257/console)
for PR 6262 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-113469734
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 megatron-me-uk commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-113471065
It failed an unrelated 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
Github user suyanNone commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113477240
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/6900#issuecomment-113483119
[Test build #35256 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35256/console)
for PR 6900 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6900#issuecomment-113483148
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 MechCoder commented on the pull request:
https://github.com/apache/spark/pull/6499#issuecomment-113484564
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-113489197
[Test build #35262 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35262/console)
for PR 6039 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6685#issuecomment-113492124
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/6902#issuecomment-113492125
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/5933
---
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/4055#issuecomment-113492123
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5933#discussion_r32822961
--- Diff: docs/sql-programming-guide.md ---
@@ -1258,7 +1258,12 @@ This command builds a new assembly jar that includes
Hive. Note that this Hive a
on
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6846
---
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/6886#issuecomment-113505892
[Test build #934 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/934/consoleFull)
for PR 6886 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6338#issuecomment-113505976
[Test build #935 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/935/consoleFull)
for PR 6338 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6829#issuecomment-113417003
Oh, I didn't realize you wanted to publish the assembly JAR. I don't think
it makes sense to publish assemblies as Maven artifacts. Right? anyone that
uses it via Maven
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113416966
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/4055#issuecomment-113417006
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 qiansl127 commented on the pull request:
https://github.com/apache/spark/pull/6779#issuecomment-113416732
@rxin 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 feature
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/6896#issuecomment-113425855
@srowen, Thank you for your comment.
Yes, it's a developer API for getters, but I think setters should not open
for developers like other setters of this class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6622#issuecomment-113428648
[Test build #35234 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35234/console)
for PR 6622 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113432930
[Test build #35251 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35251/consoleFull)
for PR 4055 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-113435539
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/6039#issuecomment-113435601
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/6262#issuecomment-113435533
[Test build #35252 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35252/console)
for PR 6262 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6899#issuecomment-113435577
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6836#issuecomment-113437053
Build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6836#issuecomment-113437067
Build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6836#issuecomment-113437482
[Test build #35254 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35254/consoleFull)
for PR 6836 at commit
Github user suyanNone commented on a diff in the pull request:
https://github.com/apache/spark/pull/4055#discussion_r32811839
--- Diff: core/src/main/scala/org/apache/spark/MapOutputTracker.scala ---
@@ -305,7 +305,7 @@ private[spark] class MapOutputTrackerMaster(conf:
SparkConf)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113438818
[Test build #35248 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35248/console)
for PR 4055 at commit
Github user nishkamravi2 commented on a diff in the pull request:
https://github.com/apache/spark/pull/6607#discussion_r32812336
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/scheduler/SchedulerSuite.scala
---
@@ -0,0 +1,91 @@
+/*
+ * Licensed to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4055#issuecomment-113438854
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/6898#issuecomment-113443531
[Test build #933 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/933/console)
for PR 6898 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6262#issuecomment-113445723
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/6262#issuecomment-113445706
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/6900#issuecomment-113445724
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/6900#issuecomment-113445699
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 yijieshen commented on the pull request:
https://github.com/apache/spark/pull/6874#issuecomment-113447735
Close by mistake.
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/6896#issuecomment-113447318
A lot of similar stuff was done in 1.3 in SPARK-3288:
https://github.com/apache/spark/commit/3453d578ad9933be6881488c8ca3611e5b686af9
Seems consistent, yeah.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113449360
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 yijieshen commented on the pull request:
https://github.com/apache/spark/pull/6874#issuecomment-113451741
@rxin @cloud-fan , thanks for the detailed reviews.
I've change the implementation in the latest commit, mind review it again?
---
If your project is set up for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6737#issuecomment-113460933
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 srowen opened a pull request:
https://github.com/apache/spark/pull/6901
[SPARK-5836] [DOCS] [STREAMING] Clarify what may cause long-running Spark
apps to preserve shuffle files
Clarify what may cause long-running Spark apps to preserve shuffle files
You can merge this
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5074#discussion_r32817019
--- Diff: docs/programming-guide.md ---
@@ -1090,6 +1090,67 @@ for details.
/tr
/table
+### Shuffle operations
+
+Certain
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-113470039
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/6039#issuecomment-113470067
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/6685#issuecomment-113480003
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/4055#issuecomment-113494092
[Test build #35263 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35263/consoleFull)
for PR 4055 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-113470504
[Test build #35262 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35262/consoleFull)
for PR 6039 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113475454
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/6832#issuecomment-113482545
Yeah me too but I remember being unable to figure it out when I took a shot
at it, and I assume you couldn't either. This at least uses GNU sed
consistently.
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-113489308
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/6901#issuecomment-113491777
[Test build #35260 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35260/console)
for PR 6901 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6901#issuecomment-113491882
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/6902#issuecomment-113491705
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/6902#issuecomment-113498150
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/6499#issuecomment-113390451
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/6499#issuecomment-113390331
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/5717#issuecomment-113390374
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6686#discussion_r32804117
--- Diff: python/pyspark/sql/types.py ---
@@ -56,6 +56,32 @@ def __eq__(self, other):
def __ne__(self, other):
return not
Github user lfrancke commented on the pull request:
https://github.com/apache/spark/pull/6890#issuecomment-113395470
Thanks guys for taking a look and getting this in so fast.
---
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/6822#issuecomment-113395659
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6843#discussion_r32804637
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -307,9 +307,176 @@ case class StringLength(child:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6822#issuecomment-113395672
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 adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/6782#issuecomment-113399141
ping @rxin @marmbrus
---
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/5717#issuecomment-113408241
[Test build #35233 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35233/console)
for PR 5717 at commit
501 - 600 of 1062 matches
Mail list logo
