Github user srowen commented on the issue:
https://github.com/apache/spark/pull/15342
This is what SPARK-3261 is about. It's a corner case to be sure. To me it
seems like having duplicate centroids is worse because the model loses some of
its meaning. Points may arbitrarily assign to one or the other of two identical
centroids. Of the 3 possible behaviors, looks like we have all 3 on the table:
1) error
2) return < k centroids
3) return k centroids
I suppose I prefer the new behavior but I can't say I feel that strongly. I
guess matching scikit has some value.
---
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]
