Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14818
If we are closely matching the capability of glmnet then we could name it
`glmnet` or `spark.glmnet`, if this fits in the existing `spark.glm`
implementation (which is different from the SparkR `glm` function) then we
should add it there, otherwise our convention would be to add a new function
that is named for what it does, such as "spark.multiclassLogisticRegression"
From what you have described perhaps it makes sense to add to `spark.glm`?
---
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
