Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17507
Merged to master/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 and wishes so,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17507
**[Test build #3633 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3633/testReport)**
for PR 17507 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17507
**[Test build #3633 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3633/testReport)**
for PR 17507 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/17507
@guoxiaolongzte no need to ping nearly this frequently. We frequently leave
changes open for comments for at least a few days. Ping if you have addressed
all comments but haven't seen replies in
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17507
help merge spark master@srowen
---
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 guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/17507
@srowen Help code review,thank you!
---
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/17507
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
