Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/13580
Merged into master and 2.0
---
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
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13580
LGTM -- seems like the lower risk option here, especially for 2.0.
---
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
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13580
I don't have the strong feelings, but I still believe both cases hurt
performance in different ways and in rare cases, and if that's to happen I
prefer the version that yells less at the user. In
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13580
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/13580
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60241/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13580
**[Test build #60241 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60241/consoleFull)**
for PR 13580 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13580
**[Test build #60241 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60241/consoleFull)**
for PR 13580 at commit
