You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Liang-Chi Hsieh (JIRA)" <ji...@apache.org> on 2017/10/06 03:21:02 UTC

[jira] [Commented] (SPARK-8515) Improve ML attribute API

    [ https://issues.apache.org/jira/browse/SPARK-8515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194074#comment-16194074 ] 

Liang-Chi Hsieh commented on SPARK-8515:
----------------------------------------

I'm working on a new ML attribute API which is supposed to solve the issues like SPARK-19141 and SPARK-21926 and maybe SPARK-12886.

The basic attribute design is similar to previous API. But new API supports sparse Vector attributes. So we don't need to keep every attributes in a Vector column. The new API is also trimming down some unnecessary parts in previous API.

cc [~mlnick]

> Improve ML attribute API
> ------------------------
>
>                 Key: SPARK-8515
>                 URL: https://issues.apache.org/jira/browse/SPARK-8515
>             Project: Spark
>          Issue Type: Improvement
>          Components: ML
>    Affects Versions: 1.4.0
>            Reporter: Xiangrui Meng
>              Labels: advanced
>
> In 1.4.0, we introduced ML attribute API to embed feature/label attribute info inside DataFrame's schema. However, the API is not very friendly to use. We should re-visit this API and see how we can improve it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org