Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13693
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60608/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13693
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13693
**[Test build #60608 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60608/consoleFull)**
for PR 13693 at commit
[`90246cb`](https://github.com/apache/spark/commit/
Github user nezihyigitbasi commented on the issue:
https://github.com/apache/spark/pull/13693
yep will do.
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/13693
Thanks @nezihyigitbasi.
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/13693
But well, you already reverted the change, so @nezihyigitbasi please send
the PR again with my changes on top.
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13693
It looks large but it's basically just moving the method to the class
instead of the object.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user davies commented on the issue:
https://github.com/apache/spark/pull/13693
@nezihyigitbasi I reverted that commit both in 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
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/13693
Ah the "fix" is much larger than I thought (I thought it would've been an
one liner)
@davies was suggesting reverting the commit and then do a proper review.
---
If your project is set up fo
Github user nezihyigitbasi commented on the issue:
https://github.com/apache/spark/pull/13693
@vanzin thanks for fixing this.
---
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
enab
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/13693
@rxin
---
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 feat
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13693
**[Test build #60608 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60608/consoleFull)**
for PR 13693 at commit
[`90246cb`](https://github.com/apache/spark/commit/9
12 matches
Mail list logo
