Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/13641
@mengxr I thought more about the `UnaryTransformer` cases, and I actually
don't think it's necessary to bump the annotations for the classes, just the
public methods/vals exposing `Vector`.
I thought the concrete classes would be binary incompatible but I don't
actually think that is the case - and I just tested this (master against commit
immediately prior to e2efe05) and apart from `scalingVec` it is fine.
I've created
[SPARK-16127](https://issues.apache.org/jira/browse/SPARK-16127) to track
further annotations that need updating related to new `ml.linalg` classes, and
I think I will revert this particular change for `UnaryTransformer` classes in
#13840.
---
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]
