Github user janewangfb commented on a diff in the pull request:
https://github.com/apache/spark/pull/18975#discussion_r134847542
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/SQLQuerySuite.scala
---
@@ -2040,4 +2040,83 @@ class SQLQuerySuite extends
Github user janewangfb commented on a diff in the pull request:
https://github.com/apache/spark/pull/18975#discussion_r134845802
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/SQLQuerySuite.scala
---
@@ -2040,4 +2040,83 @@ class SQLQuerySuite extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16774
**[Test build #81047 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81047/testReport)**
for PR 16774 at commit
Github user janewangfb commented on a diff in the pull request:
https://github.com/apache/spark/pull/18975#discussion_r134845628
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkSqlParser.scala ---
@@ -1509,4 +1509,84 @@ class SparkSqlAstBuilder(conf: SQLConf)
Github user janewangfb commented on a diff in the pull request:
https://github.com/apache/spark/pull/18975#discussion_r134844461
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/InsertIntoDataSourceDirCommand.scala
---
@@ -0,0 +1,67 @@
+/*
+ *
Github user janewangfb commented on a diff in the pull request:
https://github.com/apache/spark/pull/18975#discussion_r134843683
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/InsertIntoDataSourceDirCommand.scala
---
@@ -0,0 +1,67 @@
+/*
+ *
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16774
**[Test build #81046 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81046/testReport)**
for PR 16774 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/19021
---
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 janewangfb commented on a diff in the pull request:
https://github.com/apache/spark/pull/18975#discussion_r134842881
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkSqlParser.scala ---
@@ -1509,4 +1509,84 @@ class SparkSqlAstBuilder(conf: SQLConf)
Github user janewangfb commented on a diff in the pull request:
https://github.com/apache/spark/pull/18975#discussion_r134842831
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkSqlParser.scala ---
@@ -1509,4 +1509,84 @@ class SparkSqlAstBuilder(conf: SQLConf)
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18645
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81037/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18645
**[Test build #81037 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81037/testReport)**
for PR 18645 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/19021
Thanks! Merging to master.
---
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/18645
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 janewangfb commented on a diff in the pull request:
https://github.com/apache/spark/pull/18975#discussion_r134842420
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala
---
@@ -359,6 +359,18 @@ case class
Github user poplav commented on the issue:
https://github.com/apache/spark/pull/16087
@barrybecker4 Following the trail of this issue...What is the solution for
many columns rather than the workaround for chunking? Thanks!
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18958
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/18958
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81038/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18958
**[Test build #81038 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81038/testReport)**
for PR 18958 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/18964
> I also notice that Spark RPC by default uses java native serialization,
even a verifying endpoint exist or not request would cost 1K of payload size,
not to mention some other real logic
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18281
**[Test build #81045 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81045/testReport)**
for PR 18281 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/19027
I like this approach @HyukjinKwon :D!
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18368
Set.
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18368
Hi, @gatorsmile .
Could you set @aokolnychyi as an `Assignee` and `Fix Versions` at
https://issues.apache.org/jira/browse/SPARK-21102? Thanks!
---
If your project is set up for it, you
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18962
Sorry, you are right we talked about both there. I was just thinking of
the hadoop not supporting it case. Still agree to split out to another jira.
---
If your project is set up for it, you
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19018
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/19018
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81041/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19018
**[Test build #81041 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81041/testReport)**
for PR 19018 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18317
**[Test build #81044 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81044/testReport)**
for PR 18317 at commit
Github user sitalkedia closed the pull request at:
https://github.com/apache/spark/pull/18317
---
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
GitHub user sitalkedia reopened a pull request:
https://github.com/apache/spark/pull/18317
[SPARK-21113][CORE] Read ahead input stream to amortize disk IO cost â¦
Profiling some of our big jobs, we see that around 30% of the time is being
spent in reading the spill files from
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19016
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81040/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19016
**[Test build #81040 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81040/testReport)**
for PR 19016 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19016
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/18962
> If we don't then we need to conditionalize and only do for for HDFS or
other hadoop supported filesystems.
I thought in the previous discussion we chose to treat that as a separate
issue
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/17849
Thanks @holdenk!
---
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/18281
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/18281
**[Test build #81043 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81043/testReport)**
for PR 18281 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18281
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81043/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18281
**[Test build #81043 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81043/testReport)**
for PR 18281 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18317
**[Test build #81042 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81042/testReport)**
for PR 18317 at commit
Github user sitalkedia commented on the issue:
https://github.com/apache/spark/pull/18317
@jiangxb1987 - Made a change to wrap the read ahead input stream around
the compressed input stream so that we can amortize the cost of decompression
as well
---
If your project is set up for
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/18962#discussion_r134821799
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -330,19 +332,21 @@ object SparkSubmit extends CommandLineUtils {
Github user sitalkedia commented on a diff in the pull request:
https://github.com/apache/spark/pull/18317#discussion_r134821455
--- Diff: core/src/main/java/org/apache/spark/io/ReadAheadInputStream.java
---
@@ -0,0 +1,288 @@
+/*
+ * Licensed under the Apache License,
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18962
also I just realized on our original discussion of "Spark on YARN doesn't
support upload remote resources from http, https or ftp server" I think the
feature to download without this change
Github user tgravescs commented on a diff in the pull request:
https://github.com/apache/spark/pull/18962#discussion_r134820252
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -330,19 +332,21 @@ object SparkSubmit extends CommandLineUtils {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19018
**[Test build #81041 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81041/testReport)**
for PR 19018 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/18581#discussion_r134817030
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/csv/CSVSuite.scala
---
@@ -1195,4 +1196,46 @@ class CSVSuite extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19016
**[Test build #81040 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81040/testReport)**
for PR 19016 at commit
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/19016#discussion_r134816715
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -27,6 +27,17 @@ vignette: >
limitations under the License.
-->
+```{r setup,
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/19018
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 this feature
enabled
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/19029#discussion_r134816423
--- Diff: mllib/src/main/scala/org/apache/spark/ml/stat/Summarizer.scala ---
@@ -438,6 +438,10 @@ private[ml] object SummaryBuilderImpl extends Logging {
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/19016
Sure - change LGTM. Lets see if @HyukjinKwon has any more comments ? If not
we can merge to master, branch-2.2 and then do some more tests.
---
If your project is set up for it, you can
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/19016#discussion_r134815709
--- Diff: R/pkg/vignettes/sparkr-vignettes.Rmd ---
@@ -27,6 +27,17 @@ vignette: >
limitations under the License.
-->
+```{r setup,
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/19016
It likely best to back port this to branch-2.2 so the test can pass with
matching API in a released jar.
Then we can see everything passing (except having to hand edit the version
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/18581#discussion_r134814393
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/HadoopFileLinesReader.scala
---
@@ -32,7 +32,9 @@ import
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/18581#discussion_r134813986
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/source/libsvm/LibSVMOptions.scala ---
@@ -41,11 +41,15 @@ private[libsvm] class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18581
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81036/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18581
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/18581
**[Test build #81036 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81036/testReport)**
for PR 18581 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/18940
---
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 tgravescs commented on the issue:
https://github.com/apache/spark/pull/18940
+1, I'm going to merge as it appears all comments addressed.
---
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 gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/19022#discussion_r134807546
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/expressions/ExpressionSetSuite.scala
---
@@ -210,4 +210,13 @@ class
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/19013#discussion_r134807428
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -202,7 +209,7 @@ object SparkSubmit extends CommandLineUtils {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19022
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81039/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19022
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/19022
**[Test build #81039 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81039/testReport)**
for PR 19022 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19022
**[Test build #81039 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81039/testReport)**
for PR 19022 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/19022
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 feature
enabled and wishes so,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18958
**[Test build #81038 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81038/testReport)**
for PR 18958 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/18266#discussion_r134797984
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JdbcUtils.scala
---
@@ -768,6 +769,25 @@ object JdbcUtils extends
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/18910#discussion_r134795818
--- Diff:
resource-managers/mesos/src/main/scala/org/apache/spark/deploy/mesos/config.scala
---
@@ -70,4 +70,19 @@ package object config {
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/19016
Ah I see. Yeah the failed tests makes sense. We can also try to submit a
custom tar.gz to r-hub to test it with the PDF and a different version number ?
---
If your project is set up for it, you
Github user susanxhuynh commented on the issue:
https://github.com/apache/spark/pull/18910
@srowen Sean, would you like to 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 your project does not
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/19027
Cool looks to me like a very reasonable fix.
Could we perhaps add a test for numpy.bool_ or numpy.float_ (that it should
fail)?
---
If your project is set up for it, you can reply to this
Github user kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/18730#discussion_r134786732
--- Diff:
core/src/main/scala/org/apache/spark/util/io/ChunkedByteBuffer.scala ---
@@ -63,6 +65,19 @@ private[spark] class ChunkedByteBuffer(var chunks:
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/19016
I think that is caused by the way I build the source package - I use the
option --no-build-vignettes so the source package I test with doesn't have the
PDF in it
Similarly for the
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18958
LGTM except some minor comments
---
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 jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/18730
It would be great to benchmark this improvement, otherwise we are not sure
there is no regression.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18958#discussion_r134780644
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/vectorized/ColumnarBatch.java
---
@@ -505,18 +511,12 @@ public void
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18958#discussion_r134780277
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/vectorized/ColumnarBatch.java
---
@@ -95,19 +81,32 @@ public void close() {
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18958#discussion_r134779475
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/vectorized/ColumnarBatch.java
---
@@ -307,64 +306,69 @@ public void update(int ordinal,
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/19016
Thanks @felixcheung ! Are the warnings about the missing PDF unavoidable ?
I see something like
```
checking package vignettes in 'inst/doc' ... WARNING
Package vignette without
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18875
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81033/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18875
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/18875
**[Test build #81033 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81033/testReport)**
for PR 18875 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18645
**[Test build #81037 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81037/testReport)**
for PR 18645 at commit
Github user neoremind commented on the issue:
https://github.com/apache/spark/pull/18964
@cloud-fan would you take a look of the PR, the update is very simple.
Thanks very much!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18581
**[Test build #81036 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81036/testReport)**
for PR 18581 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19022
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/19022
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81035/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19022
**[Test build #81035 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81035/testReport)**
for PR 19022 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19022
**[Test build #81035 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81035/testReport)**
for PR 19022 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18581
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/19022
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18581
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81034/
Test FAILed.
---
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/19022
cc @gatorsmile @HyukjinKwon May you help to trigger Jenkins tests? 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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18581
**[Test build #81034 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81034/testReport)**
for PR 18581 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/19022
We can edit the PR title and description to show the changes clearly.
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/19022#discussion_r134761549
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/ExpressionSet.scala
---
@@ -67,6 +67,12 @@ class ExpressionSet protected(
201 - 300 of 425 matches
Mail list logo
