Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11919#issuecomment-214523146
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12573
---
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 pull request:
https://github.com/apache/spark/pull/11919#issuecomment-214522903
**[Test build #56915 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56915/consoleFull)**
for PR 11919 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/12573#issuecomment-214522478
Merged into 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
Github user kevinyu98 commented on the pull request:
https://github.com/apache/spark/pull/12646#issuecomment-214521095
@dongjoon-hyun Hello Dongjoon: I have fix the comments, let me know if you
see anything else I need to change. Also I did git fetch upstream, git merge
Github user bomeng closed the pull request at:
https://github.com/apache/spark/pull/12347
---
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 bomeng commented on the pull request:
https://github.com/apache/spark/pull/12347#issuecomment-214518666
closing 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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12668#issuecomment-214518004
**[Test build #56923 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56923/consoleFull)**
for PR 12668 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12668#issuecomment-214515327
**[Test build #56921 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56921/consoleFull)**
for PR 12668 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12668#issuecomment-214515338
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12614#issuecomment-214515386
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user wangmiao1981 commented on the pull request:
https://github.com/apache/spark/pull/12560#issuecomment-214515243
@MLnick I agree. I will remove the feature log now and only log parameters.
I will keep the named feature method.
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12614#issuecomment-214515383
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12668#issuecomment-214515335
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12614#issuecomment-214515143
**[Test build #56917 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56917/consoleFull)**
for PR 12614 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12667#issuecomment-214514867
**[Test build #56922 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56922/consoleFull)**
for PR 12667 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12668#issuecomment-214514873
**[Test build #56921 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56921/consoleFull)**
for PR 12668 at commit
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/12668
[SPARK-14853] [SQL] Support LeftSemi/LeftAnti in SortMergeJoinExec
## What changes were proposed in this pull request?
This PR update SortMergeJoinExec to support LeftSemi/LeftAnti, so it
GitHub user sameeragarwal opened a pull request:
https://github.com/apache/spark/pull/12667
[SPARK-14467][SQL] Experiments: Async I/O in FileScanRDD
## What changes were proposed in this pull request?
Builds on https://github.com/apache/spark/pull/12243 to help benchmark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12665#issuecomment-214513400
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12665#issuecomment-214513406
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12665#issuecomment-214513124
**[Test build #56913 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56913/consoleFull)**
for PR 12665 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12589#issuecomment-214510368
**[Test build #56919 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56919/consoleFull)**
for PR 12589 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12625#issuecomment-214512829
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12625#issuecomment-214512825
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12625#issuecomment-214512583
**[Test build #56911 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56911/consoleFull)**
for PR 12625 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11635
---
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 pull request:
https://github.com/apache/spark/pull/12625#issuecomment-214511787
**[Test build #56920 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56920/consoleFull)**
for PR 12625 at commit
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/11635#issuecomment-214511495
Merging to 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12500#issuecomment-214510751
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12500#issuecomment-214510753
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12500#issuecomment-214510609
**[Test build #56916 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56916/consoleFull)**
for PR 12500 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12589#issuecomment-214510031
**[Test build #2872 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2872/consoleFull)**
for PR 12589 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12589#issuecomment-214510079
**[Test build #2873 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2873/consoleFull)**
for PR 12589 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12589#issuecomment-214510146
**[Test build #2874 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2874/consoleFull)**
for PR 12589 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12585
---
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 pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214508934
**[Test build #56918 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56918/consoleFull)**
for PR 12493 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/12585#issuecomment-214508566
Thanks merging into 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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12585#issuecomment-214508281
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user sethah commented on the pull request:
https://github.com/apache/spark/pull/12663#issuecomment-214508180
These changes look good. I left a couple small comments.
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214507799
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214507057
**[Test build #56909 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56909/consoleFull)**
for PR 12493 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214507478
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214507476
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
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12608#issuecomment-214504735
That's all. Thanks for separating this out.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12625#issuecomment-214504622
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12608#issuecomment-214504699
* pyspark.ml.clustering.KMeans needs to be updated too (in the docstrings)
* pyspark.mllib.clustering.KMeansModel has a doc test example which needs
to be updated
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12585#issuecomment-214504703
**[Test build #2870 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2870/consoleFull)**
for PR 12585 at commit
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/12608#discussion_r60979730
--- Diff: python/pyspark/mllib/clustering.py ---
@@ -349,9 +347,6 @@ def train(cls, rdd, k, maxIterations=100, runs=1,
initializationMode="k-means||"
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12625#issuecomment-214504621
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12625#issuecomment-214504531
**[Test build #56910 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56910/consoleFull)**
for PR 12625 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12585#issuecomment-214504366
**[Test build #2869 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2869/consoleFull)**
for PR 12585 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12614#issuecomment-214503773
**[Test build #56917 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56917/consoleFull)**
for PR 12614 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12665#issuecomment-214503106
Oh, I see. I overlooked that.
Thank you, @davies !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user dongjoon-hyun closed the pull request at:
https://github.com/apache/spark/pull/12665
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12608#issuecomment-214502804
I'll take a look
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/12665#issuecomment-214502099
LZ4BlockInputStream.java is NOT licensed to Apache Software Foundation
(ASF), even it's licensed under Apache License.
---
If your project is set up for it, you can
Github user Mpn177 commented on the pull request:
https://github.com/apache/spark/pull/12664#issuecomment-214501325
Don't see any problems with this.
---
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 dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12426#discussion_r60977845
--- Diff: R/pkg/inst/tests/testthat/test_context.R ---
@@ -141,3 +141,8 @@ test_that("sparkJars sparkPackages as comma-separated
strings", {
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12426#discussion_r60977738
--- Diff: R/pkg/R/context.R ---
@@ -226,6 +226,47 @@ setCheckpointDir <- function(sc, dirName) {
invisible(callJMethod(sc, "setCheckpointDir",
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12426#discussion_r60977638
--- Diff: R/pkg/NAMESPACE ---
@@ -287,6 +287,7 @@ export("as.DataFrame",
"read.json",
"read.parquet",
"read.text",
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12585#issuecomment-214499333
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12585#issuecomment-214499329
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12585#issuecomment-214498735
**[Test build #56907 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56907/consoleFull)**
for PR 12585 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12500#issuecomment-214498270
**[Test build #56916 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56916/consoleFull)**
for PR 12500 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12585#issuecomment-214497498
**[Test build #2868 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2868/consoleFull)**
for PR 12585 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12663#issuecomment-214496921
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12663#issuecomment-214496922
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12663#issuecomment-214496772
**[Test build #56914 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56914/consoleFull)**
for PR 12663 at commit
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/12402#discussion_r60975535
--- Diff: python/pyspark/ml/clustering.py ---
@@ -22,7 +22,151 @@
from pyspark.mllib.common import inherit_doc
__all__ =
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12596#issuecomment-214495321
Thanks for the PR. This should also include:
* LassoWithSGD (recommend using LinearRegression with elasticNetParam = 1.0)
* RidgeRegressionWithSGD (recommend
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/12596#discussion_r60974980
--- Diff: python/pyspark/mllib/classification.py ---
@@ -312,6 +313,10 @@ def train(cls, data, iterations=100, step=1.0,
miniBatchFraction=1.0,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12593#issuecomment-214494498
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12593#issuecomment-214494500
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12593#issuecomment-214494351
**[Test build #56912 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56912/consoleFull)**
for PR 12593 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12663#issuecomment-214493865
I'll wait to update this until your reviews are done. Thanks for taking a
look!
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12589#issuecomment-214493617
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12568
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12589#issuecomment-214493611
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12589#issuecomment-214493425
**[Test build #56905 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56905/consoleFull)**
for PR 12589 at commit
Github user BenFradet commented on the pull request:
https://github.com/apache/spark/pull/12500#issuecomment-214493135
@MLnick will do
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/12568#issuecomment-214492945
LGTM. 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
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/12560#issuecomment-214490075
@wangmiao1981 I tend to agree with @yanboliang. I don't think adding
instrumentation is critical enough to break the `train` method signature, even
if it is
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12659#issuecomment-214488360
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/12663#discussion_r60971502
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/Classifier.scala ---
@@ -62,6 +65,76 @@ abstract class Classifier[
def
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/12659#discussion_r60971154
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala
---
@@ -622,40 +620,44 @@ class SessionCatalog(
*
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12498#issuecomment-214486402
Here it is: https://issues.apache.org/jira/browse/SPARK-14899
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12498#issuecomment-214485807
Update after speaking with @mengxr
Since we're breaking behavior anyways with with PR, perhaps we should try
to enforce good practice by:
* Removing "native"
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12666#issuecomment-214484848
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12498
---
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 dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12665#issuecomment-214483662
This PR contains only comment updates and moves, and RAT check is passed.
```
GitHub user sbcd90 opened a pull request:
https://github.com/apache/spark/pull/12666
[SPARK-14889][Spark Core] scala.MatchError: NONE (of class
scala.Enumeration) when spark.scheduler.mode=NONE
## What changes were proposed in this pull request?
Handling exception for the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12663#issuecomment-214482287
**[Test build #56914 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56914/consoleFull)**
for PR 12663 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11919#issuecomment-214482289
**[Test build #56915 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56915/consoleFull)**
for PR 11919 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12498#issuecomment-214482165
This LGTM.
We'll still need to update the pyspark.mllib implementation. @yanboliang
I'll merge this with master, but could you please do that in a follow-up PR?
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/12521#issuecomment-214482001
/cc @tdas
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12662
---
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 MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/11919#discussion_r60969566
--- Diff: mllib/src/main/scala/org/apache/spark/ml/recommendation/ALS.scala
---
@@ -656,13 +656,15 @@ object ALS extends DefaultParamsReadable[ALS] with
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/12521#discussion_r60969585
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/DataFrameReaderWriterSuite.scala
---
@@ -368,4 +368,79 @@ class
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12662#issuecomment-214481742
Just a note. The test in that file is
```
create table test (a int) stored as inputformat
'org.apache.hadoop.hive.ql.io.RCFileInputFormat' outputformat
401 - 500 of 786 matches
Mail list logo
