Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14043
**[Test build #61712 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61712/consoleFull)**
for PR 14043 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14033
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/14036
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61706/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14033
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61707/
Test PASSed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14043
Just for reference, what PR or JIRA is this backporting?
---
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 jerryshao commented on the issue:
https://github.com/apache/spark/pull/14043
#13804
---
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 maropu commented on the issue:
https://github.com/apache/spark/pull/14039
@srowen thanks for the comment. Yea, I noticed that and I'm fixing this to
remove only shuffle files generated by `ShuffleExchange`.
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14042
**[Test build #61711 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61711/consoleFull)**
for PR 14042 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14042
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61711/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14042
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 liancheng commented on the issue:
https://github.com/apache/spark/pull/14025
@tdas Would you please to help review streaming example code changes?
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 markhamstra commented on the issue:
https://github.com/apache/spark/pull/14039
Actually, they can be reused -- not in Spark as distributed, but it is an
open question whether reusing shuffle files within Spark SQL is something that
we should be doing and want to support.
Github user WeichenXu123 commented on a diff in the pull request:
https://github.com/apache/spark/pull/14025#discussion_r69417590
--- Diff: docs/configuration.md ---
@@ -1564,8 +1564,8 @@ spark.sql("SET -v").show(n=200, truncate=False)
{% highlight r %}
-#
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14033
**[Test build #61709 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61709/consoleFull)**
for PR 14033 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14033
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61709/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14033
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 liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/14025#discussion_r69415295
--- Diff: docs/configuration.md ---
@@ -1564,8 +1564,8 @@ spark.sql("SET -v").show(n=200, truncate=False)
{% highlight r %}
-#
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14004
**[Test build #61710 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61710/consoleFull)**
for PR 14004 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14004
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61710/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14004
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/14039
**[Test build #61715 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61715/consoleFull)**
for PR 14039 at commit
GitHub user techaddict reopened a pull request:
https://github.com/apache/spark/pull/13334
[SPARK-15576] Add back hive tests blacklisted by SPARK-15539
## What changes were proposed in this pull request?
Add back hive tests blacklisted by SPARK-15539
## How was this
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/13981#discussion_r69422844
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/regression/DecisionTreeRegressorSuite.scala
---
@@ -96,6 +108,15 @@ class DecisionTreeRegressorSuite
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14041
It doesn't work to only keep the 0.10 classes? I was hoping they'd be a
superset of 0.8 for these purposes. Can we skip generating javadoc for one of
them rather than modify the classpath, if
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14029
Merged to master/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
enabled and wishes so,
Github user techaddict commented on the issue:
https://github.com/apache/spark/pull/13334
@andrewor14 I've made the changes, can you take a look now ?
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/13334
**[Test build #61716 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61716/consoleFull)**
for PR 13334 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14029
---
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14033#discussion_r69425803
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/generators.scala
---
@@ -94,6 +94,62 @@ case class UserDefinedGenerator(
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14016
Is this safe to merge for 2.0.0? I don't think Python 2.6 support is
officially gone yet. It seems OK for `master` at least, and you can of course
force a version of Python if needed.
---
If your
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13834
Hm, wait, don't we have a problem where a _fatal_ error is thrown from this
block? now it still waits for the process in the finally block, but will hang
because the stream is not closed. If that's
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/13680#discussion_r69426474
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/benchmark/UnsafeArrayDataBenchmark.scala
---
@@ -0,0 +1,256 @@
+/*
+ * Licensed to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14041
**[Test build #61708 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61708/consoleFull)**
for PR 14041 at commit
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/14033#discussion_r69428234
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/generators.scala
---
@@ -94,6 +94,62 @@ case class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14041
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/61708/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14041
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 dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/14033#discussion_r69428617
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/generators.scala
---
@@ -94,6 +94,62 @@ case class
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/14033#discussion_r69429057
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/generators.scala
---
@@ -94,6 +94,62 @@ case class
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14044
cc @cloud-fan , too.
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/12972
@yhuai Could you please take a look?
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14028
@rxin and @yhuai Could you review this maybe?
---
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/14044
**[Test build #61714 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/61714/consoleFull)**
for PR 14044 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14044
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
301 - 343 of 343 matches
Mail list logo
