Github user jsoltren commented on the issue:
https://github.com/apache/spark/pull/18604
ð
---
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
@jsoltren please close, this was merged but PRs to branches are not closed
automatically.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18604
merging 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 feature
enabled and wishes so,
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 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 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 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 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
12 matches
Mail list logo
