Github user itg-abby commented on the issue:
https://github.com/apache/spark/pull/15496
@sethah
Thanks for your input! SciPy is definitely a much better solution, I was
naively operating under the assumption that I must match DenseVector types 1:1.
Actually, there is already a flag "_have_scipy" so I have added the check
for that in order to create the type when it is available. Otherwise, users
just get the standard SparseVector back.
The PR has been updated.
---
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
