Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-162647533
Also, can you please add the "[DOC]" tag to the PR title? T'hanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9952#discussion_r46861703
--- Diff: docs/mllib-clustering.md ---
@@ -718,6 +718,34 @@ sameModel = LDAModel.load(sc, "myModelPath")
+## Bisecting k-means
+
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-162626994
That should be 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 project does not have this f
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9952#discussion_r46861709
--- Diff: docs/mllib-clustering.md ---
@@ -718,6 +718,34 @@ sameModel = LDAModel.load(sc, "myModelPath")
+## Bisecting k-means
+
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9952#discussion_r46861700
--- Diff: docs/mllib-clustering.md ---
@@ -718,6 +718,34 @@ sameModel = LDAModel.load(sc, "myModelPath")
+## Bisecting k-means
+
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/9952#discussion_r46861720
--- Diff:
examples/src/main/scala/org/apache/spark/examples/mllib/BisectingKMeansExample.scala
---
@@ -0,0 +1,58 @@
+/*
+ * Licensed to the Apache
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-162612827
I'll go ahead and review this, but if you have time to add a Java example,
that would be awesome--thanks!
---
If your project is set up for it, you can reply to this
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-162607544
Thanks! I'll review today
---
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 hav
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-161983105
@jkbradley ping
---
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 featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-161472005
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-161472006
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-161471916
**[Test build #47095 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47095/consoleFull)**
for PR 9952 at commit
[`2f4c2a5`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-161468528
**[Test build #47095 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/47095/consoleFull)**
for PR 9952 at commit
[`2f4c2a5`](https://gith
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-161466765
I moved the documentation to this PR from
https://github.com/apache/spark/pull/9968. Because the PR depends on this PR.
I modified the docs for `BisectingKMeans`
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-160019724
@jkbradley could you review 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 project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-160018848
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-160018847
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/9952#issuecomment-160018805
**[Test build #46790 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46790/consoleFull)**
for PR 9952 at commit
[`86f6085`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-160016969
**[Test build #46790 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46790/consoleFull)**
for PR 9952 at commit
[`86f6085`](https://gith
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-160012938
All right. I'll fix 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 project does not have thi
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9952#issuecomment-159702245
When you modify this and [https://github.com/apache/spark/pull/9968] to use
the ```include_example``` functionality, it may make sense to change this
example code to u
21 matches
Mail list logo
