Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13459
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
enabled and wishes so, or if
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/14473
@ZunwenYou Would you mind addressing the comments in the JIRA first? Adding
a new optimization algorithm to an API that is now deprecated definitely
warrants more high level discussion before code
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13459
**[Test build #63253 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63253/consoleFull)**
for PR 13459 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14503
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 project does not have this
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/13701
@davies I improved the test case by adding a SQL metrics. Please take a
look. Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/12753
@vanzin Thanks for looking into this, I have resolved the conflicts.
---
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 issue:
https://github.com/apache/spark/pull/14500
**[Test build #63242 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63242/consoleFull)**
for PR 14500 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14232
@f7753 I think just listing the message types here is not super useful.
Yes, new messages were added and not mentioned in the documentation, but then
adding just "foo is used by bar" doesn't really
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14500
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63242/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14500
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14500
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63243/
Test FAILed.
---
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/14155#discussion_r73623489
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -229,10 +230,8 @@ case class AlterTableSetPropertiesCommand(
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/14155#discussion_r73623449
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -229,10 +230,8 @@ case class AlterTableSetPropertiesCommand(
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9571#discussion_r73623442
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -667,6 +710,123 @@ private[history] class FsHistoryProvider(conf:
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9571#discussion_r73624122
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -667,6 +700,90 @@ private[history] class FsHistoryProvider(conf:
Github user clockfly commented on the issue:
https://github.com/apache/spark/pull/14497
+1
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14501
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14501
**[Test build #63249 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63249/consoleFull)**
for PR 14501 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14501
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63249/
Test PASSed.
---
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/14450#discussion_r73632453
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/datasources/parquet/SpecificParquetRecordReaderBase.java
---
@@ -204,7 +205,8 @@
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14491
Oh, this is only about streaming examples. I can look at those in a
separate PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/12800
@atokhy that's a little weird. The examples module should be inheriting the
guava shading from the parent pom. I have a 1.6 build locally (with patches, so
I'll check the official package tomorrow)
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13680#discussion_r73638020
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/UnsafeArrayData.java
---
@@ -25,30 +25,36 @@
import
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14502
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 project does not have this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13701
**[Test build #63254 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63254/consoleFull)**
for PR 13701 at commit
GitHub user shiv4nsh opened a pull request:
https://github.com/apache/spark/pull/14503
[#SPARK-16911] Fix the links in the programming guide
## What changes were proposed in this pull request?
Fix the broken links in the programming guide of the Graphx Migration and
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9571#discussion_r73624337
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -667,6 +710,123 @@ private[history] class FsHistoryProvider(conf:
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9571#discussion_r73624345
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -667,6 +710,123 @@ private[history] class FsHistoryProvider(conf:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14499
**[Test build #63241 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63241/consoleFull)**
for PR 14499 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14499
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14499
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63241/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14467
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14467
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63248/
Test PASSed.
---
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14445
thanks. merging to master and 2.0!
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/12819
**[Test build #63252 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63252/consoleFull)**
for PR 12819 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12819
**[Test build #63252 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63252/consoleFull)**
for PR 12819 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/14155#discussion_r73622711
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/internal/HiveSerDe.scala ---
@@ -42,8 +41,7 @@ object HiveSerDe {
HiveSerDe(
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/9571
A few minor things left.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14500
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14500
**[Test build #63246 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63246/consoleFull)**
for PR 14500 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14500
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63246/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12819
**[Test build #63251 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63251/consoleFull)**
for PR 12819 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/14155#discussion_r73633166
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/createDataSourceTables.scala
---
@@ -275,238 +269,21 @@ case class
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13428#discussion_r73636023
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -891,10 +891,12 @@ private[spark] object SparkSubmitUtils {
val
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13428#discussion_r73636009
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -891,10 +891,12 @@ private[spark] object SparkSubmitUtils {
val
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12819
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12819
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63252/
Test PASSed.
---
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14155#discussion_r73644259
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/createDataSourceTables.scala
---
@@ -275,238 +269,21 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14155
**[Test build #63257 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63257/consoleFull)**
for PR 14155 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14483
---
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 issue:
https://github.com/apache/spark/pull/14498
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63240/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14498
**[Test build #63240 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63240/consoleFull)**
for PR 14498 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14498
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14497
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14497
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63238/
Test PASSed.
---
Github user skonto commented on the issue:
https://github.com/apache/spark/pull/11157
How about the rest of the ports, what would happen to them in that case?
We will have only one executor per job right? Right now I get conflicts
without the isolator in my local tests.
In
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/14500#discussion_r73619320
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -389,6 +389,50 @@ case class TruncateTableCommand(
}
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/14109#discussion_r73643402
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -862,27 +873,30 @@ class LinearRegressionSummary
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14482
@gatorsmile how about keep working on them after this PR is merged?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14482
@cloud-fan Sure, will do. 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 feature
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14155#discussion_r73644536
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveClientImpl.scala
---
@@ -374,20 +373,7 @@ private[hive] class HiveClientImpl(
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14155#discussion_r73644517
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveMetastoreCatalog.scala ---
@@ -70,64 +69,16 @@ private[hive] class
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14155#discussion_r73644322
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -506,76 +495,16 @@ object DDLUtils {
}
/**
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14482#discussion_r73643735
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -420,45 +420,40 @@ private[sql] abstract class
Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/14109
@sethah In my opinion, I think using `@transient lazy val` is okay since
there are only two places dereferencing the `lazy val`, and we don't use it in
the tight loop. LGTM except one small
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14482
**[Test build #63256 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63256/consoleFull)**
for PR 14482 at commit
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/14109#discussion_r73644694
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/LinearRegression.scala ---
@@ -862,27 +873,30 @@ class LinearRegressionSummary
Github user shiv4nsh closed the pull request at:
https://github.com/apache/spark/pull/14493
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
Adding #13248
---
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
Github user davies commented on the issue:
https://github.com/apache/spark/pull/14487
LGTM, merging 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 this feature
enabled
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13506
@kevinyu98 Could you update the PR and fix merge conflicts? 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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14113
This is not contained in https://github.com/apache/spark/pull/14482. Should
I leave it open? or you will merge it into the PR?
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14113
**[Test build #63237 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63237/consoleFull)**
for PR 14113 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13950
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 project does not have this feature
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13680#discussion_r73565692
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/util/UnsafeArraySuite.scala
---
@@ -18,27 +18,131 @@
package
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/14308
This has been updated since fixing the errors in Java @srowen @MLnick . I
know most of these changes are trivial, but will hopefully make some of the
examples easier to follow. Thanks!
---
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/12753
Sorry this has been forgotten for so long. I think instead of adding a new
way of referencing variables, it might be better to use the new code I'm adding
in #14468; that way it would be easier to
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14113
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 feature
enabled and wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12913
**[Test build #63228 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63228/consoleFull)**
for PR 12913 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12913
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12913
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63228/
Test PASSed.
---
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/14258
I see - So I was thinking that we could merge this into master as well as
its not going to fail any tests or affect any users building SparkR from source
-- I dont think we make any promises about
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14464
---
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 issue:
https://github.com/apache/spark/pull/14239
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14428
**[Test build #63236 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63236/consoleFull)**
for PR 14428 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14495
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63230/
Test PASSed.
---
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/13907
This is not contained in https://github.com/apache/spark/pull/14482. Should
I leave it open? Or should I fix the conflict after
https://github.com/apache/spark/pull/14482 is merged?
---
If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13950
**[Test build #63232 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63232/consoleFull)**
for PR 13950 at commit
Github user mgummelt commented on the issue:
https://github.com/apache/spark/pull/11157
So I hate to ask for another significant change to this PR, but it strikes
me that the source of most of the complexity here is partitioning an offer
around a port so we can reuse the rest of the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13950
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63232/
Test PASSed.
---
GitHub user nchammas opened a pull request:
https://github.com/apache/spark/pull/14496
[SPARK-16772] [Python] [Docs] Fix API doc references to UDFRegistration +
Update "important classes"
## Proposed Changes
* Update the list of "important classes" in `pyspark.sql` to
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/14482#discussion_r73568017
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -420,45 +420,40 @@ private[sql] abstract class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13950
**[Test build #63232 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63232/consoleFull)**
for PR 13950 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/11228
@jeanlyn do you mind updating the PR to solve conflicts? 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 nchammas commented on the issue:
https://github.com/apache/spark/pull/14496
cc @rxin - Follow-on to #14393.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14487
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/11127
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
enabled and wishes so, or if the
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
Adding #9866
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14239
**[Test build #63235 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63235/consoleFull)**
for PR 14239 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14469
**[Test build #63234 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63234/consoleFull)**
for PR 14469 at commit
301 - 400 of 468 matches
Mail list logo
