Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17100
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/73604/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17100
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/17100
**[Test build #73604 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73604/testReport)**
for PR 17100 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17100
**[Test build #73604 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/73604/testReport)**
for PR 17100 at commit
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/17100
@rberenguel : how about adding the "[SQL]" tag to this, since while the
feature request comes out of PySpark its changing the SQL code.
---
If your project is set up for it, you can reply to this
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/17100
Jenkins, 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17100
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
