You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Joseph K. Bradley (JIRA)" <ji...@apache.org> on 2015/01/07 01:03:35 UTC

[jira] [Updated] (SPARK-5114) Should Evaluator by a PipelineStage

     [ https://issues.apache.org/jira/browse/SPARK-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph K. Bradley updated SPARK-5114:
-------------------------------------
          Component/s: ML
          Description: 
Pipelines can currently contain Estimators and Transformers.

Question for debate: Should Pipelines be able to contain Evaluators?

Pros:
* Evaluators take input datasets with particular schema, which should perhaps be checked before running a Pipeline.

Cons:
* Evaluators do not transform datasets.   They produce a scalar (or a few values), which makes it hard to say how they fit into a Pipeline or a PipelineModel.
     Target Version/s: 1.3.0
    Affects Version/s: 1.2.0
              Summary: Should Evaluator by a PipelineStage  (was: Should )

> Should Evaluator by a PipelineStage
> -----------------------------------
>
>                 Key: SPARK-5114
>                 URL: https://issues.apache.org/jira/browse/SPARK-5114
>             Project: Spark
>          Issue Type: Question
>          Components: ML
>    Affects Versions: 1.2.0
>            Reporter: Joseph K. Bradley
>
> Pipelines can currently contain Estimators and Transformers.
> Question for debate: Should Pipelines be able to contain Evaluators?
> Pros:
> * Evaluators take input datasets with particular schema, which should perhaps be checked before running a Pipeline.
> Cons:
> * Evaluators do not transform datasets.   They produce a scalar (or a few values), which makes it hard to say how they fit into a Pipeline or a PipelineModel.



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