Github user sethah commented on the issue:
https://github.com/apache/spark/pull/15496
@itg-abby I see what you're going for, but I don't think it's a great idea
in general. For many operations on sparse vectors, we should not materialize
the sparse vector as dense. I'm not sure if it's reasonable to use Scipy, but a
better solution to me would be:
````python
def __getattr__(self, item):
csr = scipy.sparse.csr_matrix((self.values, self.indices, [0, 2]))
return getattr(csr, item)
````
As you say, we can alternatively write our own. But the current patch would
materialize potentially enormous arrays unnecessarily. Thoughts?
cc @holdenk
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
