Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/19047#discussion_r135247004
--- Diff:
launcher/src/main/java/org/apache/spark/launcher/AbstractCommandBuilder.java ---
@@ -136,7 +136,8 @@ void addOptionString(List cmd, String
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/19053#discussion_r135235516
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/UserDefinedTypeSuite.scala ---
@@ -203,12 +203,14 @@ class UserDefinedTypeSuite extends QueryTest
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18730
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/19008
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81126/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18730
**[Test build #81125 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81125/testReport)**
for PR 18730 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18730
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81125/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19008
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/19008
**[Test build #81126 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81126/testReport)**
for PR 19008 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15435
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/15435
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81124/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15435
**[Test build #81124 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81124/testReport)**
for PR 15435 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19029
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/19029
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81129/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19029
**[Test build #81129 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81129/testReport)**
for PR 19029 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19029
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81127/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19029
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/19029
**[Test build #81127 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81127/testReport)**
for PR 19029 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19053
**[Test build #81130 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81130/testReport)**
for PR 19053 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18994
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/18994
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81123/
Test PASSed.
---
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/19053
[SPARK-21837][SQL][TESTS] UserDefinedTypeSuite local UDFs not actually
testing what it intends
## What changes were proposed in this pull request?
Adjust Local UDTs test to assert about
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18994
**[Test build #81123 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81123/testReport)**
for PR 18994 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18787
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/18787
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81122/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18787
**[Test build #81122 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81122/testReport)**
for PR 18787 at commit
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/18902
@zhengruifeng DataFrame-based operation is 2~3x slower than RDD-based
operation is a known issue, because of the deserialization cost. If we switch
to RDD-based method, we need to implement our
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18918
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19050
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81121/
Test PASSed.
---
GitHub user heary-cao reopened a pull request:
https://github.com/apache/spark/pull/18918
[SPARK-21707][SQL]Improvement a special case for non-deterministic filters
in optimizer
## What changes were proposed in this pull request?
Currently, Did a lot of special handling
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19050
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/19050
**[Test build #81121 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81121/testReport)**
for PR 19050 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19029
**[Test build #81129 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81129/testReport)**
for PR 19029 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19051
**[Test build #3902 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3902/testReport)**
for PR 19051 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18730
**[Test build #81128 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81128/testReport)**
for PR 18730 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19051
**[Test build #3901 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3901/testReport)**
for PR 19051 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19029
**[Test build #81127 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81127/testReport)**
for PR 19029 at commit
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/19029#discussion_r135216154
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/optim/WeightedLeastSquares.scala ---
@@ -440,7 +440,7 @@ private[ml] object WeightedLeastSquares {
Github user LiShuMing commented on the issue:
https://github.com/apache/spark/pull/19052
Sorry, don't pull this request. I will close 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
Github user LiShuMing closed the pull request at:
https://github.com/apache/spark/pull/19052
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/19052
Isn't this already fixed in
https://github.com/apache/spark/commit/846bc61cf5aa522dc755d50359ef3856ef2b17bf?
---
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/19008
**[Test build #81126 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81126/testReport)**
for PR 19008 at commit
Github user mdespriee commented on the issue:
https://github.com/apache/spark/pull/17461
Hi @hhbyyh, @jkbradley
a gentle ping on this PR. It's not WIP anymore, and ready for a review.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18730#discussion_r135203892
--- Diff:
core/src/main/scala/org/apache/spark/internal/config/package.scala ---
@@ -293,6 +293,13 @@ package object config {
.booleanConf
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18730
**[Test build #81125 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81125/testReport)**
for PR 18730 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18730#discussion_r135203827
--- Diff:
core/src/main/scala/org/apache/spark/util/io/ChunkedByteBuffer.scala ---
@@ -56,7 +63,9 @@ private[spark] class ChunkedByteBuffer(var chunks:
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18730
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19052
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 LiShuMing opened a pull request:
https://github.com/apache/spark/pull/19052
[Doc] ExchangeCoordinator description num error
## What changes were proposed in this pull request?
In `ExchangeCoordinator.scala` , this maybe just a mistake occasionally
which is
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15435
**[Test build #81124 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81124/testReport)**
for PR 15435 at commit
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/15435
Jenkins 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
Github user Geek-He commented on a diff in the pull request:
https://github.com/apache/spark/pull/19025#discussion_r135200981
--- Diff: core/src/main/java/org/apache/spark/memory/TaskMemoryManager.java
---
@@ -53,7 +53,7 @@
* retrieve the base object.
*
* This
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18994
**[Test build #81123 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81123/testReport)**
for PR 18994 at commit
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/19049
spark.mesos.dispatcher.historyServer.url
Set the URL of the http://spark.apache.org/docs/latest/monitoring.html#viewing-after-the-fact;>history
server. The dispatcher will
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/19016
I tested with the nightly, it passed
https://builder.r-hub.io/status/SparkR_2.2.0.tar.gz-fba296d2142edeb8bcdb082e311d8462
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18787
**[Test build #81122 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81122/testReport)**
for PR 18787 at commit
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/18787
Updated to use the new API for ColumnarBatch, please take a look @ueshin
@cloud-fan
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user YannByron commented on the issue:
https://github.com/apache/spark/pull/16138
@anabranch
I met a failure case when using `to_date`, like this:
```
spark-sql> select func(to_date('2017-08-25 12:00:00'));
```
`func` is a custom udf which extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19051
**[Test build #3901 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3901/testReport)**
for PR 19051 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19050
**[Test build #81121 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81121/testReport)**
for PR 19050 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/19049
I don't know how else to ask the question. I'd close this if there's no
answer to 'why' this is of use.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/19050
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19048
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81116/
Test FAILed.
---
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/19025#discussion_r135195514
--- Diff: core/src/main/java/org/apache/spark/memory/TaskMemoryManager.java
---
@@ -53,7 +53,7 @@
* retrieve the base object.
*
* This
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19048
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/19048
**[Test build #81116 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81116/testReport)**
for PR 19048 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15435
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/15435
**[Test build #81119 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81119/testReport)**
for PR 15435 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19050
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81117/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19051
**[Test build #81120 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81120/testReport)**
for PR 19051 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19050
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/15435
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81119/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19050
**[Test build #81117 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81117/testReport)**
for PR 19050 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19051
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/19051
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81120/
Test FAILed.
---
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/19025#discussion_r135195213
--- Diff: core/src/main/java/org/apache/spark/memory/TaskMemoryManager.java
---
@@ -74,7 +74,7 @@
* Maximum supported data page size (in bytes). In
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/19049
When the application starts, spark will generate an app directory in the
event log directory.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user iamhumanbeing commented on the issue:
https://github.com/apache/spark/pull/19037
ok. I will close this 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
Github user iamhumanbeing closed the pull request at:
https://github.com/apache/spark/pull/19037
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/19049
When would the history server receive events from clusters with different
resource managers?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19029
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/81118/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19029
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/19029
**[Test build #81118 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81118/testReport)**
for PR 19029 at commit
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/19049
Sorryï¼I do not understand what you mean.
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/19049
This still isn't addressing the point: when would they not _all_ be YARN?
---
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 guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/19049
For example, I would like to view some of the applications of the resource
schedule of yarn, I can sort the 'master' column.
---
If your project is set up for it, you can reply to this
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/19049
What does knowing the resource scheduler help? but my point is, it's
already known in general.
A history server most certainly collects history from different users'
apps, but not from different
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/19049
1.It is more convenient for the observer to more easily know the resource
scheduling mode of the current spark application.
2.For the 'Spark User' column. It would be identical in
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/18488
---
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/18488
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/19051
**[Test build #81120 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81120/testReport)**
for PR 19051 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/19051#discussion_r135190132
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/tuning/CrossValidatorSuite.scala ---
@@ -187,14 +187,13 @@ class CrossValidatorSuite
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/19051#discussion_r135190085
--- Diff:
common/kvstore/src/main/java/org/apache/spark/util/kvstore/KVStoreIterator.java
---
@@ -31,7 +32,7 @@
*
*/
@Private
-public
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/19051#discussion_r135190194
--- Diff: pom.xml ---
@@ -2058,7 +2058,7 @@
${java.version}
-target
${java.version}
-
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/19051
[MINOR][BUILD] Fix build warnings and Java lint errors
## What changes were proposed in this pull request?
Fix build warnings and Java lint errors. This just helps a bit in
evaluating
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/19049
What's the value of this column? In just about all cases it will have the
same value in every row, like 'yarn'. Even if not, why is it useful?
---
If your project is set up for it, you can reply to
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/19049
Sorry, I did not understand what you meant.
---
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/15435
**[Test build #81119 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/81119/testReport)**
for PR 15435 at commit
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/15435
Jenkins 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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/19049
Why? It would be identical in almost all use cases.
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/19037
Same, why do you think the test can or should be more specific? There is no
motivation
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
201 - 300 of 300 matches
Mail list logo
