Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/16193#discussion_r91609923
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/python/ExtractPythonUDFs.scala
---
@@ -165,4 +167,31 @@ object ExtractPythonUDFs extends Rul
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16200
**[Test build #69880 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69880/consoleFull)**
for PR 16200 at commit
[`0dc4c94`](https://github.com/apache/spark/commit/0
Github user mengxr commented on the issue:
https://github.com/apache/spark/pull/16154
Confirmed this patch fixed the issue in our environment:)
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/16218
---
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 ena
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16219
**[Test build #69879 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69879/consoleFull)**
for PR 16219 at commit
[`fc1557e`](https://github.com/apache/spark/commit/f
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/16218
No worries. Since this isn't tested by jenkins, I'm going to merge this and
test this manually
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHu
GitHub user tcondie opened a pull request:
https://github.com/apache/spark/pull/16219
[SPARK-18790][SS] Keep a general offset history of stream batches
## What changes were proposed in this pull request?
Instead of only keeping the minimum number of offsets around, we should
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16191
---
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 ena
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14561
---
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 ena
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13026
---
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 ena
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16198
---
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 ena
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7739
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14223
---
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 ena
Github user vanzin closed the pull request at:
https://github.com/apache/spark/pull/16217
---
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 ena
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16217
Ah, cool. I was planning to do that later, but since you already did,
closing.
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16217
Similar to the last pr i coudln't merge this with merge tool but I pushed
directly to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user mengxr commented on the issue:
https://github.com/apache/spark/pull/16154
@yhuai @jkbradley I'm testing the patch in our environment to see whether
it actually solves the problem.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16216
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 feature
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16187
---
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 ena
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14680
---
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 ena
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16193#discussion_r91604263
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/python/ExtractPythonUDFs.scala
---
@@ -166,3 +174,40 @@ object ExtractPythonUDFs extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16193
**[Test build #69878 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69878/consoleFull)**
for PR 16193 at commit
[`3d9ba67`](https://github.com/apache/spark/commit/3
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16187
Fixed- let me merge this in master/branch-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 featu
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16218
LGTM.
Sorry about 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 have this feature
enabl
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16200
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69867/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16200
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
e
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16148
Agreed. We will definitely keep that in mind but there is certainly a lot
going in working the API already.
---
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/16200
**[Test build #69867 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69867/consoleFull)**
for PR 16200 at commit
[`cf32d3c`](https://github.com/apache/spark/commit/
Github user velvia commented on the issue:
https://github.com/apache/spark/pull/15219
Hi, in my experience, interfaces which are implemented by final methods are
inlined just fine in the JVM JITâ¦. but you might know more about this.
The point is more simplification and that the
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16217
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 feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13579
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69868/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13579
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13579
**[Test build #69868 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69868/consoleFull)**
for PR 13579 at commit
[`f375682`](https://github.com/apache/spark/commit/
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/15219
@velvia Thank you for your comment. It is interesting from the view of
simplification.
On the other hand, I think that current implementation thinks about
performance to encourage method inlining
Github user rezasafi commented on the issue:
https://github.com/apache/spark/pull/15275
Any update on the decision of whether this fix will be backported to 1.6?
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16218
**[Test build #69877 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69877/consoleFull)**
for PR 16218 at commit
[`abae93c`](https://github.com/apache/spark/commit/a
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/16218
cc @felixcheung @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
GitHub user shivaram opened a pull request:
https://github.com/apache/spark/pull/16218
Change the R source build to Hadoop 2.6
This PR changes the SparkR source release tarball to be built using the
Hadoop 2.6 profile. Previously it was using the without hadoop profile which
leads
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/16014
@felixcheung I triggered a nightly build on branch-2.1 and this doesn't
work correctly in the no-hadoop build. While building the vignettes we run into
an error -- I'm going to change this to use a
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16195
**[Test build #69875 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69875/consoleFull)**
for PR 16195 at commit
[`2f2a6e3`](https://github.com/apache/spark/commit/2
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16043
**[Test build #69876 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69876/consoleFull)**
for PR 16043 at commit
[`7ddc5db`](https://github.com/apache/spark/commit/7
Github user eyalfa commented on the issue:
https://github.com/apache/spark/pull/16043
@HyukjinKwon , I think I've handled all of your comments but two:
1. the one with pattern matching on `elems` (please see comment)
2. use of the Matchers syntax in tests, please respond to comm
Github user mengxr commented on the issue:
https://github.com/apache/spark/pull/16214
@yanboliang What happens if there are multiple executors on the same
machine? Are there concurrency issues?
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16205
Oh, please also support to read the old format in case RC2 is 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
Github user eyalfa commented on a diff in the pull request:
https://github.com/apache/spark/pull/16043#discussion_r91596315
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/complexTypesSuite.scala
---
@@ -0,0 +1,482 @@
+/*
+ * Licensed to the A
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16205
LGTM. Merging to master and 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 an
Github user eyalfa commented on a diff in the pull request:
https://github.com/apache/spark/pull/16043#discussion_r91595458
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/ComplexTypes.scala
---
@@ -0,0 +1,131 @@
+/*
+ * Licensed to the Apache
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16217
**[Test build #69874 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69874/consoleFull)**
for PR 16217 at commit
[`dee1efe`](https://github.com/apache/spark/commit/d
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16178
---
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 ena
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16217
Let's see if others have anything to add. @srowen @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
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/16217
Close stale PRs.
Closes #16191
Closes #16198
Closes #14561
Closes #14223
Closes #7739
Closes #13026
You can merge this pull request into a Git repository by running:
$ git p
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16178
Thanks! Merging to master and 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 vanzin commented on the issue:
https://github.com/apache/spark/pull/13026
I'm gonna propose we close this because (1) this is an old Mesos version
being terribly broken and (2) spark-class is not expected to be able to write
to `$SPARK_HOME`, much less its parent, so the f
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/16148
@felixcheung This is fine to merge since it is for docs/examples only. But
in general, we should be better about adding these right away after adding the
R APIs, rather than doing them all at the
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/16195#discussion_r91592278
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/ClientArguments.scala ---
@@ -61,11 +61,15 @@ private[spark] class ClientArguments(args:
Array[Str
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/15787
Ah, thank you @bravo-zhang !
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16176
**[Test build #69873 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69873/consoleFull)**
for PR 16176 at commit
[`8d23a00`](https://github.com/apache/spark/commit/8
Github user velvia commented on the issue:
https://github.com/apache/spark/pull/15219
@kiszk I had a quick look at your `ColumnarVector` and had some thoughts.
Right now, it seems `ColumnVector` as an abstract class mixes lots of
functionalities into one.
- Methods fo
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/16017#discussion_r91591028
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/DecisionTreeClassifier.scala
---
@@ -52,33 +52,49 @@ class DecisionTreeClassifier @Since
Github user daisukebe commented on a diff in the pull request:
https://github.com/apache/spark/pull/16195#discussion_r91589664
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/ClientArguments.scala ---
@@ -61,11 +61,15 @@ private[spark] class ClientArguments(args:
Array[
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16209
**[Test build #69871 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69871/consoleFull)**
for PR 16209 at commit
[`faa8172`](https://github.com/apache/spark/commit/f
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16176
**[Test build #69872 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69872/consoleFull)**
for PR 16176 at commit
[`3e6e8fa`](https://github.com/apache/spark/commit/3
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16014
---
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 ena
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16209
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 shivaram commented on the issue:
https://github.com/apache/spark/pull/16014
LGTM. I took another look at `release-build.sh` and I think it looks fine.
Merging this into master, branch-2.1. I'll also see if I can test this out
somehow on jenkins
---
If your project is se
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13579#discussion_r91587654
--- Diff:
core/src/test/scala/org/apache/spark/deploy/history/HistoryServerSuite.scala ---
@@ -349,6 +349,17 @@ class HistoryServerSuite extends SparkFunSuite
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16154
**[Test build #69870 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69870/consoleFull)**
for PR 16154 at commit
[`efe332d`](https://github.com/apache/spark/commit/e
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16164
It's on purpose.
> It still may misleads users in some cases, like 'scheduling delay' in
'ms' and 'processing time' in 's' or 'min'
I don't get it. I saw the time units in your scre
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16216
**[Test build #69869 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69869/consoleFull)**
for PR 16216 at commit
[`841ac5d`](https://github.com/apache/spark/commit/8
Github user mengxr commented on the issue:
https://github.com/apache/spark/pull/16154
@falaki I'm happy to add the first Scala unit test for `RBackend`:)
---
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 doe
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/16154#discussion_r91586125
--- Diff: core/src/main/scala/org/apache/spark/api/r/RBackendHandler.scala
---
@@ -143,12 +142,8 @@ private[r] class RBackendHandler(server: RBackend)
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16203
Submitted #16216 to backport it to 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
ena
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/16216
[SPARK-18774][CORE][SQL] Ignore non-existing files when ignoreCorruptFiles
is enabled (branch 2.1)
## What changes were proposed in this pull request?
Backport #16203 to branch 2.1.
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/13579
done
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/16121
---
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 ena
Github user davies commented on the issue:
https://github.com/apache/spark/pull/16121
LGTM, merging into master and 2.1 branch, 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 fe
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16193
ExistingRDD might not be always the child of `Filter`. For example,
```Python
>>> sel = df.select('key', 'value', rand()).filter((my_filter(col("key")))
& (df.value < "2"))
```
``
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/16014#discussion_r91583848
--- Diff: dev/create-release/release-build.sh ---
@@ -172,11 +172,30 @@ if [[ "$1" == "package" ]]; then
MVN_HOME=`$MVN -version 2>&1 | grep 'Maven
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13579
While tests are running, can you update the description? It mentions env
vars, which is misleading since they don't have anything to do with this.
---
If your project is set up for it, you can reply
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/16014#discussion_r91579011
--- Diff: dev/create-release/release-build.sh ---
@@ -221,14 +235,13 @@ if [[ "$1" == "package" ]]; then
# We increment the Zinc port each time
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16213
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16213
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69863/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16213
**[Test build #69863 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69863/consoleFull)**
for PR 16213 at commit
[`e8a4e1d`](https://github.com/apache/spark/commit/
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/16150
Yeah. This is mostly docs fixes - I think this is fine to go into
branch-2.1. We can see which RC gets promoted etc.
---
If your project is set up for it, you can reply to this email and have your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16165
---
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 ena
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16165
Merging to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13579
**[Test build #69868 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69868/consoleFull)**
for PR 13579 at commit
[`f375682`](https://github.com/apache/spark/commit/f
Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/13579
stylecheck; unexpected, as I thought I'd run them in the `mvn install` of
the module.
```
[error]
/home/jenkins/workspace/SparkPullRequestBuilder/core/src/test/scala/org/apache/spark/d
Github user seyfe commented on the issue:
https://github.com/apache/spark/pull/16165
Thank @vanzin. Updated the description based on final state.
---
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 ha
Github user zhzhan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16068#discussion_r91569919
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveUDFSuite.scala
---
@@ -487,6 +489,26 @@ class HiveUDFSuite extends QueryTest with
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16200
**[Test build #69867 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69867/consoleFull)**
for PR 16200 at commit
[`cf32d3c`](https://github.com/apache/spark/commit/c
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16165
Code LGTM but can you update the description to reflect the recent changes
to the PR?
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/16000
If you're not willing to make the changes, we should close this one, if you
don't mind, and reopen @uncleGen's PR instead.
---
If your project is set up for it, you can reply to this email and have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16202
---
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 ena
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16200
hmm. 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 vanzin commented on the issue:
https://github.com/apache/spark/pull/16202
Merging to master to make the builds happy.
---
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/16195
**[Test build #69866 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69866/consoleFull)**
for PR 16195 at commit
[`10e0c75`](https://github.com/apache/spark/commit/1
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16202
Yeah, mesos was missing. But I guess that only affects a tiny number of
people who'd like to use SPARK_PREPEND_CLASSES while changing that mesos code,
so probably nobody noticed.
---
If your projec
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16121
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16121
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69865/
Test PASSed.
---
301 - 400 of 515 matches
Mail list logo
