Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16857
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/16857
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73003/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16857
**[Test build #73003 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73003/testReport)**
for PR 16857 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16957
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73001/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16957
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/16957
**[Test build #73001 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73001/testReport)**
for PR 16957 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16960
**[Test build #73005 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73005/testReport)**
for PR 16960 at commit
Github user cherryii commented on the issue:
https://github.com/apache/spark/pull/9608
Yes
---
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 radekg commented on the issue:
https://github.com/apache/spark/pull/9608
Is this running on Mesos?
---
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 erikerlandson commented on the issue:
https://github.com/apache/spark/pull/13440
Hi @wangmiao1981,
I am still interested in this, but I don't have any sense about whether
upstream has any interest. Does upstream have any intention to accept it?
---
If your
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16954
cc @hvanhovell I did the internal review. It is ready for you to review it.
Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16960
cc @hvanhovell if you have a min to review 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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16960#discussion_r101575264
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/metric/SQLMetricsSuite.scala
---
@@ -309,4 +314,84 @@ class SQLMetricsSuite extends
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16960#discussion_r101575199
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/metric/SQLMetricsSuite.scala
---
@@ -309,4 +314,84 @@ class SQLMetricsSuite extends
Github user cherryii commented on the issue:
https://github.com/apache/spark/pull/15120
I am using spark 2.1.0, my docker container is a spark driver that only
runs my job, my container's entrypoint is a script that runs spark submit. I
use the client deploy-mode, set the conf values
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16960
**[Test build #73004 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73004/testReport)**
for PR 16960 at commit
GitHub user ala opened a pull request:
https://github.com/apache/spark/pull/16960
[SPARK-19447] Make Range operator generate "recordsRead" metric
## What changes were proposed in this pull request?
The Range was modified to produce "recordsRead" metric instead of
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16959
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 pwoody opened a pull request:
https://github.com/apache/spark/pull/16959
[SPARK-19631][CORE] OutputCommitCoordinator should not allow commits for
already failed tasks
## What changes were proposed in this pull request?
Previously it was possible for there to be
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16956
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72999/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16956
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/16956
**[Test build #72999 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72999/testReport)**
for PR 16956 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16958
So nice when I got two LGTMs and then Jenkins disagreed.
---
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 budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/16944#discussion_r101560890
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveMetastoreCatalog.scala ---
@@ -161,23 +161,49 @@ private[hive] class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16958
**[Test build #73002 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73002/testReport)**
for PR 16958 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16958
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/16958
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73002/
Test FAILed.
---
Github user budde commented on a diff in the pull request:
https://github.com/apache/spark/pull/16944#discussion_r101562475
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -296,6 +296,17 @@ object SQLConf {
.longConf
Github user bogdanrdc commented on the issue:
https://github.com/apache/spark/pull/16958
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16826
What's WIP 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 not have this feature
enabled and wishes
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16611
For SQL, rather than "array", can we follow Python, e.g.
```
CREATE TEMPORARY TABLE tableA USING csv
OPTIONS (nullValue ['NA', 'null'], ...)
```
---
If your project is set up for
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16611#discussion_r101553890
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameReader.scala ---
@@ -97,6 +99,15 @@ class DataFrameReader private[sql](sparkSession:
Github user cherryii commented on the issue:
https://github.com/apache/spark/pull/9608
I am using docker, my container is a spark driver that only runs my job, my
container's entrypoint is a script that runs spark submit. I use the client
deploy-mode and set all the config values you
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16534
Change looks good to me but I didn't look super carefully.
@holdenk can you take a look at this?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user radekg commented on the issue:
https://github.com/apache/spark/pull/9608
Are you deploying with Docker? If so, what problems are you facing when
using host networking?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16958
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16476
**[Test build #72994 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72994/testReport)**
for PR 16476 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16958
**[Test build #73002 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73002/testReport)**
for PR 16958 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16476
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72994/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16476
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 windpiger commented on a diff in the pull request:
https://github.com/apache/spark/pull/16672#discussion_r101541205
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/command/DDLSuite.scala
---
@@ -1816,4 +1816,123 @@ class DDLSuite extends QueryTest
Github user windpiger commented on a diff in the pull request:
https://github.com/apache/spark/pull/16672#discussion_r101541033
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/command/DDLSuite.scala
---
@@ -1816,4 +1816,123 @@ class DDLSuite extends QueryTest
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16857
**[Test build #73003 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73003/testReport)**
for PR 16857 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16927
Hm.. @felixcheung, the origin seems from Hadoop's issue.
```
java.io.IOException: (null) entry in command string: null chmod 0644
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16857
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73000/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16857
**[Test build #73000 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73000/testReport)**
for PR 16857 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16958
cc @hvanhovell @bogdanrdc
---
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 rxin opened a pull request:
https://github.com/apache/spark/pull/16958
[SPARK-13721][SQL] Make GeneratorOuter unresolved.
## What changes were proposed in this pull request?
This is a small change to make GeneratorOuter always unresolved. It is
mostly no-op change
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/16938
@cloud-fan @gatorsmile @tejasapatil let's discuss this together?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16957
**[Test build #73001 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73001/testReport)**
for PR 16957 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16857
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 srowen opened a pull request:
https://github.com/apache/spark/pull/16957
[SPARK-19550][HOTFIX][BUILD] Use JAVA_HOME/bin/java if JAVA_HOME is set in
dev/mima
## What changes were proposed in this pull request?
Use JAVA_HOME/bin/java if JAVA_HOME is set in
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16857
**[Test build #73000 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73000/testReport)**
for PR 16857 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16956
**[Test build #72999 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72999/testReport)**
for PR 16956 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16871
Yep, since `dev/mima` runs just `java`, it's likely picking up Java 7 from
the Jenkins machines. The jobs all set `JAVA_HOME`, and set it to the Java 8
home. Other Spark scripts here will use
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16857
**[Test build #72998 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72998/testReport)**
for PR 16857 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16857
**[Test build #72998 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72998/testReport)**
for PR 16857 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16857
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72998/
Test FAILed.
---
Github user windpiger commented on a diff in the pull request:
https://github.com/apache/spark/pull/16956#discussion_r101535507
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/ResolveHints.scala
---
@@ -54,10 +54,6 @@ object ResolveHints {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16857
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/16857
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/16857
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72997/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16857
**[Test build #72997 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72997/testReport)**
for PR 16857 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16857
**[Test build #72997 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72997/testReport)**
for PR 16857 at commit
Github user imatiach-msft commented on a diff in the pull request:
https://github.com/apache/spark/pull/16722#discussion_r101532020
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tree/impl/BaggedPoint.scala ---
@@ -60,12 +68,14 @@ private[spark] object BaggedPoint {
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16871
This caused the SBT build to fail because MiMa doesn't like Java 8
bytecode, but this might be simple config issue. Investigating ...
Github user imatiach-msft commented on a diff in the pull request:
https://github.com/apache/spark/pull/16722#discussion_r101531848
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/classification/DecisionTreeClassifierSuite.scala
---
@@ -351,6 +370,36 @@ class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16956
**[Test build #72996 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72996/testReport)**
for PR 16956 at commit
Github user yaooqinn commented on the issue:
https://github.com/apache/spark/pull/16955
@srowen @jerryshao Thanks for your comments. I have added some
descriptions both in the JIRA and here, please check whether OK or not.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16956
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72996/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16956
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/16956
**[Test build #72996 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72996/testReport)**
for PR 16956 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16956
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/16956
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72995/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16956
**[Test build #72995 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72995/testReport)**
for PR 16956 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16956
**[Test build #72995 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72995/testReport)**
for PR 16956 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16956#discussion_r101530187
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/ResolveHints.scala
---
@@ -54,10 +54,6 @@ object ResolveHints {
GitHub user windpiger opened a pull request:
https://github.com/apache/spark/pull/16956
[SPARK-19598][SQL]Remove the alias parameter in UnresolvedRelation
## What changes were proposed in this pull request?
Remove the alias parameter in `UnresolvedRelation`, and use
Github user cherryii commented on the issue:
https://github.com/apache/spark/pull/9608
The reason I'm asking is because bridge networking would solve a lot of
other problems. So does that mean bridge networking on mesos and docker isn't
supported right now?
---
If your project is
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16928
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72993/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16928
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/16928
**[Test build #72993 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72993/testReport)**
for PR 16928 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16476#discussion_r101516174
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -340,3 +343,104 @@ object CaseKeyWhen {
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/16476#discussion_r101515786
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -340,3 +341,91 @@ object CaseKeyWhen {
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16936
Let us call @zsxwing for some suggestions.
---
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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/16949
@srowen good questionï¼IMHOï¼we should add this API:
- provide complete API, the same as users see in webui
- if this is a security issue, we should address it in other ways
-
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/16955
Agreed with @srowen , please describe the problem and fix both here in PR
and in JIRA, also changing the title to be more meaningful. It would be better
for others without the context to
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16926
---
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/16926
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/16871
---
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/16871
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 srowen commented on the issue:
https://github.com/apache/spark/pull/16949
It's a simple change, but I wonder if this is that important to add?
I always have a worry in the back of my mind that this becomes a security
hole, as it's a way to look through the complete
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16955
There's no detail in the JIRA or PR. I can't tell whether you are solving
the problem you set out to solve. Are you saying this is the entire problem,
that the wrong config is being queried?
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16476
**[Test build #72994 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72994/testReport)**
for PR 16476 at commit
Github user gczsjdy commented on a diff in the pull request:
https://github.com/apache/spark/pull/16476#discussion_r101505199
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/conditionalExpressions.scala
---
@@ -340,3 +341,91 @@ object CaseKeyWhen {
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/16924#discussion_r101502214
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/EventLoggingListener.scala ---
@@ -137,7 +138,13 @@ private[spark] class EventLoggingListener(
Github user dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/16954
cc @hvanhovell @gatorsmile @nsyca
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/16936
Hm it just seems like the wrong approach, to externally estimate whether in
theory it won't schedule. It is certainly a problem if streaming doesn't work
though users would already realize it. The
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16954
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72992/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16954
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
401 - 500 of 547 matches
Mail list logo
