Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18953
**[Test build #80869 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80869/testReport)**
for PR 18953 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18986
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/18986
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80868/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18986
**[Test build #80868 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80868/testReport)**
for PR 18986 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18849
If the new flag `DATASOURCE_HIVE_COMPATIBLE` is set to `true` when creating
a table, are we sure it can be `true` forever? Is it a reliable flag we can
trust? Is that possible the `ALTER TABLE`
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18986
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80866/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18986
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/18986
**[Test build #80866 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80866/testReport)**
for PR 18986 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18986
**[Test build #80868 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80868/testReport)**
for PR 18986 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18973
**[Test build #80867 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80867/testReport)**
for PR 18973 at commit
Github user stanzhai commented on the issue:
https://github.com/apache/spark/pull/18986
In MySQL conversion of values from one string type to numeric, will be
compared as floating-point (real) numbers.
[](https://dev.mysql.com/doc/refman/5.7/en/type-conversion.html)
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18968
@dilipbiswal Thanks for comment.
This issue is happened at optimization phase, so I think it is supposed
that we already pass `checkAnalysis`.
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18973
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80863/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18973
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
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18973
**[Test build #80863 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80863/testReport)**
for PR 18973 at commit
Github user facaiy commented on the issue:
https://github.com/apache/spark/pull/18998
cc @yanboliang @WeichenXu123 who I believe are interested in this PR. Could
you take a look please?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18998
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 facaiy opened a pull request:
https://github.com/apache/spark/pull/18998
[SPARK-21748][ML] Migrate the implementation of HashingTF from MLlib to ML
## What changes were proposed in this pull request?
Migrate the implementation of HashingTF from MLlib to ML.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18973
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80864/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18973
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/18973
**[Test build #80864 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80864/testReport)**
for PR 18973 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18986
**[Test build #80866 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80866/testReport)**
for PR 18986 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18953
Hi, @cloud-fan .
Could you review this PR?
---
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 issue:
https://github.com/apache/spark/pull/15435
**[Test build #80865 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80865/testReport)**
for PR 15435 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15435
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80865/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15435
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/18762
---
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 issue:
https://github.com/apache/spark/pull/15435
**[Test build #80865 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80865/testReport)**
for PR 15435 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/18762
Thanks for doing this @aray, 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 holdenk commented on the issue:
https://github.com/apache/spark/pull/18647
Although I'd recommend doing a JIRA.
---
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 holdenk commented on the issue:
https://github.com/apache/spark/pull/18647
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 and wishes so, or if the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18953
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80861/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18953
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/18953
**[Test build #80861 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80861/testReport)**
for PR 18953 at commit
Github user dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/18968
@viirya Hi Simon, many thanks for finding this. Instead of adding the
compensation code in the resolve logic for in-subquery expression can we
consider to move the semantic checking of
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/18896
Thanks for catching this @WeichenXu123! I just added a note about the
intent of test.
---
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 sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/18896#discussion_r134076580
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/classification/LogisticRegressionSuite.scala
---
@@ -1392,6 +1415,61 @@ class LogisticRegressionSuite
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/18896#discussion_r134076552
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/optim/aggregator/LogisticAggregatorSuite.scala
---
@@ -238,8 +238,17 @@ class LogisticAggregatorSuite
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18538
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80862/
Test PASSed.
---
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/18981
Also to be clear pandoc is pretty optional, we want to use for packaging
but in local mode it doesn't really matter. So LGTM pending jenkins.
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18538
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 holdenk commented on the issue:
https://github.com/apache/spark/pull/18981
Thanks for fixing this @dusktreader :) OSError seems to mostly occur when
pandoc is not installed.
I think automatically attempting to install pandoc is more likely to lead
us into
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18538
**[Test build #80862 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80862/testReport)**
for PR 18538 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/18281
Also to be clear, I'm fine with the changes I've suggested being left for a
follow up (but if we do go ahead and merge this without those changes lets make
it an explicit follow up task).
---
If
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/18982#discussion_r134075412
--- Diff: python/pyspark/ml/wrapper.py ---
@@ -118,11 +118,13 @@ def _transfer_params_to_java(self):
"""
Transforms the embedded
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/18982#discussion_r134075445
--- Diff: python/pyspark/ml/tests.py ---
@@ -455,6 +455,14 @@ def test_logistic_regression_check_thresholds(self):
LogisticRegression,
Github user LiShuMing commented on the issue:
https://github.com/apache/spark/pull/18905
Sorry, busy recently, I will update it today...
---
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 holdenk commented on the issue:
https://github.com/apache/spark/pull/18732
cc @HyukjinKwon @BryanCutler
---
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 holdenk commented on the issue:
https://github.com/apache/spark/pull/18970
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 and wishes so, or if the
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/18622
Oh wait sorry I misread that code, it looks like we have this already
wrapped behind in the Spark ML API.
Since we aren't actively working on the Spark MLlib APIs right now I
probably
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/18622
So while we are trying to limit the changes in mllib, we are currently
exposing BinaryClassificationMetrics in the ML models so this makes sense to
expose.
---
If your project is set up for it,
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/17849
LGTM, its certainly sort of an intermediary fix state but making the params
accessible without users having to go through py4j manually is worth while.
I'll leave this over the weekend in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18973
**[Test build #80864 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80864/testReport)**
for PR 18973 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18997
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80859/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18997
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/18997
**[Test build #80859 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80859/testReport)**
for PR 18997 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/17373
We can open a JIRA to track
---
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 issue:
https://github.com/apache/spark/pull/18973
**[Test build #80863 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80863/testReport)**
for PR 18973 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18994
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/18994
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80855/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18538
**[Test build #80862 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80862/testReport)**
for PR 18538 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18994
**[Test build #80855 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80855/testReport)**
for PR 18994 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18953
**[Test build #80861 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80861/testReport)**
for PR 18953 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18953
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18953
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/18953
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80858/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18953
**[Test build #80858 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80858/testReport)**
for PR 18953 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18995
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/18995
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80857/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18995
**[Test build #80857 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80857/testReport)**
for PR 18995 at commit
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/18953#discussion_r134068925
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/orc/OrcQuerySuite.scala ---
@@ -205,38 +220,53 @@ class OrcQuerySuite extends QueryTest
Github user budde commented on the issue:
https://github.com/apache/spark/pull/18029
@yssharma Let me know what you think of my review suggestions. I should be
able to review any updates from here on in a timely manner but you will still
need @brkyvz or another Spark committer to do
Github user budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/18029#discussion_r134068101
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/InitialPosition.scala
---
@@ -0,0 +1,107 @@
+/*
+ * Licensed to the
Github user budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/18029#discussion_r134063427
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/InitialPosition.scala
---
@@ -0,0 +1,107 @@
+/*
+ * Licensed to the
Github user budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/18029#discussion_r134067474
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/KinesisReceiver.scala
---
@@ -148,18 +149,28 @@ private[kinesis] class
Github user budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/18029#discussion_r134063380
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/InitialPosition.scala
---
@@ -0,0 +1,107 @@
+/*
+ * Licensed to the
Github user budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/18029#discussion_r134067523
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/InitialPosition.scala
---
@@ -0,0 +1,107 @@
+/*
+ * Licensed to the
Github user budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/18029#discussion_r134067110
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/KinesisReceiver.scala
---
@@ -148,18 +149,28 @@ private[kinesis] class
Github user budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/18029#discussion_r134067791
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/KinesisInputDStream.scala
---
@@ -308,7 +308,6 @@ object
Github user budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/18029#discussion_r134067693
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/InitialPosition.scala
---
@@ -0,0 +1,107 @@
+/*
+ * Licensed to the
Github user budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/18029#discussion_r134068186
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/InitialPosition.scala
---
@@ -0,0 +1,107 @@
+/*
+ * Licensed to the
Github user budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/18029#discussion_r134067537
--- Diff:
external/kinesis-asl/src/main/scala/org/apache/spark/streaming/kinesis/InitialPosition.scala
---
@@ -0,0 +1,107 @@
+/*
+ * Licensed to the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18538
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80860/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18538
**[Test build #80860 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80860/testReport)**
for PR 18538 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18538
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/18538
**[Test build #80860 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80860/testReport)**
for PR 18538 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18940#discussion_r134058845
--- Diff: core/src/main/scala/org/apache/spark/SparkConf.scala ---
@@ -597,7 +597,8 @@ private[spark] object SparkConf extends Logging {
Github user squito commented on the issue:
https://github.com/apache/spark/pull/16992
been a while so lets run tests again just to check:
Jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/16992#discussion_r134056863
--- Diff: docs/job-scheduling.md ---
@@ -235,7 +235,7 @@ properties:
of the cluster. By default, each pool's `minShare` is 0.
The pool
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18997
**[Test build #80859 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80859/testReport)**
for PR 18997 at commit
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/18997
[SPARK-21788][SS]Handle more exceptions when stopping a streaming query
## What changes were proposed in this pull request?
Add more cases we should view as a normal query stop rather than
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18978
So, one thing I'm a little confused about is: why are there any changes
necessary to the transport library at all?
The transport library abstracts away the concept of users / secrets so that
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18953
**[Test build #80858 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80858/testReport)**
for PR 18953 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18972
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/18972
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80853/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18972
**[Test build #80853 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80853/testReport)**
for PR 18972 at commit
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18940
+1. Any further comments. @vanzin @jiangxb1987
---
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 issue:
https://github.com/apache/spark/pull/18996
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80856/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18996
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/18996
**[Test build #80856 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80856/testReport)**
for PR 18996 at commit
1 - 100 of 359 matches
Mail list logo
