Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15861
cc @mridulm can you 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 feature
enabled and
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15959#discussion_r88843463
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -627,26 +629,43 @@ private[spark] class HiveExternalCatalog(conf:
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15959#discussion_r88843445
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/AnalyzeColumnCommand.scala
---
@@ -100,99 +100,30 @@ object AnalyzeColumnCommand
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15959
cc @srinathshankar @cloud-fan @wzhfy
---
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/15959
**[Test build #68927 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68927/consoleFull)**
for PR 15959 at commit
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/15959
[SPARK-18522][SQL] Explicit contract for column stats serialization
## What changes were proposed in this pull request?
The current implementation of column stats uses the base64 encoding of the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15958
**[Test build #68926 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68926/consoleFull)**
for PR 15958 at commit
GitHub user jiangxb1987 opened a pull request:
https://github.com/apache/spark/pull/15958
[SPARK-17932][SQL] Failed to run SQL "show table extended like table_name"
in Spark2.0.0
## What changes were proposed in this pull request?
Currently we haven't implemented `SHOW
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15957
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68921/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15957
**[Test build #68921 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68921/consoleFull)**
for PR 15957 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15957
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/15868
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/15868
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68917/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15868
**[Test build #68917 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68917/consoleFull)**
for PR 15868 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15929
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/15929
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68915/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15929
**[Test build #68915 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68915/consoleFull)**
for PR 15929 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12896
**[Test build #68925 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68925/consoleFull)**
for PR 12896 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15954
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68923/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15954
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/15954
**[Test build #68923 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68923/consoleFull)**
for PR 15954 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/14038
yea, as for data files, it's okay to filter out '_' and '.'. But, the file
pattens of metadata depend on file formats as suggested in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15954
**[Test build #68923 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68923/consoleFull)**
for PR 15954 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15888
**[Test build #68924 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68924/consoleFull)**
for PR 15888 at commit
Github user dasbipulkumar commented on the issue:
https://github.com/apache/spark/pull/15880
@gatorsmile
configuration flag would be good approach.
---
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/15777
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15956#discussion_r88839350
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -388,6 +388,21 @@ abstract class BinaryComparison
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15777
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68919/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15777
**[Test build #68919 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68919/consoleFull)**
for PR 15777 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15956
So technically I think map type should be able to be used in equality
comparison, but not orderable, so I'm not sure if this is correct.
Spark SQL currently has a restriction that we just
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15953
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68914/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15953
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/15953
**[Test build #68914 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68914/consoleFull)**
for PR 15953 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14038
Do we have a strong need for this? Anything wrong with just filtering out
all file names that start with _ and .?
---
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/15868
**[Test build #68922 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68922/consoleFull)**
for PR 15868 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15955
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/15955
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68918/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15955
**[Test build #68918 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68918/consoleFull)**
for PR 15955 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15957
**[Test build #68921 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68921/consoleFull)**
for PR 15957 at commit
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/15957
[SPARK-18520][ML] Add missing setXXXCol methods for BisectingKMeansModel
and GaussianMixtureModel
## What changes were proposed in this pull request?
add `setFeaturesCol` and
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15951
When users specify schemas, we do not want to infer the schemas due to its
potentially expensive cost. Based on my understanding, data corruption issues
are common when user-specified schemas do
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15868#discussion_r88836683
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JDBCOptions.scala
---
@@ -122,6 +122,11 @@ class JDBCOptions(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15956
**[Test build #68920 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68920/consoleFull)**
for PR 15956 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15956
cc @yhuai @hvanhovell @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
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15951#discussion_r88835591
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -272,14 +309,20 @@ case class DataSource(
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15956#discussion_r88835551
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/CheckAnalysis.scala
---
@@ -183,21 +183,6 @@ trait CheckAnalysis extends
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/15913
cc @jkbradley @sethah
---
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 cloud-fan opened a pull request:
https://github.com/apache/spark/pull/15956
[SPARK-18519][SQL] map type can not be used in binary comparison
## What changes were proposed in this pull request?
MapType is not orderable, we forbid users to use map type in join key
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15777
**[Test build #68919 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68919/consoleFull)**
for PR 15777 at commit
Github user sethah commented on a diff in the pull request:
https://github.com/apache/spark/pull/15777#discussion_r88833295
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/clustering/BisectingKMeans.scala ---
@@ -95,8 +95,7 @@ class BisectingKMeansModel private[ml] (
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/15955
`HasSolver` now don't support value validation, so it's not easy to use:
GLR and LiR inherit `HasSolver`, but need to do param validation explicitly
like this PR
MLP dont inherit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15955
**[Test build #68918 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68918/consoleFull)**
for PR 15955 at commit
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/15955
[SPARK-18434][ML][FOLLOWUP] Add checking for setSolver in GLM
## What changes were proposed in this pull request?
add checking in GLM.setSolver to forbidden unsupported solvers:
`val
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15868
**[Test build #68917 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68917/consoleFull)**
for PR 15868 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15954
**[Test build #68916 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68916/consoleFull)**
for PR 15954 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15954
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68916/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15954
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/15954
**[Test build #68916 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68916/consoleFull)**
for PR 15954 at commit
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/15954
/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
enabled and wishes so, or if
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/15954
[WIP][SPARK-18516][SQL] Split state and progress in streaming
This PR separates the status of a `StreamingQuery` into two separate APIs:
- `status` - describes the status of a
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15951
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/15951
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68913/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15951
**[Test build #68913 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68913/consoleFull)**
for PR 15951 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15929
**[Test build #68915 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68915/consoleFull)**
for PR 15929 at commit
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/15868#discussion_r88829741
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JDBCOptions.scala
---
@@ -122,6 +122,11 @@ class JDBCOptions(
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15953
Hi, @gatorsmile .
This is a related case with #15682 (Dropping View) and the `uncache` issue.
But, this case is different from the above case because this PR has the
obvious solution.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15953
**[Test build #68914 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68914/consoleFull)**
for PR 15953 at commit
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/15953
[SPARK-18517][SQL] DROP TABLE IF EXISTS should not warn for non-existing
tables
## What changes were proposed in this pull request?
Currently, `DROP TABLE IF EXISTS` shows warning
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15929#discussion_r88827491
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -452,15 +444,7 @@ case class EqualNullSafe(left:
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15901
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15901
thanks, merging to master/2.1!
---
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 jagadeesanas2 commented on the issue:
https://github.com/apache/spark/pull/15947
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15952
**[Test build #68912 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68912/consoleFull)**
for PR 15952 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15952
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68912/
Test PASSed.
---
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/15893
ð
---
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/15952
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/15926#discussion_r88824474
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/MetastoreDataSourcesSuite.scala
---
@@ -413,6 +413,40 @@ class MetastoreDataSourcesSuite
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15951
**[Test build #68913 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68913/consoleFull)**
for PR 15951 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15926
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/15952
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68911/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15952
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/15952
**[Test build #68911 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68911/consoleFull)**
for PR 15952 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15952
**[Test build #68912 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68912/consoleFull)**
for PR 15952 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15952
@felixcheung , I just noticed that the API documentation for `context.R`,
`RDD.R` and `pairRDD.R` seems not appearing in the documentation. Is this true?
I ended up with getting rid of them
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/15952#discussion_r88822185
--- Diff: R/pkg/R/functions.R ---
@@ -2779,7 +2779,8 @@ setMethod("window", signature(x = "Column"),
#' locate
#'
#' Locate the position
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/15952#discussion_r88822111
--- Diff: R/pkg/R/functions.R ---
@@ -2341,7 +2341,7 @@ setMethod("from_utc_timestamp", signature(y =
"Column", x = "character"),
#' Locate the
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/15952#discussion_r88822027
--- Diff: R/pkg/R/functions.R ---
@@ -2296,7 +2296,7 @@ setMethod("n", signature(x = "Column"),
#' A pattern could be for instance
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15952
**[Test build #68911 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68911/consoleFull)**
for PR 15952 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/15952#discussion_r88821734
--- Diff: R/pkg/R/DataFrame.R ---
@@ -2541,7 +2541,8 @@ generateAliasesForIntersectedCols <- function (x,
intersectedColNames, suffix) {
#'
#'
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/15952
[WIP][SPARK-18514][DOCS] Fix the markdown for `Note:`/`NOTE:`/`Note that`
across R API documentation
## What changes were proposed in this pull request?
It seems in R, there are
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15901
LGTM cc @cloud-fan for another 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 feature
Github user witgo commented on the issue:
https://github.com/apache/spark/pull/14995
@srowen
This PR is a comprehensive solution. Used to solve address various 2G
limits, RPC memory footprint and other issues.
Users often encounter these problems. Why don't we need to solve
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/15945
@hvanhovell @cloud-fan I think this target might be 2.2.0, so could you
check this after 2.1 is cut. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15951
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/15951
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68910/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15951
**[Test build #68910 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68910/consoleFull)**
for PR 15951 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15951
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68909/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15951
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/15951
**[Test build #68909 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68909/consoleFull)**
for PR 15951 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15949
@tcondie can you use all upper case for the JIRA ticket in the future, e.g.
SPARK-18339?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
1 - 100 of 194 matches
Mail list logo
