You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Rekha Joshi (JIRA)" <ji...@apache.org> on 2015/07/07 08:16:05 UTC
[jira] [Comment Edited] (SPARK-3164) Store DecisionTree
Split.categories as Set
[ https://issues.apache.org/jira/browse/SPARK-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616246#comment-14616246 ]
Rekha Joshi edited comment on SPARK-3164 at 7/7/15 6:15 AM:
------------------------------------------------------------
it was not assigned, nor closed/commented, and improvement suggestion needed in latest snapshot.but ack on decision made on api stability. thanks for letting me know [~josephkb]
sad, as i updated 5 files for a trivial pursuit, with the scala style checks :-) :-)
was (Author: rekhajoshm):
it was not assigned, nor closed/commented, and improvement suggestion needed in latest snapshot.but ack on decision made on api stability. thanks for letting me know [~josephkb]
# sad, as i updated 5 files for a trivial pursuit, with the scala style checks :-) :-)
> Store DecisionTree Split.categories as Set
> ------------------------------------------
>
> Key: SPARK-3164
> URL: https://issues.apache.org/jira/browse/SPARK-3164
> Project: Spark
> Issue Type: Improvement
> Components: ML
> Reporter: Joseph K. Bradley
> Assignee: Joseph K. Bradley
> Priority: Trivial
> Fix For: 1.4.0
>
>
> Improvement: computation
> For categorical features with many categories, it could be more efficient to store Split.categories as a Set, not a List. (It is currently a List.) A Set might be more scalable (for log n lookups), though tests would need to be done to ensure that Sets do not incur too much more overhead than Lists.
--
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