You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Kaushik Ranjan (JIRA)" <ji...@apache.org> on 2014/11/15 06:42:33 UTC
[jira] [Issue Comment Deleted] (SPARK-2335) k-Nearest Neighbor
classification and regression for MLLib
[ https://issues.apache.org/jira/browse/SPARK-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kaushik Ranjan updated SPARK-2335:
----------------------------------
Comment: was deleted
(was: Hi [~bgawalt].
For evaluation of KNN-join, one needs to calculate z-scores of data-points within the dataset.
Yu-ISHIKAWA has implemented the following
https://gist.github.com/yu-iskw/37ae208c530f7018e048
Will it be justified to put up a NewFeature Issue to address z-scores?
)
> k-Nearest Neighbor classification and regression for MLLib
> ----------------------------------------------------------
>
> Key: SPARK-2335
> URL: https://issues.apache.org/jira/browse/SPARK-2335
> Project: Spark
> Issue Type: New Feature
> Components: MLlib
> Reporter: Brian Gawalt
> Priority: Minor
> Labels: features
>
> The k-Nearest Neighbor model for classification and regression problems is a simple and intuitive approach, offering a straightforward path to creating non-linear decision/estimation contours. It's downsides -- high variance (sensitivity to the known training data set) and computational intensity for estimating new point labels -- both play to Spark's big data strengths: lots of data mitigates data concerns; lots of workers mitigate computational latency.
> We should include kNN models as options in MLLib.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org