Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/18605
@felixcheung This is a follow-up PR of JIRA-20307.
---
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 yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/18554#discussion_r126868713
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/OneVsRest.scala ---
@@ -317,7 +318,12 @@ final class OneVsRest @Since("1.4.0") (
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/18600#discussion_r126868678
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/DataSourceScanExec.scala
---
@@ -73,34 +72,24 @@ trait DataSourceScanExec extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18228
**[Test build #79550 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79550/testReport)**
for PR 18228 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18228
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/18228
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79548/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18228
**[Test build #79548 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79548/testReport)**
for PR 18228 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/18600#discussion_r126866057
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/DataSourceScanExec.scala
---
@@ -73,34 +72,24 @@ trait DataSourceScanExec extends
Github user janewangfb commented on the issue:
https://github.com/apache/spark/pull/18023
@gatorsmile
Sure, I could have a follow-up PR to resolve DataFrameNaFunctions.fill.
thanks for reviewing this PR.
---
If your project is set up for it, you can reply to this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/18023
---
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/18023
Thanks! 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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18023
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18023
The last comment is about `DataFrameNaFunctions.fill`. It does not work
when `spark.sql.parser.quotedRegexColumnNames` is on. Could you resolve that in
the follow-up PR?
---
If your project is
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18444
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/18444
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79547/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18444
**[Test build #79547 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79547/testReport)**
for PR 18444 at commit
Github user facaiy commented on a diff in the pull request:
https://github.com/apache/spark/pull/18554#discussion_r126863072
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/OneVsRest.scala ---
@@ -317,7 +318,12 @@ final class OneVsRest @Since("1.4.0") (
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/18594
I'm hesitant to support the change. If we don't notify the failure to
driver, the status of the failed task would not be updated, thus not
rescheduled, perhaps it's not the behavior we expect
Github user jsoltren commented on the issue:
https://github.com/apache/spark/pull/18604
My preference is to backport this and other blacklisting related fixes as
far back as possible on Spark2 - meaning 2.1 and 2.0 as well, unless convinced
otherwise. So, yes, @cloud-fan, I hope we
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18228#discussion_r126857958
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringExpressions.scala
---
@@ -1199,6 +1199,49 @@ case class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18604
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/18604
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79545/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18604
**[Test build #79545 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79545/testReport)**
for PR 18604 at commit
Github user heary-cao commented on the issue:
https://github.com/apache/spark/pull/18555
@gatorsmile @cloud-fan
please review it again.
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18555
**[Test build #79549 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79549/testReport)**
for PR 18555 at commit
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18601
@srowen thank you for your suggestion. I executed `mvn dependency:tree` in
the current master and the version with this PR. I confirmed that only the
difference is related to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18228
**[Test build #79548 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79548/testReport)**
for PR 18228 at commit
Github user liu-zhaokun commented on the issue:
https://github.com/apache/spark/pull/18606
@srowen
But now,spark 2.2.0 released.we know exactly that Scala 2.10 isn't removed
in Spark 2.2.0,so we shouldn't give the user an inaccurate message.
---
If your project is set up for
Github user liu-zhaokun commented on the issue:
https://github.com/apache/spark/pull/18596
@srowen @jiangxb1987
Hello,I have modified the PR according to your opinion.Could you help me
review it again.
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18606
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 srowen commented on the issue:
https://github.com/apache/spark/pull/18606
No, the statement was correct. It said may be removed.
---
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 liu-zhaokun opened a pull request:
https://github.com/apache/spark/pull/18606
[SPARK-21382] The note about Scala 2.10 in building-spark.md is wrong.
[https://issues.apache.org/jira/browse/SPARK-21382](https://issues.apache.org/jira/browse/SPARK-21382)
There should
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18444
**[Test build #79547 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79547/testReport)**
for PR 18444 at commit
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18468
@cloud-fan could you please 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 feature
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/18281
@ajaysaini725 @jkbradley Can we avoid python-side to re-implement the
logic of OneVsRest? It can simply python-side code I think. Just let the
wrapper inherit `JavaEstimator`, and when we
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79546/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18605
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/18605
**[Test build #79546 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79546/testReport)**
for PR 18605 at commit
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/18428
Also, can you please add "OneVsRest" to the PR and JIRA titles since this
touches that class?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/18428#discussion_r126849117
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/tuning/ValidatorParams.scala ---
@@ -183,8 +198,14 @@ private[ml] object ValidatorParams {
Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/18428
LGTM
I couldn't think of a great way to reduce code duplication between
JavaWrapper and OneVsRest.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user liu-zhaokun commented on the issue:
https://github.com/apache/spark/pull/18599
@srowen
I think spark provides the param,so I can pass it in the script.
---
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 liu-zhaokun commented on a diff in the pull request:
https://github.com/apache/spark/pull/18599#discussion_r126847486
--- Diff: sbin/spark-daemon.sh ---
@@ -78,6 +78,12 @@ spark_rotate_log ()
if [ -n "$2" ]; then
num=$2
--- End diff --
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18444
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/18444
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79544/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18444
**[Test build #79544 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79544/testReport)**
for PR 18444 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/18143
@ScrapCodes I think it should be bounded by
`spark.sql.kafkaConsumerCache.capacity`.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18603
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/18603
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79543/
Test PASSed.
---
Github user 10110346 commented on a diff in the pull request:
https://github.com/apache/spark/pull/18228#discussion_r126842908
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringExpressions.scala
---
@@ -1199,6 +1199,49 @@ case class
Github user 10110346 commented on a diff in the pull request:
https://github.com/apache/spark/pull/18228#discussion_r126842852
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/stringExpressions.scala
---
@@ -1199,6 +1199,49 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18603
**[Test build #79543 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79543/testReport)**
for PR 18603 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18605
**[Test build #79546 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79546/testReport)**
for PR 18605 at commit
GitHub user wangmiao1981 opened a pull request:
https://github.com/apache/spark/pull/18605
[SparkR][SPARK-21381]:SparkR: pass on setHandleInvalid for classification
algorithms
## What changes were proposed in this pull request?
SPARK-20307 Added handleInvalid option to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18604
**[Test build #79545 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79545/testReport)**
for PR 18604 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18604
ok to test
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/18604
I don't see why we shouldn't backport a fix to 2.2.
---
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/18357
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/18357
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79542/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18357
**[Test build #79542 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79542/testReport)**
for PR 18357 at commit
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/18604
Do we want to backport this to 2.2? @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
Github user bOOm-X commented on the issue:
https://github.com/apache/spark/pull/18253
@vanzin I put an ArrayBlockingQueue as you wanted
---
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 tdas commented on the issue:
https://github.com/apache/spark/pull/18603
LGTM!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18444
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79540/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18444
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/18444
**[Test build #79540 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79540/testReport)**
for PR 18444 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18444
**[Test build #79544 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79544/testReport)**
for PR 18444 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18604
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/18444
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/18444
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79539/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18444
**[Test build #79539 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79539/testReport)**
for PR 18444 at commit
GitHub user jsoltren opened a pull request:
https://github.com/apache/spark/pull/18604
[SPARK-21219][CORE] Task retry occurs on same executor due to race coâ¦
â¦ndition with blacklisting
There's a race condition in the current TaskSetManager where a failed task
is added
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15496
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/18598
---
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/18598
Thanks! 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
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/18602
Thanks @vanzin , based on the comment of JIRA, I will try another approach,
so closing it for now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jerryshao closed the pull request at:
https://github.com/apache/spark/pull/18602
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18603
**[Test build #79543 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79543/testReport)**
for PR 18603 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18601
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/18601
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79538/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18601
**[Test build #79538 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79538/testReport)**
for PR 18601 at commit
GitHub user brkyvz opened a pull request:
https://github.com/apache/spark/pull/18603
[SPARK-21370][SS] Add test for state reliability when one read-only state
store aborts after read-write state store commits
## What changes were proposed in this pull request?
During
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15009
@kishorvpatil are you planning to address the last bit of feedback
remaining here? It shouldn't be that hard to make that test better.
---
If your project is set up for it, you can reply to this
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18602
I commented on the bug.
---
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 jerryshao commented on the issue:
https://github.com/apache/spark/pull/18602
CC @vanzin @tgravescs would you please help to review? 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18357
**[Test build #79542 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79542/testReport)**
for PR 18357 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/18357
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/18602
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/18602
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79541/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18602
**[Test build #79541 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79541/testReport)**
for PR 18602 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18357
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79537/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18357
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 zasdfgbnm commented on a diff in the pull request:
https://github.com/apache/spark/pull/18444#discussion_r126809517
--- Diff: core/src/main/scala/org/apache/spark/api/python/SerDeUtil.scala
---
@@ -72,7 +72,11 @@ private[spark] object SerDeUtil extends Logging {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18357
**[Test build #79537 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79537/testReport)**
for PR 18357 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18587
I'm 99% sure there's nothing to do for YARN. This line takes care of it:
args.jars = mergeFileLists(args.jars, resolvedMavenCoordinates)
YARN cluster mode will distribute all
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18602
**[Test build #79541 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79541/testReport)**
for PR 18602 at commit
GitHub user jerryshao opened a pull request:
https://github.com/apache/spark/pull/18602
[SPARK-21377][YARN] Add a new configuration to extend AM classpath in yarn
client mode
## What changes were proposed in this pull request?
This PR propose a new configuration
Github user zasdfgbnm commented on a diff in the pull request:
https://github.com/apache/spark/pull/18444#discussion_r126806942
--- Diff: core/src/main/scala/org/apache/spark/api/python/SerDeUtil.scala
---
@@ -72,7 +72,11 @@ private[spark] object SerDeUtil extends Logging {
Github user zasdfgbnm commented on the issue:
https://github.com/apache/spark/pull/18444
For some reason, I can not reproduce the error on my machine. I run the
test using the following command:
```bash
PYSPARK_PYTHON=$(which python2) ./bin/spark-submit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18444
**[Test build #79540 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79540/testReport)**
for PR 18444 at commit
1 - 100 of 407 matches
Mail list logo
