Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8330#issuecomment-132914544
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8239#issuecomment-132914657
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 rxin opened a pull request:
https://github.com/apache/spark/pull/8332
[SPARK-10100][SQL] Eliminate hash table lookup if there is no grouping key
in aggregation.
This improves performance by ~ 20 - 30% in one of my local test and should
fix the performance regression
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8239#issuecomment-132915845
[Test build #41308 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41308/consoleFull)
for PR 8239 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-132944037
[Test build #41315 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41315/consoleFull)
for PR 7753 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8337#issuecomment-132943886
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/8337#issuecomment-132943897
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/8267#issuecomment-132902489
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/8267#issuecomment-132902482
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 yinxusen commented on the pull request:
https://github.com/apache/spark/pull/8267#issuecomment-132902550
@feynmanliang Conflicts fixed.
---
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/8231#issuecomment-132902943
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/8231#issuecomment-132902952
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/8267#issuecomment-132903027
[Test build #41305 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41305/consoleFull)
for PR 8267 at commit
Github user ellisonbg commented on a diff in the pull request:
https://github.com/apache/spark/pull/8318#discussion_r37554224
--- Diff: python/pyspark/__init__.py ---
@@ -36,6 +36,31 @@
Finer-grained cache persistence levels.
+import os
+import sys
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/8171#issuecomment-133077867
LGTM. Merged into master and branch-1.5. 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8171
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/8267#issuecomment-133078887
@yinxusen Could you split this PR into two? One for the user guide with
example code and Java test suite, which can be merged into 1.5, and one
implements the Python
Github user silasdavis commented on the pull request:
https://github.com/apache/spark/pull/4895#issuecomment-133078691
I am trying to get this re-opened, please see:
https://issues.apache.org/jira/browse/SPARK-3533
I have a prototype implementation that allows you to write
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/8267#discussion_r37555003
--- Diff: python/pyspark/ml/feature.py ---
@@ -30,7 +30,83 @@
'NGram', 'Normalizer', 'OneHotEncoder', 'PolynomialExpansion',
'RegexTokenizer',
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8239#issuecomment-133079190
@davies Does this look ok to you ? If so I think we can add some more tests
later and get this fix in for 1.5
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8033#issuecomment-133079332
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/8033#issuecomment-133079363
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/8239#issuecomment-133079825
LGTM
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8033#issuecomment-133080090
[Test build #41324 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41324/consoleFull)
for PR 8033 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8239
---
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/8308#issuecomment-133080507
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8308#issuecomment-133080468
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 ehnalis commented on the pull request:
https://github.com/apache/spark/pull/8308#issuecomment-133081165
I went through it, also reorganized a method to the front and made method
comments consistent.
---
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/8308#issuecomment-133081814
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8308#issuecomment-133081591
[Test build #41325 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41325/consoleFull)
for PR 8308 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8339#issuecomment-133081915
[Test build #41321 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41321/console)
for PR 8339 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8308#issuecomment-133081841
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8339#issuecomment-133082048
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 a diff in the pull request:
https://github.com/apache/spark/pull/8308#discussion_r37556264
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -716,11 +735,14 @@ class DAGScheduler(
}
}
- /**
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8339#issuecomment-133082051
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/8308#issuecomment-133082301
[Test build #41325 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41325/console)
for PR 8308 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8308#issuecomment-133082327
Test FAILed.
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/8308#issuecomment-133082325
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 project does
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8308#discussion_r37556365
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1162,17 +1190,20 @@ class DAGScheduler(
}
GitHub user adrian-wang opened a pull request:
https://github.com/apache/spark/pull/8331
[SPARK-10130] [SQL] type coercion for IF should have children resolved first
Type coercion for IF should have children resolved first, or we could meet
unresolved exception.
You can merge this
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/8276#discussion_r37501357
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/api/r/SQLUtils.scala
---
@@ -98,27 +98,17 @@ private[r] object SQLUtils {
val bos = new
Github user Lewuathe commented on a diff in the pull request:
https://github.com/apache/spark/pull/8313#discussion_r37503332
--- Diff: python/pyspark/ml/feature.py ---
@@ -775,7 +775,7 @@ def mean(self):
@inherit_doc
-class StringIndexer(JavaEstimator,
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/2475#discussion_r37506459
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/sources/filters.scala ---
@@ -0,0 +1,26 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-132937698
[Test build #41313 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41313/consoleFull)
for PR 7753 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8332#issuecomment-132957220
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/8332#issuecomment-132957219
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/7753#issuecomment-132959310
Test FAILed.
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/7753#issuecomment-132959307
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/7753#issuecomment-132959204
[Test build #41315 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41315/console)
for PR 7753 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8329#issuecomment-132905843
[Test build #41304 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41304/console)
for PR 8329 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8332#issuecomment-132916542
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/8333#issuecomment-132920718
[Test build #41310 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41310/consoleFull)
for PR 8333 at commit
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/8334
[SQL][minor] remove unnecessary class
This class is identical to
`org.apache.spark.sql.execution.datasources.jdbc. DefaultSource` and is not
needed.
You can merge this pull request into a Git
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8334#discussion_r37504712
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DefaultSource.scala
---
@@ -1,64 +0,0 @@
-/*
-* Licensed to the Apache
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/8335#discussion_r37505763
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/TypeUtils.scala
---
@@ -62,10 +63,6 @@ object TypeUtils {
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-132942959
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/7753#issuecomment-132942930
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/8231#discussion_r37498127
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -466,9 +468,9 @@ class Analyzer(
// Find
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8267#issuecomment-132909248
[Test build #41305 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41305/console)
for PR 8267 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8267#issuecomment-132909393
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/8267#issuecomment-132909388
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 chenghao-intel commented on a diff in the pull request:
https://github.com/apache/spark/pull/8331#discussion_r37500033
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/HiveTypeCoercion.scala
---
@@ -640,7 +640,7 @@ object HiveTypeCoercion {
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8273#issuecomment-132912149
Sorry this is too late for merging into branch-1.5. We can consider this
for master (1.6).
---
If your project is set up for it, you can reply to this email and have
Github user zzcclp commented on the pull request:
https://github.com/apache/spark/pull/8273#issuecomment-132911504
will this pr be merged into branch-1.5?I need 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8330#issuecomment-132914457
[Test build #41303 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41303/console)
for PR 8330 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8330#issuecomment-132914542
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/8332#issuecomment-132916969
[Test build #41309 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41309/consoleFull)
for PR 8332 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8333#issuecomment-132924306
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/8333#issuecomment-132924308
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/8333#issuecomment-132924221
[Test build #41310 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41310/console)
for PR 8333 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8335#issuecomment-132931429
[Test build #41312 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41312/consoleFull)
for PR 8335 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/8273#discussion_r37511672
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JdbcUtils.scala
---
@@ -211,8 +221,9 @@ object JdbcUtils extends Logging {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8033#issuecomment-132958178
[Test build #41317 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41317/consoleFull)
for PR 8033 at commit
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8313#discussion_r37513118
--- Diff: python/pyspark/ml/feature.py ---
@@ -775,7 +775,7 @@ def mean(self):
@inherit_doc
-class StringIndexer(JavaEstimator,
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8324#issuecomment-132908870
cc @liancheng can you review this? This is now the only blocker for cutting
1.5-rc.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8324
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/8273#discussion_r37504664
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JdbcUtils.scala
---
@@ -211,8 +221,9 @@ object JdbcUtils extends Logging {
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8325#issuecomment-132932511
LGTM 2
---
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
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/8231#discussion_r37498065
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -466,9 +468,9 @@ class Analyzer(
// Find
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8231#issuecomment-132903317
[Test build #41306 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41306/consoleFull)
for PR 8231 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-132938626
[Test build #41313 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41313/console)
for PR 7753 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-132938645
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/8336#issuecomment-132938620
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/8336#issuecomment-132938575
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/7753#issuecomment-132938647
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/8336
[SPARK-10092] [SQL] Backports #8324 to branch-1.5
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/liancheng/spark spark-10092/for-branch-1.5
GitHub user yanboliang opened a pull request:
https://github.com/apache/spark/pull/8337
[SPARK-9089] [Core] Fallback to another one if some codecs newInstance
throw InvocationTargetException
Fallback to another one if some codecs newInstance throw
InvocationTargetException
You
Github user yjshen closed the pull request at:
https://github.com/apache/spark/pull/8274
---
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/8329#issuecomment-132905934
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/8329#issuecomment-132905933
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/8331#issuecomment-132912493
[Test build #41307 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41307/consoleFull)
for PR 8331 at commit
Github user adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/8331#discussion_r37500152
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/HiveTypeCoercion.scala
---
@@ -640,7 +640,7 @@ object HiveTypeCoercion {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8239#issuecomment-132914797
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/8239#issuecomment-132914826
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/8324#issuecomment-132917425
This LGTM. Although the current interface still needs further refactoring
to unify different table identifier representations, but we can do it in
follow-up PRs.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8231#issuecomment-132925305
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/8231#issuecomment-132925311
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/8231#issuecomment-132925033
[Test build #41306 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41306/console)
for PR 8231 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8334#issuecomment-132925591
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/8334#issuecomment-132925647
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
1 - 100 of 467 matches
Mail list logo
