Github user husseinhazimeh commented on the issue:
https://github.com/apache/spark/pull/13980
Thanks @sethah ! I had no idea this existed. As you've mentioned in your
comment in PR #8883, exposing the prediction methods to the public API can be
handy for ensemble methods, and now there is an extra reason: latency.
I'm not sure about the merge conflicts in #8883 but they're probably due to
the new unit tests introduced. Do you think new unit tests are needed? The
current tests for `transform` are already invoking `predict` internally which
can ensure correctness..
---
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
