Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18450
thanks for the review, merging 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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18450
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18450
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78853/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18450
**[Test build #78853 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78853/testReport)**
for PR 18450 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18450
**[Test build #78853 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78853/testReport)**
for PR 18450 at commit
Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/18450
I think it is good that this would no longer throw exceptions at runtime.
Is the purpose of not allowing nested executions to minimize the queries shown
in the UI? If that's the only purpose then I
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18450
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78783/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18450
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/18450
**[Test build #78783 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78783/testReport)**
for PR 18450 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18450
**[Test build #78783 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78783/testReport)**
for PR 18450 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18450
cc @rdblue @zsxwing
---
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
11 matches
Mail list logo