Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/8883#issuecomment-157885506
> Would transform and predict confuse users?
Probably. Not sure what's best. We could also just overload transform,
but that would cause problems for the next issue you asked about.
> And what does predict mean by default if there could be multiple outputs,
e.g., predicted class, confidence, etc? Do we have a default semantic that most
users would agree on?
I think it's reasonable for "predict" to refer to the label being
predicted. Other outputs can have other more specific names. (If you talk
about the "prediction" for a prediction problem, it's pretty clear what you
mean.)
---
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]
