Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7561#issuecomment-123352359
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 bolkedebruin commented on the pull request:
https://github.com/apache/spark/pull/7489#issuecomment-123366143
@tgravescs I have added a full debug log to the jira issue (SPARK-9019).
For this cluster the job enters accepted state but never running. I don't think
I have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7523
---
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/7397#issuecomment-123373169
[Test build #37956 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37956/consoleFull)
for PR 7397 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7371
---
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/7561#issuecomment-123388415
[Test build #43 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/43/console)
for PR 7561 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7561#issuecomment-123388600
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/7561#issuecomment-123392783
[Test build #37955 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37955/console)
for PR 7561 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/7532#discussion_r35123818
--- Diff:
core/src/main/scala/org/apache/spark/deploy/master/ApplicationInfo.scala ---
@@ -96,6 +109,47 @@ private[spark] class ApplicationInfo(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7480#issuecomment-123370771
[Test build #1149 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1149/consoleFull)
for PR 7480 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/7489#issuecomment-123371110
hmm, perhaps its an interaction with the RM Ha:
15/07/21 16:02:35 INFO client.ConfiguredRMFailoverProxyProvider: Failing
over to rm1
15/07/21 16:02:35
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/4055#discussion_r35121095
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -739,6 +742,88 @@ class DAGSchedulerSuite
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/4055#discussion_r35121106
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -739,6 +742,88 @@ class DAGSchedulerSuite
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7565#issuecomment-123394190
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/7429#issuecomment-123394101
[Test build #37958 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37958/console)
for PR 7429 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7536#issuecomment-123370835
[Test build #37951 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37951/console)
for PR 7536 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7560#issuecomment-123378564
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 GraceH commented on the pull request:
https://github.com/apache/spark/pull/7528#issuecomment-123378688
Thanks @squito.
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/7318#issuecomment-123386484
Hmm okay. Lets leave it as `crosstab` in this PR -- Before the release I'll
try to do one more pass over the API and we can revisit this if required. Other
than the
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7565#issuecomment-123393312
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 have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7528
---
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/7536#issuecomment-123366165
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 squito commented on the pull request:
https://github.com/apache/spark/pull/7528#issuecomment-123369818
yeah, I don't love the idea of adding things w/out tests, but in this case
I suppose its best left for the future. lgtm pending the tests passing
---
If your project
Github user bolkedebruin commented on the pull request:
https://github.com/apache/spark/pull/7489#issuecomment-123377041
True, but SPARK-8988 mentiones that Node Report API is not available in a
secure cluster. Which is not true (my patch basically enables it). So I am -
personally -
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7560#issuecomment-123380341
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/7517#issuecomment-123380348
@jkbradley Isotonic regression expects a single feature instead of a
feature vector. Do we want to make it a `Regressor` and use `featuresCol` as a
param? One common use
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7560#issuecomment-123380296
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/7429#issuecomment-123383741
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/7429#issuecomment-123383681
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/7429#issuecomment-123384128
[Test build #37958 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37958/consoleFull)
for PR 7429 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7561#issuecomment-123392901
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/7565#issuecomment-123394206
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7559#issuecomment-123397022
add to whitelist
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7561#issuecomment-123355527
[Test build #37955 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37955/consoleFull)
for PR 7561 at commit
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/7567#discussion_r35114903
--- Diff: R/pkg/inst/tests/test_sparkSQL.R ---
@@ -21,10 +21,10 @@ context(SparkSQL functions)
# Utility function for easily checking the values
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7397#issuecomment-123369725
[Test build #1148 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1148/console)
for PR 7397 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/7397#issuecomment-123371365
retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7528#issuecomment-123381479
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/7528#issuecomment-123381194
[Test build #37954 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37954/console)
for PR 7528 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/7429#issuecomment-123382351
@coderxiang Could you help review this PR? 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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/7429#issuecomment-123382296
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/7371#issuecomment-123382153
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 harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/7489#issuecomment-123382315
That exception message is misleading. The message catch block assumes the
failure happened because the API is not available but it is because of
security
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7565#issuecomment-123394368
[Test build #37959 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37959/consoleFull)
for PR 7565 at commit
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/6948#issuecomment-123395868
Sounds good,
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7561#issuecomment-123352192
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/7561#issuecomment-123351206
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/7561#issuecomment-123351305
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/7561#issuecomment-123351651
[Test build #43 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/43/consoleFull)
for PR 7561 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7536#issuecomment-123366100
[Test build #42 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/42/console)
for PR 7536 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/7523#issuecomment-123369477
Merging this 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7536#issuecomment-123370978
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/7397#issuecomment-123376608
@piganesh You don't need to make a new PR for updates. You can push new
commits to your remote branch, which you used to create the PR. Please address
@srowen 's comment
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/4055#discussion_r35121122
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -749,7 +834,7 @@ class DAGSchedulerSuite
*| \
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/4055#discussion_r35121200
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/DAGSchedulerSuite.scala ---
@@ -17,6 +17,8 @@
package org.apache.spark.scheduler
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/4055#discussion_r35121783
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -487,8 +487,8 @@ private[spark] class TaskSetManager(
// a
Github user yjshen commented on the pull request:
https://github.com/apache/spark/pull/7365#issuecomment-123396367
More comments 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 project does not have this
Github user bolkedebruin commented on the pull request:
https://github.com/apache/spark/pull/7489#issuecomment-123396052
@harishreedharan your SPARK-8988 trace looks very much like (or is exactly
the same) as mine when testing on a CDH 5.4 cluster. With my patch the token is
added
Github user CodingCat commented on a diff in the pull request:
https://github.com/apache/spark/pull/7532#discussion_r35173556
--- Diff:
core/src/main/scala/org/apache/spark/deploy/client/AppClient.scala ---
@@ -256,4 +272,33 @@ private[spark] class AppClient(
endpoint =
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/7337#discussion_r35173552
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tuning/TrainValidationSplit.scala ---
@@ -0,0 +1,178 @@
+/*
+ * Licensed to the Apache Software
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/7337#discussion_r35173547
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tuning/TrainValidationSplit.scala ---
@@ -0,0 +1,178 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7512#issuecomment-123525589
[Test build #38007 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38007/consoleFull)
for PR 7512 at commit
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/6054#discussion_r35174305
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/PowerIterationClustering.scala
---
@@ -152,7 +152,28 @@ class PowerIterationClustering
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/6054#discussion_r35174307
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/PowerIterationClustering.scala
---
@@ -213,6 +234,29 @@ object PowerIterationClustering
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7564#issuecomment-123534982
**[Test build #37990 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37990/console)**
for PR 7564 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7564#issuecomment-123535090
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/7337#issuecomment-123539941
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/7337#issuecomment-123539981
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/7274#issuecomment-123548432
[Test build #38019 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38019/consoleFull)
for PR 7274 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7581#issuecomment-123548392
[Test build #38018 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38018/consoleFull)
for PR 7581 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7458#issuecomment-123558966
[Test build #38023 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38023/consoleFull)
for PR 7458 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/7458#issuecomment-123559602
I will merge this one once it passes jenkins to unblock other work. If you
have any comments to this, feel free to leave them at here. I will address them
in a follow-up
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7480#issuecomment-123561145
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/7567#issuecomment-123561274
**[Test build #38009 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38009/console)**
for PR 7567 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7480#issuecomment-123561237
[Test build #38028 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38028/consoleFull)
for PR 7480 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7480#issuecomment-123561157
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/7582#issuecomment-123561073
[Test build #38026 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38026/consoleFull)
for PR 7582 at commit
Github user chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/7533#discussion_r35181361
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringOperations.scala
---
@@ -356,6 +358,92 @@ case class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7458#issuecomment-123562244
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 adrian-wang reopened a pull request:
https://github.com/apache/spark/pull/6988
[WIP] [SPARK-8176] [SPARK-8197] [SQL] Udf to_date/ trunc
I'll add unit test/function registry/codegen after #6782 get in.
You can merge this pull request into a Git repository by running:
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/7584#discussion_r35183469
--- Diff: R/pkg/inst/tests/test_sparkSQL.R ---
@@ -664,10 +664,10 @@ test_that(column binary mathfunctions, {
expect_equal(collect(select(df,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7580#issuecomment-123526078
[Test build #38008 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38008/consoleFull)
for PR 7580 at commit
Github user dusenberrymw commented on the pull request:
https://github.com/apache/spark/pull/7554#issuecomment-123526084
@mengxr Thanks for the thoughts! I'll trim this PR down to just the Python
wrappers, and then open another JIRA up for further discussion on adding a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7580#issuecomment-123526251
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/7579#issuecomment-123526235
[Test build #37998 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37998/console)
for PR 7579 at commit
Github user CodingCat commented on a diff in the pull request:
https://github.com/apache/spark/pull/7532#discussion_r35173745
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -1387,8 +1374,6 @@ class SparkContext(config: SparkConf) extends Logging
with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7208#issuecomment-123527415
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/7576#issuecomment-123527437
[Test build #1151 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1151/consoleFull)
for PR 7576 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7208#issuecomment-123527425
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/7567#issuecomment-123532059
[Test build #37997 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37997/console)
for PR 7567 at commit
Github user yjshen commented on a diff in the pull request:
https://github.com/apache/spark/pull/7365#discussion_r35175062
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/Cast.scala
---
@@ -418,51 +418,518 @@ case class Cast(child: Expression,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7580#issuecomment-123531919
[Test build #38011 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38011/console)
for PR 7580 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7580#issuecomment-123531926
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/7567#issuecomment-123532304
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 nishkamravi2 commented on a diff in the pull request:
https://github.com/apache/spark/pull/7274#discussion_r35176367
--- Diff: core/src/main/scala/org/apache/spark/deploy/master/Master.scala
---
@@ -543,59 +544,108 @@ private[master] class Master(
* multiple
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7578#issuecomment-123544537
[Test build #38016 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/38016/consoleFull)
for PR 7578 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7578#issuecomment-123552016
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/7578#issuecomment-123552029
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/7573#issuecomment-123560226
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 cloud-fan opened a pull request:
https://github.com/apache/spark/pull/7583
[SQL][minor] remove literal in agg group expressions during analysis
a follow-up of https://github.com/apache/spark/pull/4169
You can merge this pull request into a Git repository by running:
1 - 100 of 1149 matches
Mail list logo
