Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14891
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 jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/14891
@srowen, anyone you'd recommend to accept the PR (after you accepted)?
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14891
OK fair enough LGTM
---
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 jaceklaskowski commented on the issue:
https://github.com/apache/spark/pull/14891
Frankly, I'd not have bothered with the changes if I had not seen them
elsewhere. See
http://spark.apache.org/docs/latest/api/scala/index.html#org.apache.spark.sql.Dataset
and look for
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14891
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64708/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14891
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/14891
**[Test build #64708 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64708/consoleFull)**
for PR 14891 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14891
I think this kind of thing is fine to call out, but we haven't used this
convention, quite, elsewhere. The APIs are all "Scala-specific" unless
otherwise noted. Even then they're callable from Java,
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14891
**[Test build #64708 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64708/consoleFull)**
for PR 14891 at commit
