Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16050
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16050
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69285/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16050
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/16050
**[Test build #69285 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69285/consoleFull)**
for PR 16050 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16050
**[Test build #69285 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69285/consoleFull)**
for PR 16050 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16050
cc @srowen do you mind if I ask to take a look 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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16050
I guess this might not cause conflicts with
https://github.com/apache/spark/pull/16013.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
