Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15168
Thank you for your investigation! How about generating a user-friendly
error message in these unsupported cases? The error messages from Hive is very
confusing to the external users.
---
If
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15168
Hi, @gatorsmile . I investigated the related PRs.
* #12934 `[SPARK-14127][SQL] Makes 'DESC [EXTENDED|FORMATTED] '
support data source tables`
* #12844 `[SPARK-14127][SQL] Native
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15233
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65874/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15233
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/15233
**[Test build #65874 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65874/consoleFull)**
for PR 15233 at commit
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/15234#discussion_r80374185
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveDDLSuite.scala
---
@@ -506,6 +506,25 @@ class HiveDDLSuite
}
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15234
**[Test build #65875 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65875/consoleFull)**
for PR 15234 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/15234
[SPARK-17660] [SQL] DESC FORMATTED for VIEW Lacks View Definition
### What changes were proposed in this pull request?
Before this PR, DESC FORMATTED does not have a section for the view
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15232
Hmm, thanks.
I thought we had "turn warning to error" in test - any idea why these
didn't error out in the PR before it was merged?
---
If your project is set up for it, you can
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15231
Let's add some tests for 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 not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15233
**[Test build #65874 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65874/consoleFull)**
for PR 15233 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15168
Partitioned View is another potential issue for this PR.
FYI, just submitted a related PR https://github.com/apache/spark/pull/15168
---
If your project is set up for it, you can
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15232
Sorry, I left and removed a wring comment. Please ignore that. Sure, I will
rather try to add an explicit check before that.
---
If your project is set up for it, you can reply to this email
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/15233
[SPARK-17659] [SQL] Partitioned View is Not Supported In SHOW CREATE TABLE
### What changes were proposed in this pull request?
`Partitioned View` is not supported by SPARK SQL. For Hive
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14897
For `CREATE SHOW TABLE` on global temporary views, we need to always
qualify the database name `global_temp` in the table name, no matter whether
users add it or not.
---
If your project is
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15168
Sure. I'll investigate from that. Thank you for the pointer, @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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15168
Yeah, please change the JIRA to improvement.
I did not check the code of Spark 1.6.2, but, since Spark 2.0, we provide a
native support for `DESC TABLE`. See the PR:
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/65872/
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 #65872 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65872/consoleFull)**
for PR 15219 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14936
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/14936
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65873/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14936
**[Test build #65873 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65873/consoleFull)**
for PR 14936 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14936
**[Test build #65873 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65873/consoleFull)**
for PR 14936 at commit
Github user philipphoffmann commented on the issue:
https://github.com/apache/spark/pull/14936
rebase 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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15232
Sure, I trust your judgement. Coould you please guide me please? (Is there
a common logic to check this?)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15219
**[Test build #65872 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65872/consoleFull)**
for PR 15219 at commit
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/15232
Thanks @HyukjinKwon - Fix looks good. But isn't it better to do the check
before we do the na.omit / as.integer ? Or will that miss some cases ?
---
If your project is set up for it, you can
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 #65871 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65871/consoleFull)**
for PR 15219 at commit
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/65871/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15225
**[Test build #3289 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3289/consoleFull)**
for PR 15225 at commit
Github user mpjlu commented on the issue:
https://github.com/apache/spark/pull/15214
Hi @yanboliang , got it. 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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15168
Actually, I think there was a reason not to do that in Spark 1.6.2. In
Spark 2.0, is there any new way to lookup the partition info from Parquet
Datasource through `SessionCatalog`?
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15230
cc @cloud-fan @yhuai
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15168
Yeah, I knew. : ) This PR is to support `DESCRIBE PARTITION`, right? The
other `DESCRIBE` commands can support all the table types. Thus, I believe we
need to support all the cases for `DESCRIBE
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15219
**[Test build #65871 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65871/consoleFull)**
for PR 15219 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15219
**[Test build #65870 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65870/consoleFull)**
for PR 15219 at commit
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 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/65870/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15219
**[Test build #65870 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65870/consoleFull)**
for PR 15219 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15168
Hi, @gatorsmile .
It's the same behavior with Apache Spark 1.6.2. This PR doesn't make any
regression for Datasource tables. Actually, the error you mentioned is raised
by
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15090
has an offline discussion with @wzhfy , here is the result:
1. The current `ColumnStats` is hard to use because most of its fields are
`Option`, some are `Option[Any]`, and we may need a
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15225
**[Test build #3289 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3289/consoleFull)**
for PR 15225 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15168
Thank you, @gatorsmile . I'll fix that soon.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12819
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65869/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12819
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/12819
**[Test build #65869 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65869/consoleFull)**
for PR 12819 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12819
**[Test build #65869 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65869/consoleFull)**
for PR 12819 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15231
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65868/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15231
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/15231
**[Test build #65868 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65868/consoleFull)**
for PR 15231 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15232
**[Test build #65867 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65867/consoleFull)**
for PR 15232 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15232
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65867/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15232
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/15231
**[Test build #65868 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65868/consoleFull)**
for PR 15231 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15231
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/15231
**[Test build #65866 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65866/consoleFull)**
for PR 15231 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15231
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65866/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15232
**[Test build #65867 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65867/consoleFull)**
for PR 15232 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15232
cc @felixcheung and @shivaram
---
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 HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/15232
[SPARK-17499][SPARKR][FOLLOWUP] Suppress warnings from is.na in spark.mlp
causing warnings in test results
## What changes were proposed in this pull request?
Some tests in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15231
**[Test build #65866 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65866/consoleFull)**
for PR 15231 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15231
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15231
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/15231
**[Test build #65865 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65865/consoleFull)**
for PR 15231 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15231
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65865/
Test FAILed.
---
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15231
FWIW - Python API seems having `path` as optional[1] and Scala API seems
doing this so as well[2].
[1]https://github.com/apache/spark/blob/master/python/pyspark/sql/readwriter.py#L521
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15231
**[Test build #65865 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65865/consoleFull)**
for PR 15231 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15231
cc @felixcheung and @shivaram
---
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 HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/15231
[SPARK-17658][SPARKR] write.df API taking path optionally in SparkR
## What changes were proposed in this pull request?
`write.df` API requires path which is not actually always
Github user chuanlei commented on a diff in the pull request:
https://github.com/apache/spark/pull/15195#discussion_r80357457
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/streaming/DataStreamWriter.scala
---
@@ -290,8 +284,8 @@ final class DataStreamWriter[T]
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15214
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/15214
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65864/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15214
**[Test build #65864 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65864/consoleFull)**
for PR 15214 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15230
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/15230
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65863/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15230
**[Test build #65863 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65863/consoleFull)**
for PR 15230 at commit
Github user gglanzani commented on the issue:
https://github.com/apache/spark/pull/15074
@thunterdb any updates here? Can this be merged?
---
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/15215
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15168
It sounds like the implementation of this PR does not support data source
tables. Please try the following example.
```Scala
spark
.range(1).select('id as 'a, 'id
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/15215
Merged into master. Thanks for 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 does not have this feature
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/15214
@mpjlu The most important cause of this change is that the fit/train model
should not dependent on the order of users setting params. In other words,
users should get the same model whether set
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15214#discussion_r80355108
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/feature/ChiSqSelectorSuite.scala ---
@@ -76,7 +76,7 @@ class ChiSqSelectorSuite extends
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15214#discussion_r80355103
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/ChiSqSelector.scala ---
@@ -160,6 +166,12 @@ final class ChiSqSelector @Since("1.6.0")
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15214
**[Test build #65864 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65864/consoleFull)**
for PR 15214 at commit
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15214#discussion_r80355100
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/ChiSqSelector.scala ---
@@ -143,13 +149,13 @@ final class ChiSqSelector @Since("1.6.0")
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15168
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/15168
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65861/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15168
**[Test build #65861 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65861/consoleFull)**
for PR 15168 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15149
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/15149
Merged 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 wishes so, or
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15179
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/15179
Merged to master/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
enabled and wishes so,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15230
**[Test build #65863 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65863/consoleFull)**
for PR 15230 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/15230
[SPARK-17657] [SQL] Disallow Users to Change Table Type
### What changes were proposed in this pull request?
Hive allows users to change the table type from `Managed` to `External` or
from
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15229
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/15229
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65862/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15229
**[Test build #65862 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65862/consoleFull)**
for PR 15229 at commit
Github user jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/14808
@sethah I seem to have missed the other comment with the notes what has to
be done to make the PR an example for the change. Sorry.
Since I'm very new to it and the only way to learn
1 - 100 of 104 matches
Mail list logo
