Skip to content

MLContext extension naming mismatch with dynamic API #1754

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
artidoro opened this issue Nov 28, 2018 · 1 comment
Closed

MLContext extension naming mismatch with dynamic API #1754

artidoro opened this issue Nov 28, 2018 · 1 comment
Labels
API Issues pertaining the friendly API

Comments

@artidoro
Copy link
Contributor

Extensions to MLContext don't consistently match either the static API names, or the dynamic API names for estimators. This leads users that directly instantiate the dynamic API to find different names for the same estimators than when finding them through MLContext.

Since the estimators obtained through MLContext use the dynamic API, I would suggest that their names match the dynamic API names.
@artidoro artidoro added the API Issues pertaining the friendly API label Nov 28, 2018
@sfilipi
Copy link
Member

sfilipi commented Nov 29, 2018

CC: @Zruty0, @CESARDELATORRE

@artidoro I would suggest closing this, and adding to the naming discussion in #1690

@ghost ghost locked as resolved and limited conversation to collaborators Mar 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
API Issues pertaining the friendly API
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@artidoro @sfilipi