GitHub user ConeyLiu opened a pull request:
https://github.com/apache/spark/pull/15864
[SPARK-18420]Fix the compile errors caused by checkstyle
## What changes were proposed in this pull request?
Small fix, fix the compile errors caused by checkstyle
## How was
Github user ConeyLiu closed the pull request at:
https://github.com/apache/spark/pull/15864
---
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 issue:
https://github.com/apache/spark/pull/15863
Thank you for review, @gatorsmile .
In the Spark code, `JDBCOption` is always receiving `CaseInsensitiveMap`.
For example, here.
-
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15862
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15863
Not always. Try this code path.
```Scala
val df = spark.createDataFrame(sparkContext.parallelize(arr2x2),
schema2)
df.write.format("jdbc")
.option("URL", url1)
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
So @joshrosen or @davies now that I've updated the shell scripts does this
look good to go?
I'll make a follow up to maybe add shellcheck to our standard linting if
it's something we want
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15851#discussion_r87693230
--- Diff: mllib/src/main/scala/org/apache/spark/ml/r/RWrapperUtils.scala ---
@@ -41,5 +41,29 @@ object RWrapperUtils extends Logging {
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15863
Hi @dongjoon-hyun, I just happened to look at this PR and I am just
curious. Would this be possible to override `filterKeys` in
`CastInsensitiveMap` as something like below?
```scala
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15861
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68562/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15861
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/13837
**[Test build #68567 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68567/consoleFull)**
for PR 13837 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15863
Oh, sure. I'll investigate it.
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15866
Build started: [CORE] `org.apache.spark.JavaAPISuite`
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/15863#discussion_r87700361
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -314,8 +311,7 @@ case class DataSource(
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15860
re-ping @joshrosen?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15863
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/15863
**[Test build #68572 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68572/consoleFull)**
for PR 15863 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15863
Yes. It seems not to solve this problem. The problem is the following list
is case-sensitive.
```
private val jdbcOptionNames = ArrayBuffer.empty[String]
```
---
If your project
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/15866
[SPARK-18422][CORE] Fix wholeTextFiles test to pass on Windows in
JavaAPISuite
## What changes were proposed in this pull request?
This PR fixes the test `wholeTextFiles` in
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
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 HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/15867
[WIP][SPARK-18423][Streaming] ReceiverTracker should close checkpoint dir
when stopped even if it was not started
## What changes were proposed in this pull request?
Several tests are
Github user pwoody closed the pull request at:
https://github.com/apache/spark/pull/14733
---
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 pwoody commented on the issue:
https://github.com/apache/spark/pull/14733
Closing stale PR
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15655
**[Test build #68564 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68564/consoleFull)**
for PR 15655 at commit
Github user vijoshi commented on the issue:
https://github.com/apache/spark/pull/15655
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68565 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68565/consoleFull)**
for PR 15717 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15857
cc @dongjoon-hyun @cloud-fan
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15815
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68566/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15815
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 yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15851#discussion_r87693172
--- Diff: R/pkg/inst/tests/testthat/test_mllib.R ---
@@ -971,10 +971,15 @@ test_that("spark.randomForest Classification", {
predictions <-
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15863
Oh, it seems not. I just removed my suggestion. I will take a look at this
again if it is possible in similar way. Thanks!
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15863
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/15863
**[Test build #68563 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68563/consoleFull)**
for PR 15863 at commit
Github user anabranch commented on the issue:
https://github.com/apache/spark/pull/15815
Sounds good to me. I will update it shortly.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15659
**[Test build #68570 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68570/consoleFull)**
for PR 15659 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15857
Thank you for pining me, @gatorsmile . Thank you for fixing this,
@hvanhovell .
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15862
**[Test build #68568 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68568/consoleFull)**
for PR 15862 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15862
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/15862
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68568/
Test PASSed.
---
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/15851#discussion_r87693194
--- Diff: mllib/src/main/scala/org/apache/spark/ml/r/RWrapperUtils.scala ---
@@ -41,5 +41,29 @@ object RWrapperUtils extends Logging {
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/15826
Merged into master and branch-2.1. Thanks for reviewing.
---
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 ConeyLiu opened a pull request:
https://github.com/apache/spark/pull/15865
[SPARK-18420]Fix the compile errors caused by checkstyle
## What changes were proposed in this pull request?
Small fix, fix the compile errors caused by checkstyle
## How was
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15694
Would there be other things I should take care of maybe?
---
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 issue:
https://github.com/apache/spark/pull/15863
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68563/
Test PASSed.
---
Github user anabranch commented on the issue:
https://github.com/apache/spark/pull/15815
@srowen Think this is probably ready.
- [ ] Updated All Languages
- [ ] Updated Ticket Description
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15815
**[Test build #68566 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68566/consoleFull)**
for PR 15815 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15717#discussion_r87697174
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -273,6 +273,68 @@ case class AlterTableUnsetPropertiesCommand(
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15717#discussion_r87697240
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -273,6 +273,68 @@ case class AlterTableUnsetPropertiesCommand(
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15717
A basic question. Like Hive, we should not support `ALTER VIEW CHANGE
COLUMN`, right?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15815
https://cloud.githubusercontent.com/assets/6477701/20239969/3d5cb0ba-a950-11e6-8a55-e96e8cd02970.png;>
For Python documenation, it seems fine.
---
If your project is set up for it, you
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15863
Our user-specified JDBC options/parameters are case sensitive, right?
---
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 minrk commented on the issue:
https://github.com/apache/spark/pull/15659
Sounds great!
---
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/15815
**[Test build #68566 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68566/consoleFull)**
for PR 15815 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15866
@srowen It seems `org.apache.spark.JavaAPISuite.writeWithNewAPIHadoopFile`
is also being failed but the root cause seems different. That is being failed
with the exception as below:
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15815
**[Test build #68573 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68573/consoleFull)**
for PR 15815 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15863
**[Test build #68572 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68572/consoleFull)**
for PR 15863 at commit
Github user anabranch commented on the issue:
https://github.com/apache/spark/pull/15815
The test failure seems quite unrelated but we'll see if it happens again.
---
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 anabranch commented on a diff in the pull request:
https://github.com/apache/spark/pull/15815#discussion_r87699964
--- Diff: R/pkg/R/DataFrame.R ---
@@ -936,7 +936,9 @@ setMethod("unique",
#' Sample
#'
-#' Return a sampled subset of this
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15659
and or @rxin?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15866
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/15863
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68572/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15866
**[Test build #68569 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68569/consoleFull)**
for PR 15866 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15866
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68569/
Test PASSed.
---
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15863
Thank you for review, @HyukjinKwon . Let me see that.
---
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 issue:
https://github.com/apache/spark/pull/15865
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 project does not have this
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14788
Hi @rxin, do you mind if I ask what you do think about 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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15361
ping ..
---
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/15655
**[Test build #68564 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68564/consoleFull)**
for PR 15655 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15655
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68564/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15655
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15854
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15862
**[Test build #68568 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68568/consoleFull)**
for PR 15862 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15865
Hi @ConeyLiu, It seems
```
[ERROR]
src/main/java/org/apache/spark/io/NioBufferedFileInputStream.java:[133]
(coding) NoFinalizer: Avoid using finalizer method.
```
is
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15863
I updated `DataSource` consistently to use `CaseInsensitiveMap` and am
running tests.
After testing, this PR will include the followings.
- Fix `DataSource` to use
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15857
It looks good to me.
---
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 weiqingy commented on the issue:
https://github.com/apache/spark/pull/15858
@srowen Thanks for the 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
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15717
**[Test build #68565 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68565/consoleFull)**
for PR 15717 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15843
I'm not so sure about that, we still would want to cleanup the underlying
Java reference object on delete if it isn't needed anymore. I think the
question is do we want to support shallow copy of
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15867
**[Test build #68571 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68571/consoleFull)**
for PR 15867 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15826
---
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/15854
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15861
**[Test build #68562 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68562/consoleFull)**
for PR 15861 at commit
Github user anabranch commented on a diff in the pull request:
https://github.com/apache/spark/pull/15815#discussion_r87696862
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -1612,7 +1612,9 @@ class Dataset[T] private[sql](
}
/**
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15717
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/15717
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68565/
Test FAILed.
---
Github user anabranch commented on a diff in the pull request:
https://github.com/apache/spark/pull/15815#discussion_r87696853
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -1612,7 +1612,9 @@ class Dataset[T] private[sql](
}
/**
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15866
**[Test build #68569 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68569/consoleFull)**
for PR 15866 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13837
**[Test build #68567 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68567/consoleFull)**
for PR 13837 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13837
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68567/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15867
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68571/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15867
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/15867
**[Test build #68571 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68571/consoleFull)**
for PR 15867 at commit
Github user ConeyLiu commented on the issue:
https://github.com/apache/spark/pull/15865
@HyukjinKwon I'm sorry for that, I've fixed it, please take a look. Thanks
a lot.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15854
**[Test build #68578 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68578/consoleFull)**
for PR 15854 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15869
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 project does not have this
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15854
test 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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/13837
**[Test build #68579 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68579/consoleFull)**
for PR 13837 at commit
GitHub user weiqingy opened a pull request:
https://github.com/apache/spark/pull/15869
[YARN][DOC] Update Yarn configuration doc
## What changes were proposed in this pull request?
- Add documentation for two yarn configurations:
`spark.yarn.report.interval` and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15863
**[Test build #68574 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68574/consoleFull)**
for PR 15863 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15815
**[Test build #68573 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68573/consoleFull)**
for PR 15815 at commit
1 - 100 of 200 matches
Mail list logo
