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 2017/02/07 22:17:41 UTC
[jira] [Commented] (SPARK-17498) StringIndexer.setHandleInvalid
should have another option 'new'
[ https://issues.apache.org/jira/browse/SPARK-17498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856918#comment-15856918 ]
Joseph K. Bradley commented on SPARK-17498:
-------------------------------------------
Linking related issue for QuantileDiscretizer where we provide a handleInvalid option for putting invalid values in a special bucket.
> StringIndexer.setHandleInvalid should have another option 'new'
> ---------------------------------------------------------------
>
> Key: SPARK-17498
> URL: https://issues.apache.org/jira/browse/SPARK-17498
> Project: Spark
> Issue Type: Improvement
> Components: ML
> Reporter: Miroslav Balaz
>
> That will map unseen label to maximum known label +1, IndexToString would map that back to "<undef>" or NA if there is something like that in spark,
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org