Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132418318
@shivaram thank you for reviewing and merging it!
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/8297
---
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 the feature is enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132417968
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132417967
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132417896
[Test build #41195 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41195/console)
for PR 8297 at commit
[`b3ff9f0`](https://github.
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132417749
Ok cool. I'll merge this first after Jenkins passes and then we can retest
#7833.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132417409
Right. However, I thought we should isolate the validation problem for
#7883. So I reverted it on other PR under review.
---
If your project is set up for it, you can r
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132416477
LGTM. I thought this was a part of some other open PR ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132415613
[Test build #41195 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41195/consoleFull)
for PR 8297 at commit
[`b3ff9f0`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132415115
Merged build triggered.
---
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132415135
Merged build started.
---
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
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8297#issuecomment-132414939
@shivaram could you review it, please? Thank you for your continuous
support.
---
If your project is set up for it, you can reply to this email and have your
reply appe
GitHub user yu-iskw opened a pull request:
https://github.com/apache/spark/pull/8297
[SparkR][Minor] Get rid of a long line warning
```
R/functions.R:74:1: style: lines should not be more than 100 characters.
jc <- callJStatic("org.apache.spark.sql.functions", "li
13 matches
Mail list logo
