You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Derrick Burns (JIRA)" <ji...@apache.org> on 2015/01/09 23:37:34 UTC
[jira] [Commented] (SPARK-5186) Vector.equals and Vector.hashCode
are very inefficient
[ https://issues.apache.org/jira/browse/SPARK-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14271989#comment-14271989 ]
Derrick Burns commented on SPARK-5186:
--------------------------------------
My mistake! I mis-read the implementation of toArray!
However, this means that the implementation is NOT incorrect, just poor.
Converting sparse vectors to dense vectors to compare them can be extremely
costly.
> Vector.equals and Vector.hashCode are very inefficient
> -------------------------------------------------------
>
> Key: SPARK-5186
> URL: https://issues.apache.org/jira/browse/SPARK-5186
> Project: Spark
> Issue Type: Bug
> Components: MLlib
> Affects Versions: 1.2.0
> Reporter: Derrick Burns
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> The implementation of Vector.equals and Vector.hashCode are correct but slow for SparseVectors that are truly sparse.
--
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