Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/3099#issuecomment-62299039
@shivaram
> IMHO it would be good to have the developer API updates as well and test
a couple of more pipelines before we push this out.
I'll try to get a branch based on this PR ready next week for feedback.
Not sure if we want to do a mega-PR though; hopefully it can be kept as a
separate follow-up.
> Also I am not sure I fully understand the difference between the User API
and the Developer API
These are loose terms; part of the "Developer" API will actually be public.
E.g., Classifier will be public since it will be needed for the boosting API.
But most users won't have to worry about these abstract classes, and the
classes will include some private[ml] methods to make developers' lives easier.
---
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
