Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/15257#discussion_r81067756
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/literals.scala
---
@@ -46,12 +57,17 @@ object Literal {
case s:
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15291
Hi, @vanzin , could you review this PR?
The test is written by you here.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14897
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/14897
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66082/
Test PASSed.
---
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/15291#discussion_r81066657
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/FsHistoryProviderSuite.scala
---
@@ -141,7 +141,7 @@ class FsHistoryProviderSuite
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14897
**[Test build #66082 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66082/consoleFull)**
for PR 14897 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15168
Hi, @hvanhovell . I thought it's a regression bug fix.
I'm wondering if you think this is a new feature for Spark 2.1.
---
If your project is set up for it, you can reply to this email
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15257#discussion_r81066475
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/literals.scala
---
@@ -46,12 +57,17 @@ object Literal {
case s:
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/15291#discussion_r81066374
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/FsHistoryProviderSuite.scala
---
@@ -141,7 +141,7 @@ class FsHistoryProviderSuite
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15219
**[Test build #66085 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66085/consoleFull)**
for PR 15219 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14215
**[Test build #66086 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66086/consoleFull)**
for PR 14215 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15292
**[Test build #66084 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66084/consoleFull)**
for PR 15292 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14215
I am reopening this. Please refer the discussion in
https://github.com/apache/spark/pull/15264
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user HyukjinKwon reopened a pull request:
https://github.com/apache/spark/pull/14215
[SPARK-16544][SQL][WIP] Support for conversion from compatible schema for
Parquet data source when data types are not matched
## What changes were proposed in this pull request?
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15291#discussion_r81065527
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/FsHistoryProviderSuite.scala
---
@@ -141,7 +141,7 @@ class FsHistoryProviderSuite extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15292
**[Test build #66083 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66083/consoleFull)**
for PR 15292 at commit
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/15292
[SPARK-17719][SQL] Unify and tie up options in a single place in JDBC
datasource package
## What changes were proposed in this pull request?
This PR proposes to fix arbitrary usages
Github user Myasuka commented on the issue:
https://github.com/apache/spark/pull/15078
@jodersky Actually, BashOnWindows only exists on Windows10 Anniversary
Update. Moreover, this feature needs to be manually enabled to take effects.
And I don't think this bash environment
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15219
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66081/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15219
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/15219
**[Test build #66081 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66081/consoleFull)**
for PR 15219 at commit
Github user wgtmac commented on a diff in the pull request:
https://github.com/apache/spark/pull/15248#discussion_r81062518
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -179,7 +180,11 @@ class HistoryServer(
}
--- End diff --
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15172
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/15172
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66080/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15172
**[Test build #66080 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66080/consoleFull)**
for PR 15172 at commit
Github user ioana-delaney commented on the issue:
https://github.com/apache/spark/pull/15289
@JoshRosen Wouldn't be a better design to push down the predicate but keep
the original predicate as well? If the aggregate is above a complex join, not
pushing down the predicate may have
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15248
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66079/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15248
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/15248
**[Test build #66079 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66079/consoleFull)**
for PR 15248 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15291
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/15291
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66078/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15291
**[Test build #66078 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66078/consoleFull)**
for PR 15291 at commit
Github user cjjnjust commented on a diff in the pull request:
https://github.com/apache/spark/pull/15172#discussion_r81060550
--- Diff:
common/network-common/src/main/java/org/apache/spark/network/sasl/aes/SparkAesCipher.java
---
@@ -0,0 +1,270 @@
+/*
+ * Licensed to the
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14897
@gatorsmile That's a good question, if users are using a SQL shell, there
is no way for them to figure out the global temp database.
But including global temp database in SHOW DATABASES
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14897
**[Test build #66082 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66082/consoleFull)**
for PR 14897 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15047
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/15047
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66069/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15047
**[Test build #66069 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66069/consoleFull)**
for PR 15047 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15263
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/15263
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66077/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15263
**[Test build #66077 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66077/consoleFull)**
for PR 15263 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15263
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66076/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15263
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/15263
**[Test build #66076 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66076/consoleFull)**
for PR 15263 at commit
Github user wgtmac commented on the issue:
https://github.com/apache/spark/pull/15247
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 and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15219
**[Test build #66081 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66081/consoleFull)**
for PR 15219 at commit
Github user wgtmac commented on the issue:
https://github.com/apache/spark/pull/15247
Another test failed in the mllib:
org.apache.spark.mllib.classification.NaiveBayesSuite.Naive Bayes Multinomial
@ajbozarth Have you seen this kind of unrelated failure before? Do I have
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15257
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66075/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15257
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/15257
**[Test build #66075 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66075/consoleFull)**
for PR 15257 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15289
---
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 ericl closed the pull request at:
https://github.com/apache/spark/pull/15282
---
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15289
@JoshRosen I cannot cherry-pick this one into 2.0. Could you open a PR
against 2.0 I feel you that this is required?
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15172
**[Test build #66080 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66080/consoleFull)**
for PR 15172 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15289
Merging to master/2.0. 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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15289
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/15289
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66074/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15289
**[Test build #66074 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66074/consoleFull)**
for PR 15289 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/15178#discussion_r81052440
--- Diff:
core/src/main/scala/org/apache/spark/broadcast/TorrentExecutorBroadcast.scala
---
@@ -0,0 +1,174 @@
+/*
+ * Licensed to the Apache
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15274
@marmbrus I just wonder if adding `to_json` make senses (although maybe it
should be done in another PR). Just curious. I am just imaging the case to
write out dataframes by some data sources
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15248
**[Test build #66079 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66079/consoleFull)**
for PR 15248 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15291
**[Test build #66078 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66078/consoleFull)**
for PR 15291 at commit
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/15291
[SPARK-17412][CORE] FsHistoryProviderSuite fails if `root` user runs it
## What changes were proposed in this pull request?
`FsHistoryProviderSuite` fails if `root` user runs it. The
Github user Sherry302 commented on the issue:
https://github.com/apache/spark/pull/15286
Thank you very much. @tgravescs @JoshRosen
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/15286
---
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/15286
committed this 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/15248
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/15248
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66073/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15248
**[Test build #66073 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66073/consoleFull)**
for PR 15248 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15287
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 sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/15264
^ @davies what do you think? Would `ParquetRowConverter` be a good place to
handle this schema evolution between logical and physical types?
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15287
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66071/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15287
**[Test build #66071 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66071/consoleFull)**
for PR 15287 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/15283#discussion_r81049069
--- Diff: README.md ---
@@ -24,9 +24,9 @@ To build Spark and its example programs, run:
build/mvn -DskipTests clean package
-(You do
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15289
LGTM - pending Jenkins.
---
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 Sherry302 commented on the issue:
https://github.com/apache/spark/pull/15246
Hi, @srowen Yes, you are right. I am searching the code base to see if we
can fix more.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15264
@sameeragarwal Thanks. One thing I'd like to sure is, though, do you think
this is the right place to fix? I just want to be very sure on this before I
reopen my old pr and proceed further.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15286
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66066/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15286
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/15286
**[Test build #66066 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66066/consoleFull)**
for PR 15286 at commit
Github user sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/15264
That's a great explanation. Yes, this patch is really targeted at fixing
the second issue and it does seem like a subset of SPARK-16544. If you have
cycles towards working on a broader fix,
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15078
From the discussion above, I would like to stay against 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
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15078
I'm not sure older Windows versions have powershell installed by default..
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15263
**[Test build #66077 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66077/consoleFull)**
for PR 15263 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15263
**[Test build #66076 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66076/consoleFull)**
for PR 15263 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15290
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 dafrista opened a pull request:
https://github.com/apache/spark/pull/15290
[SPARK-17715] [Scheduler] Make task launch logs DEBUG
## What changes were proposed in this pull request?
Ramp down the task launch logs from INFO to DEBUG. Task launches can happen
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15248
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/15248
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66064/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15248
**[Test build #66064 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66064/consoleFull)**
for PR 15248 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15288
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66072/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15288
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/15288
**[Test build #66072 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66072/consoleFull)**
for PR 15288 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15284
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66060/
Test PASSed.
---
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14897#discussion_r81044097
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -2433,31 +2433,65 @@ class Dataset[T] private[sql](
}
/**
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15284
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/15284
**[Test build #66060 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66060/consoleFull)**
for PR 15284 at commit
Github user tnachen commented on the issue:
https://github.com/apache/spark/pull/14644
@mgummelt @srowen Please review as well
---
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 maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/15257#discussion_r81043337
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/literals.scala
---
@@ -60,6 +70,45 @@ object Literal {
}
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15248
**[Test build #66062 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66062/consoleFull)**
for PR 15248 at commit
1 - 100 of 486 matches
Mail list logo
