spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Pentreath (JIRA)" <>
Subject [jira] [Commented] (SPARK-14409) Investigate adding a RankingEvaluator to ML
Date Fri, 24 Feb 2017 07:51:44 GMT


Nick Pentreath commented on SPARK-14409:

[~roberto.mirizzi] the {{goodThreshold}} param seems pretty reasonable in this context to
exclude irrelevant items. I think it can be a good {{expertParam}} addition.

Ok, I think that a first pass at this should just aim to replicate what we have exposed in
{{mllib}} and wrap {{RankingMetrics}}. Initially we can look at: (a) supporting numeric columns
and doing the windowing & {{collect_list}} approach to feed into {{RankingMetrics}}; (b)
support Array columns and feed directly into {{RankingMetrics}} or (c) support both.

[~yongtang] already did a PR here: It is fairly
complete and also includes MRR. [~yongtang] are you able to work on reviving that PR? If os,
[~roberto.mirizzi] [~danilo.ascione] are you able to help review that PR?

> Investigate adding a RankingEvaluator to ML
> -------------------------------------------
>                 Key: SPARK-14409
>                 URL:
>             Project: Spark
>          Issue Type: New Feature
>          Components: ML
>            Reporter: Nick Pentreath
>            Priority: Minor
> {{mllib.evaluation}} contains a {{RankingMetrics}} class, while there is no {{RankingEvaluator}}
in {{ml.evaluation}}. Such an evaluator can be useful for recommendation evaluation (and can
be useful in other settings potentially).
> Should be thought about in conjunction with adding the "recommendAll" methods in SPARK-13857,
so that top-k ranking metrics can be used in cross-validators.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message