Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4653#issuecomment-74775239
[Test build #27660 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27660/consoleFull)
for PR 4653 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4664#issuecomment-74781824
[Test build #27662 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27662/consoleFull)
for PR 4664 at commit
GitHub user ilganeli opened a pull request:
https://github.com/apache/spark/pull/4665
SPARK-5570: No docs stating that `new
SparkConf().set(spark.driver.memory, ...) will not work
I've updated documentation to reflect true behavior of this setting in
client vs. cluster mode.
You
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4662
---
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/4667#issuecomment-74798165
Test PASSed.
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/4611#issuecomment-74799888
[Test build #27670 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27670/consoleFull)
for PR 4611 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4337#issuecomment-74802183
[Test build #27671 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27671/consoleFull)
for PR 4337 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4611#issuecomment-74806519
[Test build #27670 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27670/consoleFull)
for PR 4611 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4662#issuecomment-74771232
[Test build #27659 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27659/consoleFull)
for PR 4662 at commit
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/4639#discussion_r24867218
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala ---
@@ -165,8 +165,10 @@ case class CreateMetastoreDataSourceAsSelect(
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/4660#issuecomment-74794927
This LGTM Josh - thanks for giving this such a thorough look.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4660
---
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 CodingCat commented on the pull request:
https://github.com/apache/spark/pull/2851#issuecomment-74798631
Hi, @squito , thanks for the further comments
I have addressed them and also replied under some of them
The snapshots was uploaded,
I will
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4639
---
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 chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/4506#issuecomment-74803371
/cc @marmbrus @rxin @yhuai I noticed that we have added the
`dataFrameEagerAnalysis` in `SQLConf`, probably we also need to update the `def
table` code for using
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4629#issuecomment-74776721
Test PASSed.
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/4667#issuecomment-74789295
[Test build #27665 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27665/consoleFull)
for PR 4667 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4667#issuecomment-74797312
[Test build #614 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/614/consoleFull)
for PR 4667 at commit
Github user dondrake commented on the pull request:
https://github.com/apache/spark/pull/4666#issuecomment-74799310
@davies 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
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/4562#issuecomment-74803640
Thank you @yhuai , I am closing this PR. :)
---
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 chenghao-intel closed the pull request at:
https://github.com/apache/spark/pull/4562
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4668#issuecomment-74805857
[Test build #27669 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27669/consoleFull)
for PR 4668 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4668#issuecomment-74805860
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/4611#issuecomment-74806525
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/4663
[SPARK-5875][SQL]logical.Project should not be resolved if it contains
aggregates or generators
https://issues.apache.org/jira/browse/SPARK-5875 has a case to reproduce
the bug and explain the root
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4641#issuecomment-74782325
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/4641#issuecomment-74782316
[Test build #27658 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27658/consoleFull)
for PR 4641 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4639#issuecomment-74789292
[Test build #27666 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27666/consoleFull)
for PR 4639 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3781#issuecomment-74795803
[Test build #27668 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27668/consoleFull)
for PR 3781 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4666#issuecomment-74800097
[Test build #613 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/613/consoleFull)
for PR 4666 at commit
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/4634#issuecomment-74774029
If I understand correctly, the need is for an operator with an optional
map-side combine. The
alternative is to force the user to choose between `groupByKey` and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4663#issuecomment-74779809
[Test build #27661 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27661/consoleFull)
for PR 4663 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4629
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/4662#issuecomment-74791922
Hey @brkyvz thanks for this, I'm going to merge it. I might remove Spark
Packages-specific comments. While it's great that this will work well with
Spark packages, I
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4668#issuecomment-74798447
[Test build #27669 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27669/consoleFull)
for PR 4668 at commit
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/4602#issuecomment-74801565
/cc @marmbrus @yhuai Any comment on this?
---
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/3781#issuecomment-74803198
Test PASSed.
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/3781#issuecomment-74803108
[Test build #27667 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27667/consoleFull)
for PR 3781 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3781#issuecomment-74803195
[Test build #27668 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27668/consoleFull)
for PR 3781 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3781#issuecomment-74803111
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/4337#issuecomment-74808529
Test PASSed.
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/4337#issuecomment-74808524
[Test build #27671 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27671/consoleFull)
for PR 4337 at commit
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/4639#discussion_r24867096
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveContext.scala ---
@@ -61,6 +61,21 @@ class HiveContext(sc: SparkContext) extends
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4655
---
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/4665#issuecomment-74782476
[Test build #27663 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27663/consoleFull)
for PR 4665 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4666#issuecomment-74788241
[Test build #613 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/613/consoleFull)
for PR 4666 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/4521#issuecomment-74788155
@dondrake Because we need to cut 1.3-RC1 now, I create another PR for
master and 1.3, see #4666
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4664#issuecomment-74792015
Test PASSed.
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/4664#issuecomment-74792004
[Test build #27662 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27662/consoleFull)
for PR 4664 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4639#issuecomment-74797547
[Test build #27666 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27666/consoleFull)
for PR 4639 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4639#issuecomment-74797549
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/4666#issuecomment-74799115
Test PASSed.
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/4666#issuecomment-74799108
[Test build #27664 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27664/consoleFull)
for PR 4666 at commit
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/4662#issuecomment-74770805
Adding spark-packages as a repo broke one test. Pushing update once I make
sure it passes it locally.
---
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/4662#issuecomment-74770780
[Test build #27656 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27656/consoleFull)
for PR 4662 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/4521#issuecomment-74773330
The `long` in JVM will be converted into `int` in Python by Pyrolite, this
change sounds reasonable.
`long` in Python is actually BigInteger, it's much slower
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4653#issuecomment-74786133
Test PASSed.
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/4653#issuecomment-74786127
[Test build #27660 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27660/consoleFull)
for PR 4653 at commit
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/4666
[SPARK-5722] [SQL] [PySpark] infer int as LongType
The `int` is 64-bit on 64-bit machine (very common now), we should infer it
as LongType for it in Spark SQL.
Also, LongType in SQL will
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4665#issuecomment-74791514
[Test build #27663 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27663/consoleFull)
for PR 4665 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4665#issuecomment-74791522
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/4660#issuecomment-74795986
I pushed a a51fc7ef9adb6a41c4857918217f800858fced2c hotfix to roll back a
bit of code cleanup that I did which added a `getOrElseUpdate` call, since this
might have a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4667#issuecomment-74798160
[Test build #27665 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27665/consoleFull)
for PR 4667 at commit
GitHub user tmyklebu opened a pull request:
https://github.com/apache/spark/pull/4668
Avoid deprecation warnings in JDBCSuite.
This pull request replaces calls to deprecated methods from
`java.util.Date` with near-equivalents in `java.util.Calendar`.
You can merge this pull
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/4653#issuecomment-74774366
Jenkins, test this pleas.e
---
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/4659
---
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/4666#issuecomment-74788669
[Test build #27664 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27664/consoleFull)
for PR 4666 at commit
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/4667
[SPARK-5878] fix DataFrame.repartition() in Python
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davies/spark repartition
Alternatively you
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4667#issuecomment-74788828
[Test build #614 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/614/consoleFull)
for PR 4667 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4663#issuecomment-74790118
[Test build #27661 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27661/consoleFull)
for PR 4663 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4663#issuecomment-74790128
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/3781#issuecomment-74795129
@srowen Thank you for picking up this PR. I've changed the
`shutdownCallback` to be a simple volatile variable.
---
If your project is set up for it, you can reply to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3781#issuecomment-74795273
[Test build #27667 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27667/consoleFull)
for PR 3781 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4663
---
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/4506#issuecomment-74802654
[Test build #27672 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27672/consoleFull)
for PR 4506 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4629#issuecomment-74776715
[Test build #27657 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27657/consoleFull)
for PR 4629 at commit
GitHub user brkyvz opened a pull request:
https://github.com/apache/spark/pull/4664
[SPARK-5507] Added documentation for BlockMatrix
Docs for BlockMatrix. @mengxr
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/brkyvz/spark
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/4639#discussion_r24867128
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveMetastoreCatalog.scala ---
@@ -499,24 +499,69 @@ private[hive] class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4662#issuecomment-74783070
[Test build #27659 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27659/consoleFull)
for PR 4662 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4662#issuecomment-74783079
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/4562#issuecomment-74788801
@chenghao-intel can you close it? It is has been fixed by #4655.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/4629#issuecomment-74789577
Thanks for adding the test.
LGTM, so I'm going to merge this into `master` (1.4.0) and `branch-1.3`
(1.3.0). Thanks!
---
If your project is set up for it,
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/4611#issuecomment-74800315
Thank you @srowen , I've updated the script, seems much simpler.
Appreciated if you can confirm the change under OS X, sorry, I don't have
machine with OS X.
Github user dbtsai commented on the pull request:
https://github.com/apache/spark/pull/4593#issuecomment-74805610
Sorry for the late reply since I'm traveling recently. My concern is that
will this cause caching twice in the new ML api? For example, in
Github user MechCoder commented on a diff in the pull request:
https://github.com/apache/spark/pull/4654#discussion_r24877024
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/GaussianMixture.scala ---
@@ -168,16 +182,26 @@ class GaussianMixture private (
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/4602#issuecomment-74807564
@chenghao-intel After another look of the code, I think it may be better to
remove aliases from the `generator`. Then, `MultiAlias` can be used to assign
the names to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4671#issuecomment-74822968
Test PASSed.
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/4671#issuecomment-74822964
[Test build #27675 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27675/consoleFull)
for PR 4671 at commit
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/4670
[Minor] [SQL] Cleans up DataFrame variable names and toDF() calls
Although we've migrated to the DataFrame API, lots of code still uses `rdd`
or `srdd` as local variable names. This PR tries to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4669#issuecomment-74811554
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4670#issuecomment-74812750
[Test build #27674 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27674/consoleFull)
for PR 4670 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/4670#issuecomment-74812701
cc @rxin
---
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 yhuai opened a pull request:
https://github.com/apache/spark/pull/4671
[SPARK-4903][SQL]Backport the bug fix for SPARK-4903
The original fix was a part of
https://issues.apache.org/jira/browse/SPARK-4912 (commit
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/4231#issuecomment-74819739
Thanks ! Looking forward to learn lot's more
---
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 nitin2goyal opened a pull request:
https://github.com/apache/spark/pull/4669
[SPARK-5880][SQL] Change log level of pruned batch's statistics string
Change log level of pruned batch's statistics string in Spark SQL in-memory
columnar store
You can merge this pull
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/4670#issuecomment-74824183
Thanks for doing this.
---
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/4506#issuecomment-74809281
[Test build #27672 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27672/consoleFull)
for PR 4506 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4506#issuecomment-74809284
Test PASSed.
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/4671#issuecomment-74814762
[Test build #27675 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/27675/consoleFull)
for PR 4671 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4670
---
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
1 - 100 of 389 matches
Mail list logo
