Github user hhbyyh commented on the issue:
https://github.com/apache/spark/pull/16020
Close this as it's better resolved in
https://issues.apache.org/jira/browse/SPARK-18608.
Thanks for the comments and discussion.
---
If your project is set up for it, you can reply to this email
Github user hhbyyh commented on the issue:
https://github.com/apache/spark/pull/16020
@MLnick Do you think we still need the event listener unit test?
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16020
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16020
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69582/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16020
**[Test build #69582 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69582/consoleFull)**
for PR 16020 at commit
[`678cd43`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16020
**[Test build #69582 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69582/consoleFull)**
for PR 16020 at commit
[`678cd43`](https://github.com/apache/spark/commit/6
Github user hhbyyh commented on the issue:
https://github.com/apache/spark/pull/16020
I just added a straight forward check for the data frame cache level.
---
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 MLnick commented on the issue:
https://github.com/apache/spark/pull/16020
Yes unit tests would be good to add.
Tests may require using event listeners to check the caching of the
intermediate dataset with/without cached initial data. Or at least that is
the
Github user hhbyyh commented on the issue:
https://github.com/apache/spark/pull/16020
Sure we can change KMeans as well. And perhaps we can also add some unit
tests. I'll send update.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16020
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16020
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69247/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16020
**[Test build #69247 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69247/consoleFull)**
for PR 16020 at commit
[`0105220`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16020
**[Test build #69247 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69247/consoleFull)**
for PR 16020 at commit
[`0105220`](https://github.com/apache/spark/commit/0
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16020
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69198/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16020
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/16020
**[Test build #69198 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69198/consoleFull)**
for PR 16020 at commit
[`a4c88ee`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16020
**[Test build #69198 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69198/consoleFull)**
for PR 16020 at commit
[`a4c88ee`](https://github.com/apache/spark/commit/a
17 matches
Mail list logo
