Github user ehsanmok commented on the pull request:
https://github.com/apache/spark/pull/11617#issuecomment-195066706
Well, if it's about performance shouldn't the same apply to BLAS then? and
the jira I mentioned is not something outside of Spark, it's going to be on top
of mllib.linalg.optimization. Cloning the array is the solution but not a
consistent one with the whole Spark as far as i can tell and developer should
always do that for CholeskyDecomposition but not for BLAS! That's the double
standard. And accordingly docs and those javaALS tests must be modified.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
