Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18795
Merged to master/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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18795
**[Test build #3878 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3878/testReport)**
for PR 18795 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18795
**[Test build #3878 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3878/testReport)**
for PR 18795 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18795
**[Test build #3877 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3877/testReport)**
for PR 18795 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18795
**[Test build #3877 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3877/testReport)**
for PR 18795 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18795
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
