GitHub user holdenk reopened a pull request:
https://github.com/apache/spark/pull/10150
[SPARK-11944][PYSPARK][MLLIB] python mllib.clustering.bisecting k means
From the coverage issues for 1.6 : Add Python API for
mllib.clustering.BisectingKMeans.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/holdenk/spark
SPARK-11937-python-api-coverage-SPARK-11944-python-mllib.clustering.BisectingKMeans
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/10150.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #10150
----
commit 9b95e944f943a31ea8e969faa80662bce1080bdd
Author: Holden Karau <[email protected]>
Date: 2015-12-02T16:07:39Z
Some progress, not a lot
commit 427e487ca3e2ad27b692d9acd40fbd8a9b726312
Author: Holden Karau <[email protected]>
Date: 2015-12-03T04:20:55Z
murh some murh. airplain code isn't very good but it distracts me - start
adding a class for calling bisectingkmeans. I don't really like how
BisectingKMeans is set up (its different from many of the others which is fnur)
but trying to decide if I should make the python API more closely match the
Scala API or match the rest of the Python API. These are questions for after
I've slept perhaps.
commit f5a40c85a2b91b4c93a66db2c15164bb57db44d6
Author: Holden Karau <[email protected]>
Date: 2015-12-04T21:01:58Z
A bunch of works towards getting BisectingKMeans in PySpark
commit d3e4c1a6a19e8cb0d19bbe5feab48c7655d48a00
Author: Holden Karau <[email protected]>
Date: 2015-12-04T22:23:08Z
Add a bit more pydoc descriptions, fix the prediction call, and verify with
different k
commit 868c4a7931834fe2bf85ccabe97a640f4bff4dc2
Author: Holden Karau <[email protected]>
Date: 2015-12-05T04:25:17Z
fix compute cost
----
---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
