Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15514
Merged to master
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15514
I'm OK with it. For the record, was there any fix here that impacts Spark?
updating just to keep updated isn't a bad idea but wouldn't want to update
through every version of everything. Maybe at
Github user davies commented on the issue:
https://github.com/apache/spark/pull/15514
cc @JoshRosen
---
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
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15514
Awesome, thanks for taking this on @jagadeesanas2, this looks pretty
reasonable although it might be helpful if we mentioned briefly the PR
description what the Py4J changes were in this release
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15514
**[Test build #3356 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3356/consoleFull)**
for PR 15514 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15514
**[Test build #3356 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3356/consoleFull)**
for PR 15514 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15514
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67075/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15514
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/15514
**[Test build #67075 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67075/consoleFull)**
for PR 15514 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15514
**[Test build #67075 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/67075/consoleFull)**
for PR 15514 at commit
10 matches
Mail list logo
