Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 24 Dec 2017 07:21:00 +0000 (UTC)
From: "Joseph K. Bradley (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.12838622.1434585430000.526899.1514100060161@Atlassian.JIRA>
In-Reply-To: <JIRA.12838622.1434585430000@Atlassian.JIRA>
References: <JIRA.12838622.1434585430000@Atlassian.JIRA> <JIRA.12838622.1434585430382@jira-lw-us.apache.org>
Subject: [jira] [Commented] (SPARK-8418) Add single- and multi-value support
 to ML Transformers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 24 Dec 2017 07:21:11 -0000


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

Joseph K. Bradley commented on SPARK-8418:
------------------------------------------

One more thought: Looking at existing PRs and docs for inputCols & outputCols, I'm worried it may be unclear to users how to use multi-column APIs.  E.g., if OneHotEncoderEstimator (or any of the others) have docs talking about transforming a Numeric column to a Vector column, then users may be confused about whether each inputCol is treated independently, all concatenated in the output, or what.  I'm commenting on the OHE PR but thought this was relevant to all of these PRs.

> Add single- and multi-value support to ML Transformers
> ------------------------------------------------------
>
>                 Key: SPARK-8418
>                 URL: https://issues.apache.org/jira/browse/SPARK-8418
>             Project: Spark
>          Issue Type: Sub-task
>          Components: ML
>            Reporter: Joseph K. Bradley
>
> It would be convenient if all feature transformers supported transforming columns of single values and multiple values, specifically:
> * one column with one value (e.g., type {{Double}})
> * one column with multiple values (e.g., {{Array[Double]}} or {{Vector}})
> We could go as far as supporting multiple columns, but that may not be necessary since VectorAssembler could be used to handle that.
> Estimators under {{ml.feature}} should also support this.
> This will likely require a short design doc to describe:
> * how input and output columns will be specified
> * schema validation
> * code sharing to reduce duplication


--
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