Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-115976114
[Test build #35892 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35892/console)
for PR 6967 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-115976126
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 bryanjj commented on the pull request:
https://github.com/apache/spark/pull/6141#issuecomment-115977592
ok sounds good, I'll close it
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user bryanjj reopened a pull request:
https://github.com/apache/spark/pull/6141
[SPARK-6380] Resolution of equi-join key in post-join projection
create a new method in LogicalPlan for resolving ambiguous references and
wrote an implentation for Project.
handles cases
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-115997708
[Test build #35893 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35893/console)
for PR 6921 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-115997709
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/6950#issuecomment-115999390
@JoshRosen is a better person to check this out.
---
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/7053#issuecomment-115975997
[Test build #967 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/967/console)
for PR 7053 at commit
Github user litao-buptsse commented on the pull request:
https://github.com/apache/spark/pull/7053#issuecomment-115977907
Some unit tests failed. I will review my PR code again.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user JihongMA commented on the pull request:
https://github.com/apache/spark/pull/6297#issuecomment-115977926
while preparing the code change to address review comments. I noticed the
fix for SPARK-8359 is causing issue with decimal type, I put a comment there on
that JIRA and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7054#issuecomment-115984108
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 tszym opened a pull request:
https://github.com/apache/spark/pull/7054
[SPARK-8649] [BUILD] Mapr repository is not defined properly
The previous commiter on this part was @pwendell
The previous url gives 404, the new one seems to be OK.
This patch is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-115997080
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 dragos commented on the pull request:
https://github.com/apache/spark/pull/6903#issuecomment-115999679
@ScrapCodes @mateiz Anything else I can do to get this in?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user bryanjj closed the pull request at:
https://github.com/apache/spark/pull/6141
---
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 bryanjj closed the pull request at:
https://github.com/apache/spark/pull/6141
---
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 litao-buptsse commented on the pull request:
https://github.com/apache/spark/pull/7042#issuecomment-115978366
Scala style tests failed. I will view my code again.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6924#issuecomment-115971724
I've eyeballed the change again and looks like it's consistent with
everyone's intentions. I'll merge after checking that docs build after this
doc-only change.
---
If
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6924
---
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 litao-buptsse commented on the pull request:
https://github.com/apache/spark/pull/7042#issuecomment-115979188
OK. I will try to make a version same as master #7053 for branch-1.4
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/7048#issuecomment-115984726
Thanks for fixing this! `ENUM` is not specified in the Parquet format spec,
but according to parquet-mr 1.7.0, it is only used for converting Avro,
ProtoBuf, and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-115997423
[Test build #35893 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35893/consoleFull)
for PR 6921 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6921#issuecomment-115997110
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 Lewuathe commented on the pull request:
https://github.com/apache/spark/pull/5707#issuecomment-115997683
@jkbradley I'm so sorry for keeping bothering you, but could you check it
again? Thank you.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7056#issuecomment-116005594
[Test build #35894 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35894/consoleFull)
for PR 7056 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7056#issuecomment-116040685
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/7056#issuecomment-116040653
[Test build #35894 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35894/console)
for PR 7056 at commit
Github user litao-buptsse commented on the pull request:
https://github.com/apache/spark/pull/7053#issuecomment-116045509
@srowen I think maybe the first fs param in addResource() is needed,
especially it's useful when doing unit test. I see the
ClientDistributedCacheManagerSuite
Github user uncleGen closed the pull request at:
https://github.com/apache/spark/pull/4135
---
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/7055#issuecomment-116003341
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 litao-buptsse closed the pull request at:
https://github.com/apache/spark/pull/7042
---
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 viirya opened a pull request:
https://github.com/apache/spark/pull/7056
[SPARK-8677][SQL] Fix non-terminating decimal expansion for decimal divide
operation
JIRA: https://issues.apache.org/jira/browse/SPARK-8677
You can merge this pull request into a Git repository by
GitHub user litao-buptsse opened a pull request:
https://github.com/apache/spark/pull/7055
[SPARK-8657] [YARN] Fail to upload conf archive to viewfs
Fail to upload conf archive to viewfs in spark-1.4
JIRA Link: https://issues.apache.org/jira/browse/SPARK-8657
You can merge this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7056#issuecomment-116004905
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/7056#issuecomment-116004882
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 litao-buptsse commented on the pull request:
https://github.com/apache/spark/pull/7042#issuecomment-116004053
I create a clean new PR #7055 (ajust scala code style) for this issue and I
will close this PR. @srowen you can merge this PR to branch-1.4 temporaryly.
In
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/7059#issuecomment-116109310
@cloud-fan Thanks for looking into this, We have some offline discussion
last week, because of the data source API, we have to make InternalRow can be
casted into Row
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/7003#discussion_r33414717
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/InternalRow.scala ---
@@ -19,14 +19,54 @@ package org.apache.spark.sql.catalyst
GitHub user MechCoder opened a pull request:
https://github.com/apache/spark/pull/7058
[SPARK-8679] [PySpark] [MLlib] Default values in Pipeline API should be
immutable
It might be dangerous to have a mutable as value for default param.
e.g
def func(example,
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/7059
[SPARK-8679][SQL] remove dummy java class BaseRow and BaseMutableRow
we can use `abstract class` instead of `trait` for `MutableRow`, and remove
the dummy java row classes. This PR also contains
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/7059#issuecomment-116101231
cc @rxin @davies
I can take over the following internal/external row splitting job if
@davies is too busy recently.
Some thoughts about future
Github user paberline commented on the pull request:
https://github.com/apache/spark/pull/6995#issuecomment-116092604
I want to work on this some more to incorporate the improvement suggestion
I have received.
---
If your project is set up for it, you can reply to this email and
GitHub user hvanhovell opened a pull request:
https://github.com/apache/spark/pull/7057
[SPARK-8638] [SQL] Window Function Performance Improvements
## Description
Performance improvements for Spark Window functions. This PR will also
serve as the basis for moving away from Hive
Github user paberline closed the pull request at:
https://github.com/apache/spark/pull/6995
---
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 lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6990#discussion_r33413900
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -833,8 +833,10 @@ private[spark] class BlockManager(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7057#issuecomment-116114231
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/7059#issuecomment-116114228
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/7058#issuecomment-116114229
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 a diff in the pull request:
https://github.com/apache/spark/pull/7048#discussion_r33414842
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/parquet/CatalystSchemaConverter.scala
---
@@ -178,8 +178,8 @@ private[parquet] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7059#issuecomment-116114520
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/7058#issuecomment-116114519
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116114714
[Test build #35896 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35896/consoleFull)
for PR 7058 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7059#issuecomment-116115057
[Test build #35895 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35895/consoleFull)
for PR 7059 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7057#issuecomment-116115100
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7057#issuecomment-116115023
Jenkins, this is 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7057#issuecomment-116115098
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/7057#issuecomment-116116301
[Test build #35897 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35897/consoleFull)
for PR 7057 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116121629
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 MechCoder commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116121669
jenkins test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116121626
[Test build #35896 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35896/console)
for PR 7058 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116121945
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/7058#issuecomment-116121931
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/7058#issuecomment-116122319
[Test build #35898 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35898/consoleFull)
for PR 7058 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7060#issuecomment-116138794
[Test build #35899 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35899/consoleFull)
for PR 7060 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116173510
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/7004#issuecomment-116173506
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116173172
Jenkins, this is 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7062#issuecomment-116181658
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/7062#issuecomment-116181663
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 JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6936#discussion_r33416662
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -315,6 +315,14 @@ class SparkContext(config: SparkConf) extends Logging
with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7020#issuecomment-116147553
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/7020#issuecomment-116147548
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7020#issuecomment-116147483
Jenkins, this is 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116148896
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/7003#issuecomment-116148941
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 yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/7026#discussion_r33416949
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/client/VersionsSuite.scala ---
@@ -170,5 +180,12 @@ class VersionsSuite extends SparkFunSuite with
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6967#issuecomment-116164101
[Test build #35904 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35904/consoleFull)
for PR 6967 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116164305
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/6936#issuecomment-116164301
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 smartkiwi commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116164420
Python doctests are rather limited in expressiveness, but efficient in
keeping examples bug free in documentation.
Anywhere - here is another patch that works in
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6936#issuecomment-116164424
[Test build #35905 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35905/consoleFull)
for PR 6936 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116164570
Also, to clarify: is this primarily intended to improve the performance of
programs written against the Spark Core API? For Spark SQL + DataFrames, I
think the
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7054#issuecomment-116164685
Jenkins, this is 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7054#issuecomment-116164794
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/7054#issuecomment-116164800
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7054#issuecomment-116164855
[Test build #35906 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35906/consoleFull)
for PR 7054 at commit
Github user JDrit commented on the pull request:
https://github.com/apache/spark/pull/7004#issuecomment-116165233
This was intended to be a performance increase for spark-core with RDDs.
This works separately from spark-avro. I realize that dataframes could also be
used but the goal
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/7061
[SPARK-8683] [SPARK] Depend on mockito-core instead of mockito-all
Spark's tests currently depend on `mockito-all`, which bundles Hamcrest and
Objenesis classes. Instead, it should depend on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7061#issuecomment-116165349
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/7061#issuecomment-116165354
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7061#issuecomment-116165427
[Test build #35907 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35907/consoleFull)
for PR 7061 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116166766
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/7003#issuecomment-116166759
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/7003#issuecomment-116166791
[Test build #35908 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35908/consoleFull)
for PR 7003 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7059#issuecomment-116132934
[Test build #35895 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35895/console)
for PR 7059 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7059#issuecomment-116132999
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/7058#issuecomment-116132214
[Test build #35898 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35898/console)
for PR 7058 at commit
GitHub user brkyvz opened a pull request:
https://github.com/apache/spark/pull/7060
[SPARK-8681] fixed wrong ordering of columns in crosstab
I specifically randomized the test. What crosstab does is equivalent to a
countByKey, therefore if this test fails again for any reason, we
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7050#issuecomment-116146384
Saw confirmation on JIRA that this patch fixes the issue, so I'm going to
merge to master.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7003#issuecomment-116149511
[Test build #35901 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/35901/console)
for PR 7003 at commit
1 - 100 of 208 matches
Mail list logo
