Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15253
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66917/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15253
**[Test build #66917 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66917/consoleFull)**
for PR 15253 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15468
**[Test build #66920 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66920/consoleFull)**
for PR 15468 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11336
**[Test build #66921 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66921/consoleFull)**
for PR 11336 at commit
Github user jerryshao closed the pull request at:
https://github.com/apache/spark/pull/15253
---
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 jerryshao commented on the issue:
https://github.com/apache/spark/pull/15253
Sure, 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 and wishes so, or
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15471
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66915/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15471
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/15471
**[Test build #66915 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66915/consoleFull)**
for PR 15471 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15190
**[Test build #66919 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66919/consoleFull)**
for PR 15190 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15253
@jerryshao It's merged. Could you close this PR, 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
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/15253
Merging to 1.6. Jenkins didn't use Scala 2.11 to build. I just checked this
PR locally.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/14158
@nblintao I really haven't reviewed these changes closely enough to have a
specific complaint or concern in mind, but I'm more concerned about what
happens when you ask to see "more" when that
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/15284
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 HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/14788#discussion_r83336142
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeExpressions.scala
---
@@ -916,21 +931,26 @@ case class
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/15377#discussion_r83336101
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -2474,25 +2478,42 @@ private[spark] class CallerContext(
val context =
Github user nblintao commented on the issue:
https://github.com/apache/spark/pull/14158
@markhamstra Thanks. Here is my related explanation at the top of this PR.
> If the query text is too long (i.e. longer than 1000 chars), it will be
truncated. This is to avoid downing
Github user jodersky commented on the issue:
https://github.com/apache/spark/pull/15398
The style issues are weird. Running scalastyle in sbt worked fine...
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15472
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/15472
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66916/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15472
**[Test build #66916 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66916/consoleFull)**
for PR 15472 at commit
Github user nblintao commented on the issue:
https://github.com/apache/spark/pull/14158
Thanks, @ajbozarth. Sure, I'd love to rebase it and get it merged. But I am
really busy with my mid-terms and interviews recently. I'll take a look tonight
and fix it if it's easy to do.
Github user jodersky commented on the issue:
https://github.com/apache/spark/pull/15284
cc @marmbrus
---
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 jodersky commented on a diff in the pull request:
https://github.com/apache/spark/pull/15284#discussion_r83334074
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -628,7 +628,7 @@ object ScalaReflection extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14690
**[Test build #3339 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3339/consoleFull)**
for PR 14690 at commit
Github user brkyvz closed the pull request at:
https://github.com/apache/spark/pull/15470
---
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 markhamstra commented on the issue:
https://github.com/apache/spark/pull/14158
It's great if it is already addressed, but I just didn't see anything
explicit in the discussion or examples that showed any query of the magnitude
that I am talking about. Machine-generated
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15469
**[Test build #3338 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3338/consoleFull)**
for PR 15469 at commit
Github user jodersky commented on the issue:
https://github.com/apache/spark/pull/15338
LGTM. Let's see if @nchammas has some feedback. He had some very helpful
comments in #3881
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user jodersky commented on a diff in the pull request:
https://github.com/apache/spark/pull/15398#discussion_r83329826
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/StringUtils.scala
---
@@ -25,26 +25,25 @@ object StringUtils {
//
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15470
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/15470
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66913/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15470
**[Test build #66913 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66913/consoleFull)**
for PR 15470 at commit
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/14158
Thanks @markhamstra that was already addressed earlier in review
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15398
**[Test build #66918 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66918/consoleFull)**
for PR 15398 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15398
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/15398
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66918/
Test FAILed.
---
Github user jodersky commented on the issue:
https://github.com/apache/spark/pull/15398
thanks @yhuai for the feedback! I enumerated some issues in the pull
request description, do you have any input on them? My personal opinion is that
we should change the regex matching to conform
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15398
**[Test build #66918 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66918/consoleFull)**
for PR 15398 at commit
Github user markhamstra commented on the issue:
https://github.com/apache/spark/pull/14158
Please be certain that this works well even for very large queries. They
are not commonplace, but I know that Spark SQL does sometimes get asked to
handle SQL queries that are hundreds of
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/14690
> Oops there is a conflict now.
NP. I'm working on the rebase.
---
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 mallman commented on a diff in the pull request:
https://github.com/apache/spark/pull/14690#discussion_r83325529
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/DataSourceScanExec.scala
---
@@ -225,13 +225,19 @@ case class FileSourceScanExec(
}
Github user mallman commented on a diff in the pull request:
https://github.com/apache/spark/pull/14690#discussion_r83325088
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/PruneFileSourcePartitions.scala
---
@@ -0,0 +1,72 @@
+/*
+ * Licensed
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15148
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66914/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15148
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/15148
**[Test build #66914 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66914/consoleFull)**
for PR 15148 at commit
Github user fidato13 commented on the issue:
https://github.com/apache/spark/pull/15327
cc @srowen @hvanhovell @vanzin @skyluc @kmader @zsxwing @datafarmer
---
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 ajbozarth commented on the issue:
https://github.com/apache/spark/pull/14461
@nblintao I'd like to take another look at this, mind rebasing?
---
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 ajbozarth commented on the issue:
https://github.com/apache/spark/pull/14158
@nblintao Could you rebase? I'd like to try and see if we can get this
reviewed and merged.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15253
**[Test build #66917 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66917/consoleFull)**
for PR 15253 at commit
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/14204
@nblintao Are you willing to rebase this and see if we can try to get it
merged?
---
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/15253
LGTM pending tests
---
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/15253
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 wishes so,
Github user holdenk closed the pull request at:
https://github.com/apache/spark/pull/13571
---
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 holdenk commented on the issue:
https://github.com/apache/spark/pull/13571
So @rxin just commented with an explicit "Won't Fix" on the JIRA.
@zero323 certainly Jython can be slow, but as the benchmark shows it can be
much faster than our current Python UDF
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/15470#discussion_r83319730
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/streaming/DataStreamWriter.scala
---
@@ -222,9 +222,13 @@ final class DataStreamWriter[T]
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/15408#discussion_r83319614
--- Diff:
core/src/main/java/org/apache/spark/io/NioBufferedFileInputStream.java ---
@@ -72,30 +74,35 @@ private boolean refill() throws IOException {
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/12257
Looking through some stale prs to review and try to push through. This
still looks like a good add, @sarutak could you rebase?
---
If your project is set up for it, you can reply to this email
Github user mallman commented on a diff in the pull request:
https://github.com/apache/spark/pull/14690#discussion_r83318096
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -616,6 +617,44 @@ private[spark] class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/11336
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/11336
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66911/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11336
**[Test build #66911 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66911/consoleFull)**
for PR 11336 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15472
**[Test build #66916 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66916/consoleFull)**
for PR 15472 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14690
**[Test build #3339 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3339/consoleFull)**
for PR 14690 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14690
Oops there is a conflict now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14690
The mima failure is just mima flaky.
---
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 tdas opened a pull request:
https://github.com/apache/spark/pull/15472
[SPARK-17731][SQL][STREAMING] Metrics for structured streaming
## What changes were proposed in this pull request?
**This PR adds the same metrics to branch-2.0 that was added to master in
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15235
---
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/15471
**[Test build #66915 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66915/consoleFull)**
for PR 15471 at commit
GitHub user falaki opened a pull request:
https://github.com/apache/spark/pull/15471
[SPARK-17919] Make timeout to RBackend configurable in SparkR
## What changes were proposed in this pull request?
This patch makes RBackend connection timeout configurable by user.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14690
**[Test build #66912 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66912/consoleFull)**
for PR 14690 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15235
Merging in master. 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 and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14690
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/14690
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66912/
Test FAILed.
---
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/15235
@petermaxlee Thanks for making the change. This LGTM now that the fix for
`SPARK-17599` is in the right place. The rest is just moving around,
consolidating old code.
---
If your project is set up
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15148
**[Test build #66914 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66914/consoleFull)**
for PR 15148 at commit
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/15148
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/15470
**[Test build #66913 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66913/consoleFull)**
for PR 15470 at commit
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/15470
cc @zsxwing
---
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
GitHub user brkyvz opened a pull request:
https://github.com/apache/spark/pull/15470
[SPARK-17921] failfast on checkpointLocation specified for memory streams
## What changes were proposed in this pull request?
The checkpointLocation option in memory streams in
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15460
`Caused by: sbt.ForkMain$ForkError:
org.apache.spark.sql.catalyst.analysis.NoSuchTableException: Table or view
'default' not found in database 'srcpart';` Seems we swapped the db and table
name
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15469
**[Test build #3338 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3338/consoleFull)**
for PR 15469 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14690
**[Test build #66912 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66912/consoleFull)**
for PR 14690 at commit
Github user Yunni commented on the issue:
https://github.com/apache/spark/pull/15148
Have no idea to solve this MiMa test. Could anyone give some clue?
```
java.lang.ArrayIndexOutOfBoundsException: 1660
at
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15469
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/15469
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66910/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15469
**[Test build #66910 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66910/consoleFull)**
for PR 15469 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/11336
**[Test build #66911 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66911/consoleFull)**
for PR 11336 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14690
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/14690
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66906/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14690
**[Test build #66906 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66906/consoleFull)**
for PR 14690 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15307
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/15416
@yangw1234 can you fix the scala styles?
---
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 ericl commented on the issue:
https://github.com/apache/spark/pull/15460
LGTM if tests pass :)
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/15397
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/15460
A bunch of mysterious failures ...
---
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/15469
**[Test build #66910 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66910/consoleFull)**
for PR 15469 at commit
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/15460
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 zsxwing commented on the issue:
https://github.com/apache/spark/pull/15397
Thanks! Merging to master and 2.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/15469
Graduate a list of Spark SQL APIs to stable
## What changes were proposed in this pull request?
This patch graduates a list of Spark SQL APIs and mark them stable.
The following are
201 - 300 of 604 matches
Mail list logo
