Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15375
**[Test build #66750 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66750/consoleFull)**
for PR 15375 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15408
**[Test build #66749 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66749/consoleFull)**
for PR 15408 at commit
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/15422
@zsxwing You are right, NewHadoopRDD is not handling this case.
Probably would be good to add exception handling there when nextKeyValue
throws exception ?
Context is, for large
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14847
@viirya This is a pretty interesting. Based on the suggestion from @rxin
let us discuss it? Also cc @ioana-delaney @nsyca
---
If your project is set up for it, you can reply to this email and
Github user mgummelt commented on a diff in the pull request:
https://github.com/apache/spark/pull/13713#discussion_r82846312
--- Diff: docs/running-on-mesos.md ---
@@ -506,8 +506,13 @@ See the [configuration page](configuration.html) for
information on Spark config
since
Github user mgummelt commented on a diff in the pull request:
https://github.com/apache/spark/pull/13713#discussion_r82846146
--- Diff: docs/running-on-mesos.md ---
@@ -506,8 +506,13 @@ See the [configuration page](configuration.html) for
information on Spark config
since
Github user mgummelt commented on a diff in the pull request:
https://github.com/apache/spark/pull/13713#discussion_r82846761
--- Diff:
mesos/src/test/scala/org/apache/spark/scheduler/cluster/mesos/MesosCoarseGrainedSchedulerBackendSuite.scala
---
@@ -463,6 +463,21 @@ class
Github user mgummelt commented on a diff in the pull request:
https://github.com/apache/spark/pull/13713#discussion_r82846430
--- Diff:
mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -129,6 +129,7 @@ private[spark] class
Github user mgummelt commented on a diff in the pull request:
https://github.com/apache/spark/pull/13713#discussion_r82846894
--- Diff:
mesos/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosFineGrainedSchedulerBackend.scala
---
@@ -59,6 +59,8 @@ private[spark] class
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15422
@mridulm This fix just makes HadoopRDD consistent with NewHadoopRDD and the
current behavior of Spark SQL in 2.0.
For 1.6, that's another story since Spark SQL uses HadoopRDD directly.
Github user sitalkedia commented on the issue:
https://github.com/apache/spark/pull/15408
@rxin, @srowen, @mridulm - The consensus seems to be to treat -1 (or less
than 0) as end of file and return value of 0 to continue reading the file
further, I will make the necessary changes.
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/15422
I agree that the data that was already read is probably good. I also think
that this is a pretty big behavior change where there are legitimate cases
(i.e. tons of data and it is fine to miss
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15421
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/15421
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66745/
Test PASSed.
---
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14847
So I'd recommend closing this for now. @viirya you are welcome to work on
it still, but it should:
1. Be obvious in explain (e.g. through an operator) that this behavior
exists.
2. Works
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/15422
@srowen The tuples already returned would have been valid, it is the
subsequent block decompression which has failed. For example, in a 1gb file,
the last few bytes missing (or corrupt) will cause
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15421
**[Test build #66745 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66745/consoleFull)**
for PR 15421 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14847
FYI this is a relevant paper
http://www.comp.nus.edu.sg/~tankl/cs5208/readings/enough.pdf
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/14690
BTW, I'm working on a rebase to fix merge conflicts and address reviewers'
feedback.
---
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 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 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/66748/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15435
**[Test build #66748 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66748/consoleFull)**
for PR 15435 at commit
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/14690
I would be wary of amending our data sources to support case-insensitive
field resolution. For one thing, strictly speaking it can lead to ambiguity in
schema resolution. In theâpotential but
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15398
I see. Agree. Will do an investigation with @jodersky 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 olarayej commented on the issue:
https://github.com/apache/spark/pull/11336
@falaki Sorry, I was out of town. Let me get back to this today. Thank you!
---
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/15435
**[Test build #66748 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66748/consoleFull)**
for PR 15435 at commit
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/15435
@sethah This pr seems to be discussed about several details, I am pleasure
to hear your opinion, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15422
If this happens it isn't clear that anything that was read is valid. It
doesn't seem like something to ignore. Log, at least. I know people differ on
this but I think continuing with partial and
GitHub user WeichenXu123 opened a pull request:
https://github.com/apache/spark/pull/15435
[SPARK-17139][ML] Add model summary for MultinomialLogisticRegression
## What changes were proposed in this pull request?
Add model summary for MultinomialLogisticRegression.
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15190
If we have `spark.sql.hive.convertCTAS=true` and
`hive.default.fileformat=orc`, what format will we use when we create a table
through a CTAS statement?
---
If your project is set up for it, you
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15417
You can make a try.
---
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 yhuai commented on the issue:
https://github.com/apache/spark/pull/15398
I think we should consider other databases behavior and see if our behavior
makes sense.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15398
@jodersky Thank you for the patch! How about we add a summary related to
the behavior of escape in pr description and jira?
---
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/15375
**[Test build #3324 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3324/consoleFull)**
for PR 15375 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15434
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/15434
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66744/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15434
**[Test build #66744 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66744/consoleFull)**
for PR 15434 at commit
Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/15422
Why would corrupt record cause EOFException to be thrown ?
---
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 shivaram commented on the issue:
https://github.com/apache/spark/pull/15421
Yeah it should be fine to merge this into branch-2.0 when it is ready
---
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/14719
**[Test build #66747 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66747/consoleFull)**
for PR 14719 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15421
**[Test build #66746 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66746/consoleFull)**
for PR 15421 at commit
Github user falaki commented on a diff in the pull request:
https://github.com/apache/spark/pull/15421#discussion_r82814431
--- Diff: R/pkg/DESCRIPTION ---
@@ -11,7 +11,8 @@ Authors@R: c(person("Shivaram", "Venkataraman", role =
c("aut", "cre"),
email =
Github user MechCoder commented on the issue:
https://github.com/apache/spark/pull/7963
Thanks for the reviews @holdenk . Unfortunately I will not be able to work
on this anytime soon. Feel free to cherry-pick the commits, (if you wish)
---
If your project is set up for it, you can
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/15433
@techaddict Thanks for the PR. The test failures seem related to this patch
-- Could you check why they are failing ?
---
If your project is set up for it, you can reply to this email and have
Github user squito commented on the issue:
https://github.com/apache/spark/pull/15249
@kayousterhout good idea about running performance tests, I hadn't run them
on a recent rev. I confirmed that the issue in
https://github.com/apache/spark/pull/14871 was no longer present (just to
Github user dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/15423#discussion_r82818691
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkSqlParser.scala ---
@@ -168,17 +168,7 @@ class SparkSqlAstBuilder(conf: SQLConf)
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15433
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66742/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15433
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 dilipbiswal commented on a diff in the pull request:
https://github.com/apache/spark/pull/15423#discussion_r82817760
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/SQLQueryTestSuite.scala ---
@@ -207,6 +208,7 @@ class SQLQueryTestSuite extends QueryTest with
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15433
**[Test build #66742 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66742/consoleFull)**
for PR 15433 at commit
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15434
Can you update the description to explain if `ALTER TABLE db1.tbl RENAME TO
db2.tbl2` is allowed (I guess it is not allowed)?
---
If your project is set up for it, you can reply to this email and
Github user k-yokoshi commented on a diff in the pull request:
https://github.com/apache/spark/pull/13036#discussion_r82816487
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -470,7 +470,7 @@ def sampleBy(self, col, fractions, seed=None):
+---+-+
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/15408#discussion_r82816160
--- Diff:
core/src/main/java/org/apache/spark/io/NioBufferedFileInputStream.java ---
@@ -0,0 +1,129 @@
+/*
+ * Licensed under the Apache License,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15421
**[Test build #66745 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66745/consoleFull)**
for PR 15421 at commit
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/15342
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 sethah commented on the issue:
https://github.com/apache/spark/pull/9
@MLnick Good questions. For the setting of params - I'm sure it varies in
some cases, but for example, why would you want to use the same `maxIter` when
training with an initial model vs without? I
Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/15410
while I understand the problem, the issue here is that what you are
printing might not be accurate either. We only pull for new logs every X
number of seconds (default is 10s, user could change
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15434
**[Test build #66744 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66744/consoleFull)**
for PR 15434 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15434
cc @yhuai @gatorsmile
---
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 cloud-fan opened a pull request:
https://github.com/apache/spark/pull/15434
[SPARK-17873][SQL] ALTER TABLE RENAME TO should allow users to specify
database in destination table name
## What changes were proposed in this pull request?
In #14955 , we forbid users
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12064
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66743/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12064
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/12064
**[Test build #66743 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66743/consoleFull)**
for PR 12064 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15423#discussion_r82797867
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/SQLQueryTestSuite.scala ---
@@ -207,6 +208,7 @@ class SQLQueryTestSuite extends QueryTest with
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12064
**[Test build #66743 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66743/consoleFull)**
for PR 12064 at commit
Github user vijoshi commented on a diff in the pull request:
https://github.com/apache/spark/pull/15410#discussion_r82789161
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala ---
@@ -316,24 +320,41 @@ private[history] class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15433
**[Test build #66742 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66742/consoleFull)**
for PR 15433 at commit
GitHub user techaddict opened a pull request:
https://github.com/apache/spark/pull/15433
[SPARK-17822] Use weak reference in JVMObjectTracker.objMap because it may
leak JVM objects
## What changes were proposed in this pull request?
Use weak reference in JVMObjectTracker.objMap
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12933
**[Test build #66741 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66741/consoleFull)**
for PR 12933 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12933
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66741/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12933
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/12933
**[Test build #66741 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66741/consoleFull)**
for PR 12933 at commit
Github user hellertime commented on the issue:
https://github.com/apache/spark/pull/12933
Fixed scala style error
---
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 YuhuWang2002 commented on a diff in the pull request:
https://github.com/apache/spark/pull/15297#discussion_r82779299
--- Diff: core/src/main/scala/org/apache/spark/MapOutputTracker.scala ---
@@ -138,13 +138,16 @@ private[spark] abstract class MapOutputTracker(conf:
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12933
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 YuhuWang2002 commented on a diff in the pull request:
https://github.com/apache/spark/pull/15297#discussion_r82779060
--- Diff: core/src/main/scala/org/apache/spark/MapOutputTracker.scala ---
@@ -687,18 +691,21 @@ private[spark] object MapOutputTracker extends
Logging
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12933
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66740/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12933
**[Test build #66740 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66740/consoleFull)**
for PR 12933 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12933
**[Test build #66740 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66740/consoleFull)**
for PR 12933 at commit
Github user hellertime commented on the issue:
https://github.com/apache/spark/pull/12933
@tnachen rebased with 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15432
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66738/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15432
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/15432
**[Test build #66738 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66738/consoleFull)**
for PR 15432 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15432
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/15432
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66737/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15432
**[Test build #66737 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66737/consoleFull)**
for PR 15432 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15405
**[Test build #3323 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3323/consoleFull)**
for PR 15405 at commit
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/15430
cc @jkbradley
---
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 yanboliang commented on the issue:
https://github.com/apache/spark/pull/15431
cc @felixcheung @jkbradley
---
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/15431
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/15431
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66736/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15431
**[Test build #66736 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66736/consoleFull)**
for PR 15431 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12064
**[Test build #66739 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66739/consoleFull)**
for PR 12064 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12064
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 zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/15402
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/12064
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66739/
Test FAILed.
---
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15417
Yes - there are several tens of test sql that fails checkAnalysis, should
we update them all?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12064
**[Test build #66739 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66739/consoleFull)**
for PR 12064 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15429
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66732/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15429
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
401 - 500 of 661 matches
Mail list logo
